4 ms·
Couple of nits & questions: 1) I'm surprised CSS preprocessors made it as a must, and CSS in JS as only recommended. I figured that would be switched, isn't th
by jastanton 8y ago
Couple of nits & questions:
1) I'm surprised CSS preprocessors made it as a must, and CSS in JS as only recommended. I figured that would be switched, isn't the current golden path CSS in JS?
2) Is webpack a must these days? Can we not just throw everything in typescript? Maybe that's only personal preferences!
3) No one ever needs to know jQuery anymore ;)
Glad to see lodash made it though
- wolco 8y agoDon't throw away jQuery just yet.
- plopz 8y agoEspecially with the way Safari is being developed, I'm guessing we're going to go back to needing a jQuery library to handle all the browser inconsistencies.
- sbjs 8y agojQuery does a whole lot more than just handle browser inconsistencies. I feel like a shim to the standard DOM API would be better suited for solving that problem. The DOM API has grown a lot.
- adzm 8y agowebpack can handle a ton of things that you can't simply do with tsc
- sbjs 8y agoBabel and TypeScript compete. WebPack is orthogonal. WebPack can take your PNG image and inline it into base64-data if it's small enough, or return a hashed filename from your import to be cache friendly but without the caching bugs.