Top all-time · #3907
Marvin Hagemeister
Personal blog · marvinh.dev/blogprogrammingweb
Marvin Hagemeister's personal blog at marvinh.dev covers programming and web. Since 2022, 20 different Hacker News readers have linked it 26 times, most often “Speeding up the JavaScript ecosystem – Polyfills gone rogue”. It is still writing: the last post was on 2026-05-17, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link Marvin Hagemeister's writing on JavaScript performance, including the polyfills-and-bundles problem and profiling the JS ecosystem with flame graphs. Few comments discuss the posts directly.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Web presense of Marvin Hagemeister who is a core developer of preactjs
Most-linked posts?
- Speeding up the JavaScript ecosystem – Polyfills gone rogue3 people · 3 mentions · first linked 2023-09-21
- Speeding up the JavaScript ecosystem - npm scripts3 people · 3 mentions · first linked 2023-03-19
- Speeding up the JavaScript ecosystem – one library at a time3 people · 3 mentions · first linked 2022-11-29
- Birth of 86-DOS2 people · 3 mentions · first linked 2023-02-05
- Speeding up the JavaScript ecosystem part 2 – Module Resolution2 people · 2 mentions · first linked 2023-01-16
What Hacker News says?
I'm sorry, but this is just incorrect. Have you ever heard of ljharb[0]? The NPM ecosystem is rife with polyfills[1]. I don't know how you can make a distinction on which libraries would be used for "local scripting" as I don't think many library authors make that distinction. [0] - TC39 member who is self-described as "obsessed with backwards compatibility": https://github.com/ljharb [1] - Here's one of many articl…
Comment linking /blog/speeding-up-javascript-ecosystem-part-6/
on “GitLab discovers widespread NPM supply chain attack”Submitted Speeding up the JavaScript ecosystem – Isolated Declarations as a story · 45 points
HN discussionGenerally very few people care, unless it’s "an impact metric" tied to that team. Or there is a "performance sprint" or something. "DX" has been more important than "UX" in the current mainstream JS community for a while. To give an example: babel, that enabled syntactic sugar, also caused many versions of runtime implementations of various ES6+ syntax to end up in bundles, or polyfills for browsers the clients aren…
Comment linking /blog/speeding-up-javascript-ecosystem-part-6/
on “Enhance WASM: Back End Agnostic SSR for Web Components”Submitted Speeding up the JavaScript ecosystem – Polyfills gone rogue as a story · 33 points
HN discussionThis is a really nice post and series. I'm curious how you're doing the profiling and then generating the flame graphs e.g. in https://marvinh.dev/blog/speeding-up-javascript-ecosystem/ . Is this Chrome's built-in devtools being used or something else?
Comment linking /blog/speeding-up-javascript-ecosystem/
on “Speeding up the JavaScript ecosystem – Polyfills gone rogue”Submitted Speeding up the JavaScript ecosystem – Semver as a story · 23 points
HN discussionBack then network speeds were less and latency higher. Sending a runtime to the client and reducing the network traffic thereafter was a big win back then. Over time the network has improved, removing the benefit of the reduced network traffic. We still pay the runtime performance impact though. Its morphed into what modern frameworks are today and the original benefit was forgotten. Execution times have only gone u…
Comment linking /blog/speeding-up-javascript-ecosystem/
on “Google ending Basic HTML support for Gmail in 2024”Submitted Speeding Up the JavaScript Ecosystem – Server Side JSX as a story · 15 points
HN discussionSubmitted Speeding up the JavaScript Ecosystem: JavaScript plugins for Rust tools as a story · 5 points
HN discussionSubmitted Speeding up the JavaScript ecosystem part 2 – Module Resolution as a story · 4 points
HN discussionSubmitted Speeding up the JavaScript ecosystem – The barrel file debacle as a story · 3 points
HN discussionSubmitted The missing link in JavaScript tools as a story · 2 points
HN discussionSubmitted Building from First Principles as a story · 2 points
HN discussionSubmitted The modern way to write JavaScript servers as a story · 2 points
HN discussionSubmitted Birth of 86-DOS as a story · 2 points
HN discussionSubmitted Speeding up the JavaScript ecosystem – Tailwind CSS as a story · 2 points
HN discussionSubmitted Speeding up the JavaScript ecosystem – draft-JS emoji plugin as a story · 2 points
HN discussionSubmitted Speeding up the JavaScript ecosystem - npm scripts as a story · 2 points
HN discussionSubmitted Speeding up the JS ecosystem - npm scripts as a story · 2 points
HN discussionSubmitted Running 1000 tests in 1s (JS) as a story · 2 points
HN discussionSubmitted Speeding up the JavaScript ecosystem part 3 – eslint as a story · 2 points
HN discussionSubmitted Signals vs. Query-Based Compilers as a story · 1 points
HN discussionSubmitted Running 1000 tests for Preact in 1s as a story · 1 points
HN discussionSubmitted Speeding up the JavaScript ecosystem scripts as a story · 1 points
HN discussionSubmitted 30% speedup to the JavaScript ecosystem by optimizing module resolution as a story · 1 points
HN discussionSubmitted Speeding up the JavaScript ecosystem – one library at a time as a story · 1 points
HN discussion
