Live data from Hacker News

Mako: Fast, production-grade web bundler

makojs.dev

31–38 of 38 posts

Re: Mako: Fast, production-grade web bundler

#31
post #26

Earlier quoted context omitted.

Due to that caching, you still need some sort of preprocessor to digest the files and generate an import map. Third party modules also add some extra friction. I found that when I ended up pruning out all the edge cases, just bundling it ends up being less work anyway.

> Due to that caching, you still need some sort of preprocessor to digest the files and generate an import map. Why? I haven't needed import maps at all. > Third party modules also add some extra friction This is true, sometimes 3rd party JS requires you write a small ESM wrapper, etc, but I haven't found it to be too onerous

If you import a module by its path or URL, it is cached by that path. So if you update a file, browsers that have already pulled that module will get the old version. Getting around this needs some sort of digest. To import that file, you need to either use an import map to get the proper digested file or a preprocessor step to substitute the digested name into the importing module.

Re: Mako: Fast, production-grade web bundler

#32
post #29

Earlier quoted context omitted.

> I don't want to use NPM for my project. I used to feel that way coming from the Ruby / Rails ecosystem, but ultimately I settled leaned heavily into the "convention over configuration" maxim and try my best to adhere to front-end conventions, thereby following the principal of "least surprise" when it comes to wiring up any oddball bits, bobs, or libraries. Lots of Javascript libraries come as Rubygems, and they ar…

We have come to the juncture where hosting a small bit of JS functionality requires a giant swamp^Wecosystem of bundlers, transpilers, packaging systems, and specialized servers. All in the end to serve pieces of static content. It's mind boggling. Yes, you could just go it alone and do your own NPM-less JS, but you really will be mostly on your own. Once you wander into front-end development, the assumption is you l…

The nodejs ecosystem can be quite elegant, convenient, and fun! It's not at all where it was ten years ago.

> All in the end to serve pieces of static content. It's mind boggling.

This is doesn't sound like an adequate justification for the investment of complexity tokens. I'm guessing it wasn't your idea!

Re: Mako: Fast, production-grade web bundler

#33
post #14

Earlier quoted context omitted.

Rust signals fast, modern, and correct. It's absolutely a badge. You should give the language a try when you've got a spare weekend.

I think this blind evangelisation is absolutely an anti-badge and quite cringey. The quality of a program depends entirely on the people writing it, no language will automagically make it “correct”, whatever that means. “Fast” can be achieved in pretty much any language and “modern” also doesnt really mean anything in terms of code or application quality.

I understand your point, but no one's saying its fast because it's Rust.

Rust also has a decent open-source community, so adding this to the subtext will maybe encourage people to help development

Re: Mako: Fast, production-grade web bundler

#34

Earlier quoted context omitted.

I think this blind evangelisation is absolutely an anti-badge and quite cringey. The quality of a program depends entirely on the people writing it, no language will automagically make it “correct”, whatever that means. “Fast” can be achieved in pretty much any language and “modern” also doesnt really mean anything in terms of code or application quality.

I understand your point, but no one's saying its fast because it's Rust. Rust also has a decent open-source community, so adding this to the subtext will maybe encourage people to help development

The parent clearly said fast because its Rust…

Re: Mako: Fast, production-grade web bundler

#35

Mako is also a Python templating library. I have used Mako primarily since it was what reddit used to use back in 2016. Not sure if reddit still uses it.

Also an embedded server[0] and a PHP framework [1]. [0] https://makoserver.net/ [1] https://makoframework.com/

I think projects with short names need suffixes in order to not be confused with others that most likely share the name, these make sense and tell you exactly what they are.

Re: Mako: Fast, production-grade web bundler

#36

There are so many solid web bundlers that all offer a similar feature set, I am pretty skeptical that another entry is all that beneficial. It's good to have choices, but it's become difficult to keep up with such a fragmented ecosystem. I also admit that I am biased. I started using vite a couple years ago and since then have never run into any serious issues with my frontend builds/developer experience. If the main…

We need tech empowerment benchmarks for all these bundlers.

Re: Mako: Fast, production-grade web bundler

#37

Earlier quoted context omitted.

I understand your point, but no one's saying its fast because it's Rust. Rust also has a decent open-source community, so adding this to the subtext will maybe encourage people to help development

The parent clearly said fast because its Rust…

Rust is a solid technology choice for all of the aforementioned reasons. Nobody should be tip toeing around technology to satisfy language haters.

This anti-Rust hate is incredibly bizarre. It feels like the anti-Linux folks in the 00's who would decry any non-Microsoft tech choice, as if Linux was an affront to their career choices.

There are a multitude of reasons people are happy to use and evangelize Rust. It's a fucking incredible language, for one. Labeling your software as written in Rust looks a whole lot better to most people than software written in Perl or LOGO or C++.

Get over your hate. The only person it's hurting is you.

Re: Mako: Fast, production-grade web bundler

#38
post #37

Earlier quoted context omitted.

The parent clearly said fast because its Rust…

Rust is a solid technology choice for all of the aforementioned reasons. Nobody should be tip toeing around technology to satisfy language haters. This anti-Rust hate is incredibly bizarre. It feels like the anti-Linux folks in the 00's who would decry any non-Microsoft tech choice, as if Linux was an affront to their career choices. There are a multitude of reasons people are happy to use and evangelize Rust. It's a…

The aforementioned reasons are vague and meaningless in a technical sense, since they could be used to describe any other language as well. There are lots of "solid technologies" out there, not just Rust.

And no, I don't hate Rust, and I don't really care about Rust, or if a project/library is written in Rust or whatever, if it fits the bill, I will use it.

If you tell me a real argument why using Rust here is beneficial instead of the vague reasons described here, then I'm happy to listen.

If there are no reasons then that is also fine, then it seems like it was used because of a personal choice, experience or other constraints that we don't know.

If you are deeply in love with Rust or any other language then thats also fine. And I also get that Rust is great in many situations, like replacing low-level C code, etc.. But stop putting it on a pedestal if there are no real reasons to back that up (in this case).

Post reply on HN