VIA is Chromium-only because of WebHID which, last I checked, isn't even on the standards track. I don't blame Mozilla for that. The API is useful but I don't want Firefox just implementing whatever Google decides to try to railroad into web standards.
I'm with you on Mozilla removing the ability to install PWAs on desktop though. Strange that they'd ditch it on desktop but not mobile.
I've been teaching web dev for ~10 years, I learned early on that with JavaScript, the programming fundamentals need to be introduced in bits and pieces. The class hits a wall otherwise. As much as I would like to focus on programming fundamentals first, a class of adults needs to know and get hands-on experience with the why asap to keep them engaged. So I introduce some DOM basics early like the author outlined (except for the last two items).
It also really depends on the profile of the students themselves. I teach at a coding bootcamp now where we also have short courses on just front end web development. The bootcampers are typically more amenable to a front-heavy, bottom-up, fundamentals-first approach. The short-course students need more hand-holding.
Something like Next.js for JavaScript would be better. Express is too bare-bones for OP's criteria. It's bring your own batteries. Just trying to choose from all the batteries available is a full-time job.
> As for Ars, they used to have a journo that would publish 10+ page reviews of the latest Mac OS release, and the dude had an extensive knowledge of Apple and Apple products.
John Siracusa. He left Ars ~5 years ago, I think. Even after I switched away from OS X, I would still read his reviews.
After the big dump of new features in ES2015, I don't find the pace of planned updates to the language aggressive at all. JavaScript is still playing catch up.
People will complain if they don't add features. When they do add new features, people complain that they're "bloating" the language or moving too fast. Damned if you do, damned if you don't.
What do you think would be a better title? I read "web apps" I think html, css, and js. I wasn't expecting (nor would I want to) to ship Python to the browser.
That might be what's being lost in translation here. Python is the development language. If we're to analogize, HTML/JS/CSS would be the runtime stack. Perhaps this is what's lost on mruniverse
Yes, for cases when an existing widget doesn't do what you want it to do.
You seem pretty steadfast in your commitment that this post misrepresents its content. I believe you should give it a deeper review and reevaluate your understanding.
I'm with you on Mozilla removing the ability to install PWAs on desktop though. Strange that they'd ditch it on desktop but not mobile.