So they are

I don't know. On balance, the reality is cars are better overall nowadays, but every aspect of our life has gotten more complicated, including cars.

If you had the option of no screen at all, no rear-view camera, and with physical switches, would you? If this Slate truck gets released, that's the closest, but it's still required to have a rear-view camera/screen sadly.

It's practically impossible to test every permutation of code against every system. Maybe AI can help, but practically it'll just mean the software gets more complicated, with more features. And to top it all off, more and more features get regulated, so they have to be there. The rear-view camera requirement in particular, since you need a screen to see the output. And if you have a screen... well it's an already paid cost, so, might as well display other things too.

We should kill the reg.

The gains in morale can not be underestimated.

The real world often changes though, and more often than not the code has to adapt, regardless of how elegant are systems are designed.

There will be changes of course. Yet we are also more connected than ever, whereas the next town over would be a whole day trip in the past. The separation allows for more divergence.

Well, maybe if we get to Mars, differences might crop up again.

In some sense, it's better these days, competition has led to care for the reader that probably didn't exist as much then, since so few people can read.

Like how clojure basically uses maps everywhere and the whole standard library allows you to manipulate them in various ways.

The main problem with the many type approach is several same it worse similar types, all incompatible.

I like go's library it's got pretty much everything needed out of the box for web server development. Backwards compatibility is important too.

If anything the heirarchy of trust the Linux model uses will be more important now.

There are definitely challenges, but I've been around long enough now that we'll adapt, and muddle through.

The trouble will come from humans' reaction to the changes, less from the changes themselves

Saves this old man from typing anyway.

But yes, I usually constrain my plans to one function, or one feature. Too much and it goes haywire.

I think a side benefit is that I think more about the problem itself, rather than the mechanisms of coding.

If nothing else, it means Gemini's team has priorities other than the results. Necessarily that means they will lag behind others who have clearer focus

Then the only way for Google to get ahead is to help promote regulation of AI to do what they're already doing. I know it's coming cuz regulators can't help themselves, but No thanks.