In my dream world, the software meant to keep everything running would be open source so that people who also share this view can help shoulder the burden rather than leaving it for a handful of people. I can't imagine the difficulty of being the face of legal threats (most frivolous), criticism for the fact that you host a free speech forum, and deal with managing the back end.
Thing is, that's how software used to be. There used to be a dogmatically apolitical culture of collaboration and sharing in open source. People took Stallman's sperging as gospel and internalized it. Those people also happened to be super autistic themselves. Autism for these ideals held it all together.
Except then came gender nonsense (and other stupid woke politics). Gender nonsense sapped that autism, so it couldn't at least be used productively. Trannies are like termites.
Now software is falling apart and you've got dipshits writing software licenses that say you can't use the software if you're mean.
The only light at the end of the tunnel is that the legal system is still as autistic as software used to be, and so the remaining people who still believe in old open source values can still use the good licenses (AGPL would be most appropriate for web software), and won't have to worry about the project being hijacked.
Trannies that already control a project can destroy it, but if all they can do is fork it (which they can legally do), things will be fine. The flip side of trannies being termites is that they don't have the determination to take a good project, relicense it (as far as they legally can), and develop it extensively enough to displace the original project.
That's what it would take for trannies to take over a project with a good license: basically extend the original project far enough that all the new users go to their version instead of the original, and then lord over that new version as their terrible woke domain.
But they can't do that, because trannies cannot create, they can only destroy.
Example: the
node.js COC salt. Some trannies and chasers got cranky that the project wouldn't boot a contributor for their off-project comments. So they ended up forking node.js calling it ayo.js. They had a gay old time sperging about the project's "values" and little time actually coding. The conclusion was that
ayo.js has not seen any activity since end of year 2017.
Also for any non-programmers (read: neurotypical) people, if any of this piques your interest,
there's a good thread on programming drama.
I'm surprised there's no Community Watch thread for Hacker News. That site should be listed as an example on the Dunning-Kruger Effect Wikipedia page. It is full of smug morons who believe themselves to be programming geniuses (and geniuses in everything else) yet can't pass any interview that asks them to actually code. Many of them have no sense of shame and post under their real name.
The one positive to Hacker News is that they still embody the Stallman autism better than most programming forums out there. At least that seems to be the case last time I was linked there.
RE: language choice, it really doesn't matter these days. If your tables are set up right and you're avoiding basic access mistakes, you can pretty much coast on efficiency thanks to index merging in modern dbms. The time it takes to pull the data out to process is always going to dwarf the time it takes to actually process, unless you're doing something really crazy with the data, or accessing at TON of data at once.
I'd care about the choice of language more for security and speed-of-development reasons than performance. Languages that can catch broader categories of mistakes help you avoid potentially critical fuckups earlier and easier. So like type checking.
For many classes of projects: mandatory type checking > optional type checking > no type checking.