It’s a natural cycle though. New bundler created that is fast and simple to use -> New features are requested and added to the bundler which makes it more sluggish -> New bundler created that is fast and simple.
I wonder how this compares to ParcelJS.
I’m a big fan of Go but there are usually fringe benefits in having the bundler written in the language that it is bundling I.e. JavaScript.
That’s exceptional, if the benchmarks test identical workloads and features I would definitely consider switching to this.
FWIW it may sound like I’m hostile to this framework when I’m just trying to be critical in a constructive way. I use golang as my main driver at work and find most projects in Go to be better then its common counterparts, however I have been through so many JS bundlers that I scratch my head when anyone claims superior results on (Self-declared) hobby ones.
OP should know this seems really solid and like great work. I just don’t want junior devs running head first putting this in production.
I wonder how this compares to ParcelJS.
I’m a big fan of Go but there are usually fringe benefits in having the bundler written in the language that it is bundling I.e. JavaScript.