problem seems to be [...] intertwined language with culture
You lost the argument right here. Language is as fundamental to culture as the sky is blue.
The rest of your post amounts to "communication is important to function" and you are not wrong on that front. But you put no weight on the importance of culture too.
Consider this your wakeup call, that just because you don't personally care about society having an identity doesn't mean the rest of us don't.
The carbon sequestered in the earth in the form of coal, oil and gas hasn't always been in the earth. After all, hydro carbons are in fact hundreds of millions of years of dead trees buried under mud sequestering atmospheric CO2. Which implies there was a time with all that CO2 in the air yet still trees to capture it. By releasing it all, we reset the biosphere's clock to about a time when earth supported a different kind of life (one without us in it), but life nonetheless.
Frankly, the comparisons to Mars and Venus seem a bit overblown.
I used to be html and css-first, and to some degree I still am, but the advantages of SPA, lazy load, hot reload, and automatic state management and Dom rendering of a JS based framework are just too awesome to forego for the sake of staying native.
I know about HTMX but it's not really JS-less. It just creates the illusion that no JS is written. It still gets implemented in the browser with JS.
That's a weird way of saying that all manufacturers will from now adhere to the NACS or SAE J3400 charge standard, further breaking down the barriers to locked in--or monopolized--charge networks. It's also a very weird way of saying that a common charge standard will further diversify stakeholdership in an already pretty diversified charge network stakeholdership ecosystem.
Typing characters is maybe 1% of the job. The other 99% is understanding how the change affects everything else. Changing a single line of code in a function called by 1000 other functions each themselves called in 10 other functions can still potentially be more work and a bigger change than changing 9000 lines of code in a function called once.
Professional engineering is really about implementing processes and procedures that create reliable and dependable systems. Ultimately it's about responsibility and risk management. Being an engineer has nothing to do with understanding or implementing technology or technical details and specifications (unless you are in an extremely junior level engineering position). That work already has another title: that's called being a technologist (and there ain't nothing wrong with that title and that work).
Very, very, very few technologists (including self-taught programmers, computer scientists, and even some engineering grads) have, or even understand the skills needed to manage technical risk, simply because those skills are not part of any of those curriculums and the licensure required to be recognized to conduct those activities. It requires knowledge, training, and certification specifically, not just a university degree or x years on the job. Of course, it's not the sort of distinction that the general public understands by "engineering" since the public kind of just takes the act of technical risk management for granted.
Conversely, it's perhaps also why the number of engineers with hands-on skills is shockingly lower than we expect: using technology is not on the engineering curriculum.
But yeah, just because the general public confuses technical skills with engineering doesn't give you, lacking all three of : an accredited engineering degree, an engineering licence, and perhaps most importantly, malpractice insurance, licence to call yourself an engineer.
Damn, these are savage.
To be fair, robots kinda wear out over time too, arguably at a faster rate. At least living tissue can self repair.
I think you missed the part where the person you are replying to is talking about the ethics of the platform itself, not the ethical viewpoint of the users using the platform nor the personal views of the developers.
But it makes sense in the grand scheme.
How? Signal doesn't have the leverage to get the bulk of users to stop using SMS. So all that move did was to force people to reinstall an SMS. Then, signal became yet another messaging app for like one contact to manage and forget about.
Matrix does what signal does, but it's distributed, unlike Signal. Plus you have protocol portability.
You are not wrong about the lack of corporate culture. But at the end of the day, is that worth giving up family time, company of your pets, a corner office of your choosing, with access to your own fridge and amenities, being able to receive people at the door at reasonable hours, and not having to commute asinine hours?
Many people will reject that notion.
But here's the kicker: companies don't care about your well being. They only care about the bottom line. What incentive do they have to cater to your needs? None, other than the minimum for employee retention.
This idea of "team building" is just smoke and mirrors. An excuse to not have to admit the real reason: adapting away from buts-in-seats as a performance measure is hard.