I expect that a lot of bad norms that crop up in various programming communities will get tossed out after years of dysfunction, often as a result of outsiders and younger people arriving, and stating the obvious: This doesn't make sense. It's actually nice to know this when dealing with all of the mess in the present. You can't change it now, but eventually someone will.
But yes, LLMs are likely to force permanent conformity.
One could also talk about how language in general shifts with the population, but LLMs are likely to prevent it. One would think anthropologists are already looking into this experimentally...
It doesn't even matter and isn't worth arguing about what emotional state the submitter obtains. I don't care if they even achieve nirvana and ascend to permanent buddhahood.
What matters is that they are wasting the time & patience of someone who is doing good work that others benefit from.
Any happiness gained from doing that to someone is parasitic.
Important keyboard design note the author would agree with but didn't point out: Function keys are supposed to be divided into groups of four with a distinct gap between each group. This makes it much easier for the wayward touch-typist to find things.
BTW I've gone back to wired keyboard because most companies assume people who prefer wireless prefer as many unnecessary bells and whistles as possible to the point of compromising the design. There is no concept of some features being better than others, just a black/white everything/nothing.
Also refer to automobiles, tv's, all modern design...
There is very clearly an angry backlash, even if it is a backlash against phantoms, even if people are only demanding a better liar than the previous. There are no psychological black holes; the stress builds and eventually explodes.
I already know I'm dealing with huge perf issues caused by ORM & lazy-load semantics. I/O abuse is usually going to be so, so much worse than memory/cache issues. Java is mainly used for business information systems, where I/O is king. Plain vanilla memory abuse is also a big one.
But my main problem is a mgmt convinced the magic wand of AI will make all sorts of problems dissapear, and it's going to take 5 years for them to realize nope.
It's still fun to learn about cache optimization though, esp. when someone makes it reasonably digestible like this. And maybe it also helps people to recognize that OOP is not some great over-arching zen truth of truths.
> One computer scientist speculated that his LLM had attained sentience.
> How did he reach that conclusion? Basically, he asked “Are you conscious?”, the machine responded “Yes”, and that was that.
Oh, come on now. This is referring to Blake Lemoine, and while I doubt his conclusions, he wasn't being as simplistic as all that. He's not completely stupid.
This is not a writeup of "Ada is better than everything else". The author is explaining how Ada achieved safety/reliability goals that your favorite language independently evolved much later on. That is why they kept bringing up year-of-arrival for comparison.
Examples would be a nice bonus but I think the author eschewed such because they weren't interested in writing a tutorial. They had a very specific point to make and stuck to it, resulting in a very informative but concise article that reads well because of its highly disciplined authorship.
How about "Working with AI just feels like having a team of junior employees who are completely unscrupulous, sychophantic and sometimes profoundly stupid psychopathic liars"?
Am amused that someone feels compelled to justify writing a db in C#. Such conscientiousness!
I'm not sure authors of Cassandra, ElasticSearch, MongoDB (and more...?) ever had the slightest twinge of uncertainty about whether a managed memory env would cause far more problems than it fixed, even with less native tooling than in C#. Java bros DGAF
I really like the idea of implementing the std lib separate from the language. I think that would be a huge blessing for Java, Go and others, ideally allowing faster iteration on most things given that we usually don't need a reinvention of the compiler/runtime just to make a better library.
> This meant I could start the computer, log in, potentially start and use several applications and only then turn on the screen.
I mean... well... responsiveness matters to me too, and I am impressed by such inspired productivity, but... I'm also confused. Why not turn on the screen - the monitor, right?
Now thinking about how gui lag might impact the sight-impaired, tangential as that is...