5. Where in npm (I've no clue what that is) can I find: 1. a calendar widget to put on my page? 2. an email, password, confirm password form to put on my page?
You're not getting his point.
5. Where in npm (I've no clue what that is) can I find: 1. a calendar widget to put on my page? 2. an email, password, confirm password form to put on my page?
You're not getting his point.
2. That's literally what web components are for. Read OP's post. We will have <calendar-widget> and <login-form> and many more custom elements with plug-and-play functionality.
Basically the current state is that everyone knows that HTML/CSS/JS sucks (by sucks I mean not adequately productive to work in, relative to the feature demands of modern web applications), so we're building languages that compile to them so that we don't have to write them directly. JS is becoming like the assembly language of the web. Some cool stuff has come out of that, but it doesn't mean we should give up on trying to make HTML/CSS/JS better. They were designed to be written by humans, so we shouldn't need to compile to them in order to be productive.