[progx]

The problem in the past was primary browser incompatibility. That was why jQuery exists and was so successfull. Different render output with different css settings was an other problem. But, thank god, since IE dies, this problems are solved for 99% of all use cases.

[gjsman-1000]

I got into a web development a few years ago, and I am so... what would should I use? Almost euphoric that I never had to learn to work around IE6 or Internet Explorer in general; that web browsers mostly support the same feature set now (shame on Safari for still not supporting Ogg, and on Edge for not supporting AVIF), and ECMAScript 6 being widely available is a blessing.

[willtemperley]

In 2006, tech decisions were easy: shall I use jQuery or Prototype.js? PHP or ASP? Postgres or MySQL?

Nowadays, after the long decision process to go serverless I choose Cloudflare from the 13 best serverless frameworks and VueJS from the 30 frameworks they support.

So I choose SPA from the four ways to deploy VueJS. I chose TS over JS. SFCs thank you very much. Setup syntax please! Composition over options all the way.

I'm in the promised land! Types! Components! No server admin! No DB admin! Let's actually make something!

Trouble is, 18 months down the line, the commercial charts library I wanted to use is pretty much unusable with this setup. I've been through about eight dropdown menu libraries. How many person-hours were wasted with abandoned vuejs dropdown menus I wonder!?

It's been easier to write a desktop application to do the same thing in about two months.