There would also be a block of memory mapped hardware registers also needing address space that you have to poke to make the GPU actually do GPU things, instead of just being an expensive way to add extra memory to a system, no?
And if my experience from embedded development is in any way transferable, they're probably fairly spread out and probably takes a fairly big chunk of address space too.
And if Trump had just faded into obscurity after 2021 we probably wouldn't see this kind of realignment, but the fact he got reelected makes it look much less like a fluke and more like an USA that's increasingly unreliable on the international stage
Imposing tariffs one day and TACOing out a few days later and infinitum is not reliable. There is no 4D chess going on, only incompetency and self-enrichment.
The US is on the path of Russia since the end of the iron curtain, moving to a kleptocracy ruled by (tech br)olichargs.
The electoral + two-party system makes it nearly impossible to break out of this.
It's not about lights, it's about electricity always being available.
And well, always having power available (for domestic, but also for expensive production facilities that looses money while idle) using renewables is a lot more expensive than generating most of your power with renewables
To be competitive with ARM and x86 they need a talented design team creating fast and wide cores on a modern node. (which I expect to take a decade at least)
For the vast majority of non-number-crunching code any theoretical difference between instruction sets vanishes in the noise of core design.
The world /is/ peaceful right now... relatively that is.
Not to say there isn't war, but they're small wars with a million deaths being a big one.
More people died in Second World War[1] than in all wars since then combined.
If not for the Russian Civil War and WW2, the same would probably true for the Great War.
War is terrible, but the fraction of people who died in wars the last 75 years is substantially smaller than the 75 years before that and I do think that is worth celebrating.
I am not confident this will hold for the next 75 years
Now I know I'm the big bad military guy saying this, but just give it a chance.
Do you think that maybe the reluctance to engage in large wars over the last 75 years is a benefit of the nuclear deterrent rather than political ideologies, or world view narratives, or hegemons?
Just kind of noticing that the 75 year figure you put out there kind of dovetails nicely with the existence of the nuclear deterrent in multiple global arsenals.
Obviously, I believe in the nuclear deterrent. Just wondering if there are other people out there willing to admit that it has been the best tool in mankind's toolbox for obliging people to talk to each other rather than go to war.
As long as it works... and maybe one day it will no longer work and then at least we can point back to discussions such as these and say 'you were right, up to a point'.
The problem with weapons is that usually weapons end up being used. And with the US now no longer working against proliferation the risks are going up.
I cannot actually get the program working (which could easily be user error), but I could replicate the md5 by removing a newline vim inserted for me. If your file is 142 bytes, that's possibly what you're seeing
For the 'hello' program, you need to use DosBox-X with the 'cpu cputype=8086' parameter. You can use 86Box or MartyPC as well but those take more effort to set up and get the executable onto them.
x86 assembly isn't something I'm familiar with (and I should really get back to $dayjob), but I will mention the existence of emoji-test.txt [1] in case somebody wants to try and mine more executable sequences. It might be worth paying attention to the minimally-qualified, unqualified and component lines, which can be added and removed semi freely. No idea if they actually correspond to useful byte sequences.
I don't see why that would matter. Sure, it was noticed on a browser but ultimately this article is about overlap between x86 assembly and a subset of the unicode standard. The browser isn't really involved.
having the emojis survive copy & paste from a browser is surprisingly frustrating. I would have expected there to be well-defined semantics for this, but a lot of things insert variation selectors (U+FE0F) after certain emoji which breaks the code.
It's less to do with browser versions and more to do with websites. Mastodon and unfortunately blogspot seem to mess up the emoji. Fortunately you can click on the disassembly links that go to my disassembler and copy them from there.
Emoji are text. Which text editor/browser/settings should I be using to ensure I copy your reply accurately?
With the exception of (sigh) newlines, I surely hope your text editor accurately records the characters you paste into it. This job isn't different just because the characters are strange, multi colored ligatures.
Edit: As long as you work in UTF-8 that is, but you have to go out of your way to use any other encoding as an interchange format these days, even if alternative internal encodings aren't uncommon-
Some relatively recent emoji might not work in outdated browsers/operating systems. Generally, emoji font are regularly updated, but if you're using the stock browser (or Safari) on an outdated phone, you might not be able to render a lot of these emoji.
Missing emoji should still be copyable though, it just won't look as funny.
On iOS (and the same OS in other form factors), Safari is tied to your operating system. Unlike Android or Windows or even macOS, your browser cannot be updated when your device no longer gets feature updates.
In the EU one could theoretically deploy an alternative browser engine, but that relies on the version of iOS being recent enough to get the changes that Apple had to make to permit that, and in practice there are no alternative browser engines yet.
Apple doesn't keep their emoji list up to date. Apple invents new emojis, implements them, and once enough people are using it, unicode will pretty much have to incorporate it. They're pretty much to emojis what google is to web standards.
And if my experience from embedded development is in any way transferable, they're probably fairly spread out and probably takes a fairly big chunk of address space too.
reply