The JS community is in pretty deep denial today. CPUs won't get faster soon enough to keep the current levels of JS emissions from totally suffocating the mobile web, at which point we'll be the next generation of Cobol programmers -- essential, but not the future. https://twitter.com/malchata/status/1179811899959066625 …
-
-
I am naively hopeful that import-maps + node's ESM loader removing a ton of dynamism will move us towards much more shared code and much less of a need for tooling.
-
it’s the right foundation for sure, we just need some more time to fill in the gaps.
End of conversation
New conversation -
-
-
I could be wrong but I still feel like this is a problem that could be relatively trivially solved and is ripe for progress. Enabling npm (or your favorite package manager) and Node.js only use code that's actually *used* instead of bundling is absolutely possible, no?
-
This of course requires (heh) you to rethink certain fundamental aspects of both Node.js and npm at present, but I don't think that's such a wild approach nor necessarily a breaking change.
- 2 more replies
New conversation -
-
-
How would the cost be more direct in any other system?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
this sounds more like a webpack complaint than an npm complaint, but point taken.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.