Ah it looks like the editor does, but the run screen does not. My guess would be since it’s emulating dos programs, probably the keyboard should always be visible.
in the context of CPU performance / architechture `IPC` pretty much always means "Instructions per clock". That's a measure of the internal parallelism a given CPU core is achieving. Most of the time code is not able to get very close to the theoretical maximums a core can achieve for very long, so the numbers the OP is quoting are incredibly impressive.
I believe most of the 8bit microcontrollers from this era have no good optimizing compilers that get close to what competent practitioners achieve with assembly. I think it has to do with having complex addressing modes making the C stack fairly inefficient.
You are arguing against a very well known phenomenon. Technical people often avoid getting promoted to management precisely because they love doing the thing themselves. Despite the higher potential for impact in a management position, losing the detailed view of a practitioner is a real loss. This phenomenon is less obvious in big tech because there are so many people who really wanted to be managers the whole time, but had to be engineers first or never really cared about the work, but want a promotion for the better pay.
You either replied to the wrong comment or didn’t and proved my point exactly: some people like the technical low level approach, others prefer the higher level architectural work.
There’s space for both and there’s a need for both.
The missing piece that makes it not a tautology is that two apps side by side have the same aspect ratio as one app full screen (but 90 degrees rotated)
Equivalence on what metrics? In theory what you are asking for makes sense, but I think it is very hard to actually specify what equivalent means in the context of an optimization process that needs to emit code with observably different behavior. Sometimes (although admittedly rarely) speeding up sections of code can even be undesirable for example branchless code for constant time algorithms that avoid timing or energy side channel leaks, or the much more mundane elimination of signed overflow checks or other undefined behavior quirks.
Listening to eskil’s talk from the better software conference, he said in order to stand on the shoulders of giants they must first stand still. I really like that metaphor, because it basically suggests today’s apps that have sprawling unaudited dependency graphs that change all the time is effectively teetering on the shoulders of stumbling giants. The visual seems very apt for the how brittle our current software industry feels.
I agree with that statement, but disagree with "The visual seems very apt for the how brittle our current software industry feels". It feels brittle, but for every single supply-chain-attack that has happened in the past year, nothing of significant was felt. So in the end, it seems like we're doing okayishly well.
I think you could make a case for that, especially when landing in water. Quite a few dense urban areas people might need to get to have water nearby suitable for landing seaplanes. I think you would end up creating communities further from the urban areas dedicated to this mode of transport. It’s definitely not a simple or guaranteed idea, but it is actually feasible politically and technically.
reply