You need to know that 2step is done before adding x.

x = (x + (2step)) % width Or x = ( 2step + x) % width

Should be preferred?

Personally I try to bracket all things like this, so that it isn't hidden.

You're introducing a currency that does 1/8ths. A computer can handle that a lot better than decimal.

What real web are you going to get when there's no 3g, much less a reliable signal on a lot of places.

Wap worked well for actually relaying information.

Well no. Probably not...

It would be nice if the EU or someone introduced an energy star type system for reliability and repairability so that consumers could have some kind of idea what the quality is likely to be.

I was more just musing on the space around high level assembler/ low level programming language. Currently C is the option. So anything entering that space will be competing with C

What am I supposed to infer about the quality of a design company when they can't even get such simple things right?

I'm just thinking about something like the meteor missile, if you're up against a 5th gen jet with shorter range missiles, the 5th gen jet doesn't necessarily have the advantage.

Then there's things like drones. A cheap drone with a good missile is arguably the better option than an expensive jet with poor weapons.

Yes, the best option is the good jet with the good missile, but most militaries have limited budgets, so it isn't a question of having all the the things, but one of where that money is best spent. I suppose you could argue that the military knows best, but then the US military insisted on keeping cannon around on jets just in case, so it seems to me, at least plausible that the current view is more about inertia than bang for buck.

And also whether it's generating less efficient code to satisfy the type safety requirement.

Further if your 5th gen jets are relying on tech from your adversary....

TBF I'm playing with a pi Pico, so anything I do is likely to be more influenced by the memory set up. Ie xip.

I could write a whole essay on this. But I was more meditating on the assumptions and decisions made, because that was obvious/easy given the hardware available. Why don't really write languages like that now, and I don't really think C is that language anymore. But it would be interesting to see what could emerge.

Are there some hidden depths to formatting/converting that I'm missing? And yes. I know not to use floats