I too share your sentiments about the upcoming generation(s). The other thing I notice about them is that they're overall far more accepting about differences in race, sexual orientation, gender, etc.
The Jacobin JVM [0] does exactly what you suggest: 64-bit operand stack and local variables. Longs and doubles still occupy two slots on the operand stack, so as to avoid having to recompile Java classes that assume the two-slot allocation, but the design avoids having to smash together two 32-bit values every time a long or double is operated on.
Since the governor has given multiple reprieves, can he not grant clemency to avoid the miscarriage of justice? Does the governor not have that power in Oklahoma, as he does in most other states?
I have tinnitus. And I feel that silence id the only true luxury. When I am in an environment that is so quiet that the only thing I hear is the hum of my tinnitus, I feel very much at peace.
This reminds me of a point made by the late Stan Kelly-Bootle, who for years wrote the Devil's Advocate column in UNIX Review magazine. In the early 1990s, he was discussing Microsoft's new C compiler and noted that in the promo material for the new compiler, it showed a benchmark for a loop that counted from 1 to 10,000 then printed "Hello". MS claimed that without optimization it took a few milliseconds, after optimization: 0 ms. A small asterisk explained the optimizer simply removed the loop. Kelly-Bootle pointed out, that the only reason a developer would write such a loop was to introduce a needed delay. Therefore, deleting the loop was not optimizing, but in fact pessimizing. And so, it was in fact Microsoft's Pessimizing C compiler.
Agreed about the New Yorker. Likewise, agree with the exact same description for the Atlantic. And I have bounced back and forth between them over the years.
I quite agree. I take it a step further: I think devs should be taught how to handle complexity better. It's a skill that some programmers have and that others sorely lack, but AFAIK, it's not a skill taught at all in CS programs.
It's not close to as easy as you represent. To start with, there are 204 instructions, some of them, far more complex than what you term "basic," such as invokedynamic. The exception mechanism is also far from "simple," -- it's simple conceptually but extremely difficult to get exactly right when it involves finally clauses both in the exception handler and the original excepting code. There are many subtleties that can lead to completely wrong results if not designed very, very carefully. It's far from "simple."
The folks at the Jacobin JVM [0] project (a JVM written in Go) are working on the issue of size and the ability to have a fully functional JVM maintained by a small group of developers. Right now, per the latest post [1], they can run simple classes and expect to complete the interpreter in the next few months.
> For much of its lifetime, SQLite wasn't taken seriously
As far as I can recall, it was always well regarded as an embeddable database. What makes you think that it wasn't taken seriously "for much of its lifetime"?
Came here to say this. The least they could have done is provide you with a free credit report, regardless of whether you previously used your freebie.
Well done satire will fool any community. That's the definition of good satire. I don't think HN is any more easily fooled than other communities. And frequently HN finds some aspect being ridiculed and shows that in fact it's not nearly as dismissable as the satire would have one believe.
Japanese is a language with no future tense and a very choppy system of plurals (many of which have to be inferred). I don't think it's a good candidate.
This! I am frustrated at how often devs will not accept that simple things become incredibly complicated at scale. That favorite coding technique? That container you wrote? Those tests you added? All good, but until you've tested them at scale, don't assert that everyone should use them. This dynamic is true in the other direction too: that techniques often taken for granted simply are not feasible in highly resource-constrained environments. With rare exception, the best we can say with accuracy is that "I find X works well enough in the typical situations I code for."