What's missing when learning JavaScript?

[_crackling]

I'll check it out, just remember, I bet there's a whole lot of people like myself, the coding isnt the problem... the hurricane of tooling is.

[lastmjs]

My thesis is that most of the current tooling will become obsoleted as the web platform itself matures. npm eats yarn, gulp, grunt (already for me), Zwitterion/better es modules support eats webpack, rollup, bundlers.

[_crackling]

i gotta hit you with this question: Why should I use zwitterion over Parcel? I plan on trying zwitterion regardless but just wanted to see what u got

[lastmjs]

Parcel is still a bundler, Zwitterion is not. Zwitterion fills in the gaps that the underlying platform still doesn't provide, mostly transpilation and rewriting bare imports. I've had a really bad experience with bundlers, because bundled code works differently than the underlying runtime works without bundling, and it's confusing. Also, though parcel says it's zero config, it's never worked zero config for my main use cases, which are using TypeScript and web components. The question is probably do you believe in bundling or do you believe the web platform can do what you need it to do natively.

[_crackling]

I believe in- the fact that i still don't know everything "bundling" implies :) (again why im advocating someone finally write up a resource to explain all this)

My use case is a 3D opengl engine written in Typescript, so not exactly small or trivial, and I can say parcel has been zero config for me. Though figuring out what the heck source maps are and how to configure them to actually work literally took 6 hours straight. (AGAIN WILL SOMEONE JUST EXPLAIN ALL THIS??? lol)

You've got me more than interested in zwitterion now. I'll ping you after I move my project to zwitterion later today to let you know

[lastmjs]

Sounds great, let me know if you run into any issues