Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mako – fast, production-grade web bundler based on Rust

makojs.dev

Post reply on HN
Print view View original

51–60 of 215 posts

Re: Mako – fast, production-grade web bundler based on Rust

#51

Post by vmfunction »

norman784 wrote: post #45
bilekas wrote: post #24

Earlier quoted context omitted.

Haven't you heard ? Rebuilding everything in rust is the new meta. To be quite honest, call me old fashioned but the fact we need so many bundlers that we are considering which are more performant is a symptom and and not a blessing.

For me is the fact that we need a bundler is the underlying issue. I would love that bundlers became first class citizens and come already with the Javascript runtime, similar on how Bun and in some degree Deno does (AFAIK their bundler is intended to use to bundle apps to use in the server and not in the browser).

Or change the specs of ES/JS to introduce types. It will eliminate use of many projects and even typescript.

Seems like something to bring to WinterCG ? [1]

[1]https://wintercg.org/

Re: Mako – fast, production-grade web bundler based on Rust

#52

Post by podgorniy »

ecmascript wrote: post #21

Can't people figure out some other tooling besides bundlers? I mean, how many do we really need? It's probably fine, but so are all the others as well. The authors have probably spent a fair amount on time on this project so I don't want to be negative but it's just hard to be excited when it brings nothing new to the table. Why should I use this over Vite or esbuild? Because it's written in Rust? I don't understand…

I've read some faq and docs.

Their reasons are to have fast builder with flexisbility needed for business cases. If other words they are making internal tooling publically available.

Being faster than es-build is not a goal, get people excited about speed is not a goal. Have control over tooling, flexibility, be fast-enough, be opensources are the goals.

Re: Mako – fast, production-grade web bundler based on Rust

#53

Post by tombl »

ToJans wrote: post #18

I've recently taken a legacy Typescript clientside codebase that was using webpack to generate tens of js packages from minutes to seconds by using bun [0] for both dev and build: For dev I replaced webpack with "bun vite": it loads scripts ad hoc and is thus super fast at startup, and it still supports hot reloading. For build I use "bun build". I've created a small script where I don't specify the output folder, bu…

Bun.build actually has a `define:` option that does the same thing as your replace. If you use it, it'll even propagate the value, and treeshake away any `if(import.meta.hot)` you have.

Re: Mako – fast, production-grade web bundler based on Rust

#55

Post by ecmascript »

norman784 wrote: post #35
ecmascript wrote: post #21

Can't people figure out some other tooling besides bundlers? I mean, how many do we really need? It's probably fine, but so are all the others as well. The authors have probably spent a fair amount on time on this project so I don't want to be negative but it's just hard to be excited when it brings nothing new to the table. Why should I use this over Vite or esbuild? Because it's written in Rust? I don't understand…

Why matters that is written in Rust? Because there are already a few JS tools written in Rust, so you can now use the crates from projects like Deno[0], OXC[1], BiomeJS[2], etc to write your own tool with minimal effort. Also note that the Vite team is writing Rolldown[3], and guest what? They are writing it in Rust. [0] https://crates.io/search?q=deno [1] https://crates.io/search?q=oxc [2] https://crates.io/search?q…

Yeah okay, but that's not the reason why people write it in the title. They write it in the title because they know that many engineers like Rust and think people will immedietly be drawn to it.

But the language itself is not a goal or at least shouldn't be IMO. Thus it have the opposite effect on me, who do not care about what language my bundler is written in.

If I did, it still wouldn't have any competitive advantage since as you point out Vite will soon also be based on Rust.

Re: Mako – fast, production-grade web bundler based on Rust

#57

Post by dgb23 »

berkes wrote: post #22
pjmlp wrote: post #17

Everyone is making the point that using JavaScript on the server was a BIG mistake, with this ongoing rewrites. We already had our bundlers in Java and .NET land, before nodejs came to be, and life was good.

The fact that people keep releasing new bundlers, minifiers, transpilers, package managers and so on, for JavaScript is a loud and clear warning that something is amiss. People (re)write such tools either for fun or to solve a problem (or best: both). Apparently after so much re-writes the problems haven't been solved. To me, this indicates fundamental problems. I'm not familiar enough with the ecosystem to know what…

Esbuild did solve a major problem, which was very slow builds.

Vite wrapps esbuild. Not sure what it provides itself.

Then there came several specialized (Rust) tools. For the same reason esbuild was made.

I think ultimately they try to solve the same issue:

JS is supposed to be a productivity gain over compiled languages. But with ultra slow builds that goes out of the window.

Re: Mako – fast, production-grade web bundler based on Rust

#58

Post by [deleted] »

vmfunction wrote: post #51
norman784 wrote: post #45

Earlier quoted context omitted.

For me is the fact that we need a bundler is the underlying issue. I would love that bundlers became first class citizens and come already with the Javascript runtime, similar on how Bun and in some degree Deno does (AFAIK their bundler is intended to use to bundle apps to use in the server and not in the browser).

Or change the specs of ES/JS to introduce types. It will eliminate use of many projects and even typescript. Seems like something to bring to WinterCG ? [1] [1] https://wintercg.org/

[deleted]

Re: Mako – fast, production-grade web bundler based on Rust

#59

Post by mickael-kerjean »

vmfunction wrote: post #51
norman784 wrote: post #45

Earlier quoted context omitted.

For me is the fact that we need a bundler is the underlying issue. I would love that bundlers became first class citizens and come already with the Javascript runtime, similar on how Bun and in some degree Deno does (AFAIK their bundler is intended to use to bundle apps to use in the server and not in the browser).

Or change the specs of ES/JS to introduce types. It will eliminate use of many projects and even typescript. Seems like something to bring to WinterCG ? [1] [1] https://wintercg.org/

That was the initial promise of dart when it was first release but somehow it never got really there

Re: Mako – fast, production-grade web bundler based on Rust

#60

Post by benrutter »

I don't work in web, and possibly live under a rock. I'm a little confused around what bundlers actually do?

I'd sort of assumed it was a typescript build thing before, but Mako's page gives me enough info to make me realise I'm wrong, but seems to assume people are working with some base knowledge I don't have.

Any pointers to information of exactly what bundlers do? The emphasis on speed makes it sound like it's doing a whole bunch of stuff, what are the bottlenecks? Package version resolution?

Post reply on HN