I find Swift very bad for churn. Swift has had 5 versions in 5 years, with breaking api changes each time.
Every answer on Stackoverflow about Swift has several answers, one for each api version. Any time you grab some Swift code from the web or an older project, it's not going to work.
Avoiding the churn isn't an option since new Xcode versions drop support for old Swift versions. And only the two latest Xcodes will run on latest macOS. They even drop the support for the conversion tools. So if I go back to an old Swift project now, it won't compile in my Xcode, nor will my Xcode help convert the code to modern. My only option is to run an order version of Xcode in a VM to convert the code.
If I'm writing a library I want other people to use or share between projects, I'll still do it in Objective-C. Apps I do in Swift but I find it annoying.
I still have 15 year old non-ARC Objective C libraries. Why spend the time updating them when the are debugged and work fine?
Every time I have to do a Swift version update I introduce bugs.
Linux as narrowly defined as the kernel is very good at not breaking things. Linux as used in common speech to mean a Linux distribution and associated libraries undergoes constant churn.
I maintain a cross platform desktop app for Windows, macOS and Linux.
Windows is the best, 32 bit versions going back 15 years still work no issues. macOS is next, 32 bit don't no longer work, but 64 bit versions still work going back 5+ years. Ubuntu is by far the worst, some library I depend on changes it's API pretty much every year, and the old version is removed, breaking my app.
The solution appears to be Flatpak which bundle up the app with all it's required libraries. However I'm not sure how to make this work for plugins. Would each plugin need to be in it's own Flatpak? It's insane.
The country I don't understand how they do it is Bangladesh. A country the size of New York State with 164 million people. (50% of the US population). As I understand it, they generate 90% of the food they require.
When I was injured in 1991, they transplanted nerve sheaths from my leg to my arm with the hope nerves would regrow. Some actually did an I regained some sensation and movement.
That was considered pretty good at the time. I wonder how much better off I'd be if I'd been injured today instead.
I think Lisp failed because it had no killer app. Most developers don't pick a language, they pick a project and the select the most appropriate language.
Web frontend -> Javascript
Unix / Linux -> C
Wordpress plugins -> PHP
Windows apps -> .Net
iOS -> Objective C / Swift
Android -> Java
In my entire career (25 years), I've never had a project that directed me towards learning Lisp. This pretty much leaves Lisp to the type of developer that seeks out new languages and is willing to spend the extra effort integrating, and that's a pretty small number of developers.
If Lisp was in the browser instead of Javascript, it would be popular no matter the complaints about the language.
I think another thing is that governments have lost a lot of their power and are now somewhat controlled by corporations. This is usually assumed to be a bad thing, but most corporations don't like war, it's bad for business. It disrupts supply chains, kills customers, and generally makes things unstable. (Except for military contractors, but they seem to do well if there is a war or not).
I think climate change could bring another big war, because then wealth will become food and water, and that can be taken by force.
Isn't that pretty much what happened with GM? The stocks and bonds were all wiped out. And then the new GM was owned by the government / union until they did an IPO a few years later?
There is very little downside to putting a bigger motor than needed in an EV, other than a bit of extra weight to move around. As long as you don't use that power, (fast acceleration), you won't pay for it.
That said, 221 lb-ft of torque isn't very much. They don't say at what rpm that is. Most EVs are electronically torque limited at low rpm. Assuming the peak torque is around 2000 rpm, that's only 84 hp.
(My biggest pet peeve is torque without rpm -- it's meaningless!)
.apps aren't really analogous to the registry, they are more like the contents of the Program Files directory.
On macOS, the registry equivalent is all the plist files stored in ~/Library/Preferences and ~/Library/Application Support. These just get left behind when the .app is deleted.
Just don't get into writing synths or effects if you want to make any money. Kind of like making games, it's flooded with people who do it for the love and willing to do it for salaries far less than other fields. The stereotypical musician has no money. There are currently over 3000 synths listed on KVR. It's tough to do something unique and stand out.
I think the most useful thing for me is I can call it from lldb and immediately dump buffers to my terminal while debugging.