Agreed. I find that we're going in this direction in many areas, games just got there much faster.
Pretty much everywhere there is some undercurrent of "use this ultra-small generic interface for everything and life will be easier". With games and ECS, microkernels and IPC-for-everything, with frontend frameworks and components that only communicate between themselves via props and events, with event sourcing and CQRS backends, Actors in Erlang, with microservices only communicating via the network to enforce encapsulation... Perhaps even Haskell's functional-core-imperative-shell could count as that?
I feel like OOP _tried_ to get to this point, with dependency injection and interface segregation, but didn't quite get there due to bad ergonomics, verbosity and because it was still too easy to break the rules. But it was definitely an attempt at improving things.
Entity-component-system paradigm. Compared to OOP, ECS is more "data-first". It's like a database of components (attributes such as Position, Velocity, Player) with entities (simple integer identifiers) as keys. Systems are functions that query for components and perform actions on them. See Shipyard, enTT, Bevy, flecs, etc. The design space is still evolving.
on rear suspension bikes with a changing chain length you need something to account for that change in chain length so it doesn't go floppy at certain points of the rear swingarm motion.
I'm not sure Australia has a land problem in general, population density is quite low (I understand that a lot of the land doesn't support high density living). They have an issue in that their major cities have some constraints on perpetual outwards growth. Maybe this will help encourage remote work and relocation of offices to places that aren't the core downtown area of Melbourne and Sydney?
This comes up often in these discussions but, barring any indigenous lands, there's nothing especially inhospitable about central aus. Las Vegas is in the middle of a damn desert, and Arizona/New Mexico are both extreme climates compared to much of the US but they are still livable and many people actually prefer it. I can't see why this would be any different in Australia...
It’s not about how possible it is to live, it’s about places people actually want to live. There is virtually unlimited land with good climate. But people don’t want to live there because it’s far from everything. Most people have picked paying more to live closer to events, jobs, stores and friends.
Australia doesn’t have the population to start a new major city in the center. There are still multiple cities like Adelaide which could grow instead.
Isn't this a tooling and knowledge issue?
If I was as productive with TLA+ or model based design as I am with React-Native/Ionic/Swift etc. then we could have a smartphone weather app written to those standards for the same price.
While there's plenty of room for improvement, I legitimately believe that TLA+ is now in a place where it's convenient enough to use in conjunction with Ionic/Swift.
