This approach leads us exactly where we are - having 100x more HW resources, yet page load times still suck ;) And simple request to webdev - would you please make your js app build any faster then 5min always yields the same, confused look - like, where in the mess of 100+ libs should I start?

> "You have to learn the underlying tech in order to use the framework on top of it" just sounds like gatekeeping to me.

Possibly. But if you want to master your craft, you need to learn the “underlying tech.” That’s why we have computer science degrees, after all. Not all programmers have computer science degrees and in many cases, it shows. Someone who understands fundamentals is often more effective at debugging and problem solving when the s* hits the fan.

If you just want to bootcamp it without a deep-dive, that’s fine and I agree with you.

>All of this "You have to learn the underlying tech in order to use the framework on top of it" just sounds like gatekeeping to me.

I might be putting words in GPs mouth, but I read the comments as 'making a swf and embedding it in a HTML file used to be good enough. Now everything is way more complicated'.

I tend to agree with GP. Flash and it's desktop counterparts Delphi etc certainly had their warts but they were much more intuitive on the wetware. Such that accountants and non professional / semipro users could use them.

We made a mistake by throwing them out, when we IMHO should have corrected them or replaced them with less warty programs that we're still using the same paradigm to be easy and intuitive to create.