Probably also during the 2 to 3 migration, but that goal appears to have now been abandoned.

I wonder how the authors of other implementations like pypy will be able to keep up as the reference implementation becomes more and more complex.

Whenever state is updated, the listeners are all called with the updated state and can update the UI and what not based on the new state.

I haven't profiled this and compared it to frameworks, but feels adequate for the relatively simple UIs I've done.

"She was well aware of the hackers’ playfulness around the ninth floor, and she was moderately friendly with some of them, even though they would eventually blend into one collective personality in her memory: one unkempt, though polite, young male whose love for the computer had made him lose all reason."

The kind of problems caught by compile time type checking are less fine grained than those that can be caught at run time. For more exploratory programming, one would prefer the latter.

At compile time, one checks that they are passing around correct types, at run time, the actual logic of the program is exercised.

In 5 to 10 years, we'll see what kind of engineer is produced from pure LLM steering without years of hand coding experience. Even many of the more experienced ones would have some of this skill atrophied.

Let's way you wanted to do a web application using LLMs. Using a web framework would cost less tokens than using the vanilla underlying language (Python, PHP, whatever..), which is again way less tokens than building up from assembly (an LLM should be able to do this given enough time and compute).

There are many companies that compete but are careful not to break laws or cause obvious harm.

Why should a billion-dollar funded corporation still want to externalize the costs of its actions?

Is tech hiring so badly broken? Or do they have such broken processes / misaligned incentives that even people who could be doing a better job in these companies are unable to?

Also, was something lost in the transition from the traditional 'sysadmin' role to 'platform engineer' in the 'cloud native' environment?

If they changed that they'd perhaps become world powers themselves.

Subconsciously we all pick up patterns that we regularly encounter.

I want to build something useful for them but if they let me be too close to the customer, I'll be making important decisions that are supposed to be someone else's job.

I think in the end everyone will be happy. Those who just want to ship, make money and attain status and do not care much for the process will embrace whatever capabilities AI affords them and move on.

Those who get satisfaction from the process and prioritize craftsmanship will also do so and form their own subcultures where this is appreciated.

If software is eating the world as some say, then surely, there can't be just one way of doing software.

Yeah, that's one thing that is definitely noticeable. Online social services basically became data-driven psychology research companies, with the goal being to improve engagement. Every page refresh became an A/B test designed to keep you hooked.