Live data from Hacker News

Show HN: Million 3 – Optimizing compiler for React

million.dev

51–56 of 56 posts

Re: Show HN: Million 3 – Optimizing compiler for React

#51
post #19

I met Aiden (the < 20 yo who started Million) a year or so ago. He presented about Million in front of a room full of 40+ grizzled JS devs. I don't personally see any reason to use Million JS, React is fast enough as it is if you memoize and use selectors correctly. Aiden said some similar things at the time (a solution in search of a problem, that got unexpectedly popular) but I gotta say, he's a hype man for sure.…

I feel like this is all missing the points. The point is React is mid. Engineering metric is very strange these days. A guy has made your tool wicked fast, dismissed - fast enough .. wat?

Re: Show HN: Million 3 – Optimizing compiler for React

#52
post #17

I'm not a React dev, so I can't comment on the project itself. Something I noticed on the blog post, though: The image at the top of the page is served uncompressed at a whopping 18.5MB (9751px * 6132px)! Seems a bit extreme for what amounts to a simple logo and some text.

Looks like a job for pure css, or if you are feeling brave, svg!

Re: Show HN: Million 3 – Optimizing compiler for React

#53
post #17

I'm not a React dev, so I can't comment on the project itself. Something I noticed on the blog post, though: The image at the top of the page is served uncompressed at a whopping 18.5MB (9751px * 6132px)! Seems a bit extreme for what amounts to a simple logo and some text.

Yeah for all the complaints about an extra 500Kb of JS, the real offenders are often images.

But don’t forget you need to download and parse the JS and load that into memory. Plus depending on what it does it may be battery intensive.

Re: Show HN: Million 3 – Optimizing compiler for React

#54
post #19

I met Aiden (the < 20 yo who started Million) a year or so ago. He presented about Million in front of a room full of 40+ grizzled JS devs. I don't personally see any reason to use Million JS, React is fast enough as it is if you memoize and use selectors correctly. Aiden said some similar things at the time (a solution in search of a problem, that got unexpectedly popular) but I gotta say, he's a hype man for sure.…

But if it works this is one of those “chuck this in and see if you get a speedup” things, a bit like a platform upgrade for Java or .NET or moving to a new cloud SKU. Devs and managers love this kind of thing. No code just chuck it in and stuff goes faster (assuming that is how it works).

Re: Show HN: Million 3 – Optimizing compiler for React

#56
post #17

I'm not a React dev, so I can't comment on the project itself. Something I noticed on the blog post, though: The image at the top of the page is served uncompressed at a whopping 18.5MB (9751px * 6132px)! Seems a bit extreme for what amounts to a simple logo and some text.

Holy crap you're right, that was a VERY large image, fixed: 18.5MB -> 21KB
Post reply on HN