Re:The state of JavaScript modules
by pitaj on Monday May 29, 2017 @11:43AM
(#14439642)
When people complain about these things, I just don't get it. If you liked what you were doing, just keep doing it. Sure, Bower is deprecated and you might want to consider switching to an npm-based module fetcher, but every library I've seen still works with AMD.
You can include React in an HTML script tag just like you could jQuery 5+ years ago and use it like that just fine.
The issue with JS is that it's a language used for lots of different things, and one of those things is front-end web development which is, like you said, very unstable and currently in a state of enormous flux.
You say we need to draw a line between the language and the libraries, but then you go on to say the language seems to reinvent itself every year.
You can include React in an HTML script tag just like you could jQuery 5+ years ago and use it like that just fine.
The issue with JS is that it's a language used for lots of different things, and one of those things is front-end web development which is, like you said, very unstable and currently in a state of enormous flux.
You say we need to draw a line between the language and the libraries, but then you go on to say the language seems to reinvent itself every year.