I've had mixed results writing "normal" business logic in c++, but i gotta say, for SQL it's pretty incredible. Granted SQL has a lot of boilerplate and predictable structure, but it saves a ton of time honestly.

It's not artificial at all. It's a real limitation that was so outrageously annoying for the reasons mentioned above that VLC was able to "win" by tackling this one issue alone.

The success of vlc is all the proof you need. As you say, why else would it be so popular?

I'm confused, are you saying that no one can detect if you're smoking or vomiting?

If your management team can't figure out how to do what you're asking, maybe you should be firing them instead. If _no one_ can figure it out, maybe you should be firing you.

You don’t need to pretend to have such an expertise, its fine to admit you’ve never actually handled such serious matters before.

Good for you, i guess? It was absolutely as stupid as they describe. There were multiple teams that were literally interviewing people to join and then laid people off in the middle of it. My own team was trying to fill multiple positions and then they fired one of us (long tenure, good perf) and told us we could hire backfill as long as it wasn't the experienced, useful person we just let go. We explicitly asked and the answer we got was that this stupid shit was somehow protecting alphabet.

Why would you not expect these exact same challenges to develop almost immediately on Mars? It's not like one country will own Mars and even if it did, one country generally cannot agree on environmental policy even internally. I fully expect Mars, at best, to be a terrible version of Earth with all the same problems and way fewer benefits.

When has "This is too hard, let's do a full rewrite" ever worked?

I do honestly prefer using vim over emacs for a bunch of reasons, but I wish it was configured with lisp instead. Emacs seems like a fun playground.

I was just thinking we used traits and enaml quite a lot in the scientific Python community and didn't realize that's what this was pointing to.

As far as using it goes... It was alright. Very very fast to set something up, but has the usual "many things are now easy, but some things are now impossible" problem that many other frameworks introduce.

Depending on the product, the latency difference might not even be visible compared to the every day latency of the backend itself.

If your ui maintains state via some kind of async layer then the latency might not be observable at all.

So many examples of this across Google it's not even funny.