Live data from Hacker News

Parcel v2

parceljs.org

101–103 of 103 posts

Re: Parcel v2

#101
post #100

Earlier quoted context omitted.

Your analogy is laughably absurd. Poop on the street is a public health hazard, someone shoving poop down your throat is assault. Comparing such things to free open-source software is borderline trolling.

Isn't it great that you can refute any analogy by finding a literal difference between the analogy and thing being explained?

Isn't it great that you can defend any bad analogy with a reply that no analogy is perfect? Your analogy makes no sense at all.

Re: Parcel v2

#102
post #76

Earlier quoted context omitted.

Those are some really impressive numbers. I was really impressed with the speed of Vite, which uses Rollup under the hood. I never had any real complains about Webpack's speed until I tried Vite out. In my experience with Vue apps, the difference between Vite (Rollup) and Webpack was much greater than esbuild's data shows.

Vite only uses Rollup for the production build step. During development it uses ESBuild for pre-bundling, and then serves everything as native ESM, that's why it's so fast. They might get rid of Rollup in the future if ESBuild gains more features.

oh, cool! I didn't realize that. Then yea, I am very impressed by esbuild's performance.

Re: Parcel v2

#103

Earlier quoted context omitted.

I don’t think zero configuration is mutually exclusive with full configuration control. Zero config is often just a design exercise in setting reasonable defaults on top of a configurable system.

It could be argued that Vite is zero config because it allows you to go without a configuration file, but it says "zero config" nowhere on the site. It isn't because I want there to always be some configuration that I avoid zero config, it's because I've seen some projects like Next.js reject requests for a configuration setting that I thought were good and it has turned me off to the idea of "zero config". https://g…

I get that. Curious, what do you think of prettier, which appears to philosophically align with next.js based on the issues you linked? Personally, prettier is more palatable specifically because it does one thing.
Post reply on HN