4 ms·

You completely omit (conveniently) how browsers have evolved over the past decade, how business requirements have changed (and become more complex) and how npm

You completely omit (conveniently) how browsers have evolved over the past decade, how business requirements have changed (and become more complex) and how npm itself (you could argue the entire JS ecosystem, along with language changes) has changed. Cool, things use to be easier when you were working pre-Node dominance but you weren't shipping the complex interaction patterns that have resulted in the ecosystem we have today. So frustrating to have conversations with those who have no perspective or context on the why and rest on their laurels of old when "things were easier". Good grief.

cxr 4y ago
> You completely omit (conveniently) how browsers have evolved over the past decade Why would I talk about that? The article is about the James Webb Space Telescope, not the James Webb Browser. Aside from that, this is rooted at the mention of "node_modules", which is a NodeJS-ism; browsers don't even run NodeJS modules (unless you recompile them to standard JS), so browsers are doubly irrelevant... > and how npm itself (you could argue the entire JS ecosystem, along with language changes) has changed I didn't omit that. I was very explicit about NodeJS cannibalizing JS. > So frustrating to have conversations with those who have no perspective or context on the why and rest on their laurels of old when "things were easier". You seem to have me confused with someone else. (Talk about "context"!) Where does that quote from? It looks like you made it up.
albertopv 4y ago
In 2008 I adapted an ecommerce web app working only in IE6 to work on Firefox, it used plain XMLHttpRequest with XML api, no json. Parsing XML was a pain. In 2012 I wrote a Bill Of Material web editor for fashion products, 8k lines of pure javascript, embedded in a monstrous legacy web application, still running. Or a datagrid that had to work with IE10 loading 10k rows with client side filtering because the client requested so. Not enormous projects, but things have been complex for a long time, now they are often overengineered, I wouldn't touch FE dev env with a ten meter long pole. Things were much easier with JSF, especially for pure b2b stuff.

cxr 4y ago

> You completely omit (conveniently) how browsers have evolved over the past decade Why would I talk about that? The article is about the James Webb Space Telescope, not the James Webb Browser. Aside from that, this is rooted at the mention of "node_modules", which is a NodeJS-ism; browsers don't even run NodeJS modules (unless you recompile them to standard JS), so browsers are doubly irrelevant... > and how npm itself (you could argue the entire JS ecosystem, along with language changes) has changed I didn't omit that. I was very explicit about NodeJS cannibalizing JS. > So frustrating to have conversations with those who have no perspective or context on the why and rest on their laurels of old when "things were easier". You seem to have me confused with someone else. (Talk about "context"!) Where does that quote from? It looks like you made it up.

albertopv 4y ago

In 2008 I adapted an ecommerce web app working only in IE6 to work on Firefox, it used plain XMLHttpRequest with XML api, no json. Parsing XML was a pain. In 2012 I wrote a Bill Of Material web editor for fashion products, 8k lines of pure javascript, embedded in a monstrous legacy web application, still running. Or a datagrid that had to work with IE10 loading 10k rows with client side filtering because the client requested so. Not enormous projects, but things have been complex for a long time, now they are often overengineered, I wouldn't touch FE dev env with a ten meter long pole. Things were much easier with JSF, especially for pure b2b stuff.