Top all-time · #1720
Stefan Krause
Personal blog · stefankrause.netprogrammingweb
Stefan Krause writes Stefan_Krause.blog(), a personal blog at stefankrause.net about programming and web. Since 2011, 43 different Hacker News readers have linked it 55 times, most often “JS web frameworks benchmark – Round 4”. No feed was found, so read it on the site itself.
Too few sampled comments (28) to say how often HN recommends it.?
Why HN links it
HN readers link Stefan Krause's js-frameworks-benchmark tables and write-ups to compare front-end framework speed and memory use, and older posts on JVM allocation. Commenters mostly cite them as data.
Summarised by Claude from a sample of 28 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- JS web frameworks benchmark – Round 45 people · 6 mentions · first linked 2016-09-13
- JS web frameworks benchmark – Round 65 people · 5 mentions · first linked 2017-05-29
- JavaScript Web Frameworks Benchmark – Round 85 people · 5 mentions · first linked 2018-10-17
- JS web frameworks benchmark – Round 34 people · 4 mentions · first linked 2016-07-08
- /js-frameworks-benchmark5/webdriver-ts/table.html3 people · 3 mentions · first linked 2017-02-05
- C, Java and Javascript numeric benchmark and a big surprise3 people · 3 mentions · first linked 2013-05-02
- Scalar replacement: Automatic stack allocation in the java virtual machine3 people · 3 mentions · first linked 2012-01-25
- JS web frameworks benchmark – Round 83 people · 3 mentions · first linked 2018-09-28
- JS web frameworks benchmark – Round 53 people · 3 mentions · first linked 2017-01-28
- JS web frameworks benchmark – Round 72 people · 2 mentions · first linked 2017-11-21
What Hacker News says?
Here's an answer I found: Vidom ( https://github.com/dfilatov/vidom ) It's faster than React or Angular 2 in one benchmark methodology: http://www.stefankrause.net/wp/?p=218
Comment linking /wp/?p=218
on “Facebook is closing Parse”Submitted A first look at WebAssembly performance as a story · 165 points
HN discussionI'd like to discuss the following comparison in: https://vuejs.org/guide/comparison.html#Angular-2 > Vue 2.0 seems to be ahead of Angular 2 according to this 3rd party benchmark. ( http://stefankrause.net/js-frameworks-benchmark4/webdriver-t... ) The latest benchmark provided is actually: https://rawgit.com/krausest/js-framework-benchmark/master/we... But, Angular 2 is v2.1.1 now, released 2016-10-20. Someone should…
Comment linking /js-frameworks-benchmark4/webdriver-ts/table.html
on “Why we chose Vue.js”Submitted Performance Comparison of JavaScript Frameworks as a story · 112 points
HN discussionIt (v2) is quite fast too http://www.stefankrause.net/wp/?p=316
Comment linking /wp/?p=316
on “Why we chose Vue.js”Submitted JS web frameworks benchmark – Round 7 as a story · 22 points
HN discussionhttps://stefankrause.net/js-frameworks-benchmark8/table.html - thats old lit release there vs react 16 (react pre 16 would be slower and everyone agrees its generally fast already), on slack channel I believe I saw newer release benchmarks that are better (it also depends at which specific test you look at). New version of repeat is interesting: https://slack-files.com/T03PF4L4C-FCY51FZAB-c2fcf32931
Comment linking /js-frameworks-benchmark8/table.html
on “Evergreen: a React UI Framework built by Segment”Submitted JDK 7 GC behavior as a story · 10 points
HN discussion> https://stefankrause.net/js-frameworks-benchmark8/table.html The version of Svelte used there is roughly 100 releases and a year and a half old. These days Svelte's performance appears to be much closer to Inferno's than Preact's. https://krausest.github.io/js-framework-benchmark/current.ht...
Comment linking /js-frameworks-benchmark8/table.html
on “State of JavaScript 2019”Submitted A first look at WebAssembly performance as a story · 5 points
HN discussionhttps://stefankrause.net/js-frameworks-benchmark8/table.html Preact diffs against the real dom and is faster than Svelte in benchmarks while the library is only around 3.5kb (the minified code fits easily on a single screen). I'd note that authors from most of the frameworks represented have submitted their own optimizations, so performance isn't strictly based on the author's familiarity. InfernoJS is massively fas…
Comment linking /js-frameworks-benchmark8/table.html
on “State of JavaScript 2019”Submitted JS web frameworks benchmark – Round 6 as a story · 3 points
HN discussionJust throwing my side project, Surplus, out there as another example of this strategy ( https://github.com/adamhaile/surplus ). Surplus compiles JSX into optimized code that produces real DOM elements. The combination of an ahead-of-time compiler plus no virtual DOM layer means that the runtime code only has to do the minimal, truly dynamic work. As a result, Surplus is the fastest framework in Stefan Krauss's lates…
Comment linking /wp/?p=431
on “Web frameworks are transforming from runtime libraries into optimizing compilers”Submitted JS web frameworks benchmark – Round 5 as a story · 3 points
HN discussionAccording to js-framework-benchmark ( http://www.stefankrause.net/wp/?p=431 ) it doesn't just use much less memory than React, it uses less memory than any other framework, because we don't have the overhead of a virtual DOM. And yes, it's significantly faster. I answered the deduplication point in another reply to the parent, but you make a great point about code-splitting. If you're using a convention runtime fram…
Comment linking /wp/?p=431
on “Web frameworks are transforming from runtime libraries into optimizing compilers”Submitted JS web frameworks benchmark as a story · 3 points
HN discussionUnknown is relative, but here are some of the rss feeds I'm subscribed too: http://nosql.mypopescu.com/ http://lambda-the-ultimate.org/ http://eli.thegreenplace.net/ http://www.stefankrause.net/wp/ http://mechanical-sympathy.blogspot.com/ http://www.cowtowncoder.com/blog/blog.html http://highlyscalable.wordpress.com/ http://hunch.net/ http://perspectives.mvdirona.com/ http://www.scottaaronson.com/blog/ http://www.so…
Comment linking /wp/
on “Ask HN: What unknown technical blogs or sites do you read?”Submitted JS web frameworks benchmark – Round 8 as a story · 2 points
HN discussionNothing beats vanilla JS in terms of DOM manipulation speed. https://stefankrause.net/js-frameworks-benchmark8/table.html And Svelte is fast. It's as fast or faster than React in most synthetic benchmarks. For how and why, see https://svelte.dev/blog/virtual-dom-is-pure-overhead (notably the intelligent compilation step which removes need for vdom)
Comment linking /js-frameworks-benchmark8/table.html
on “Comparing Svelte and React”Submitted JS web frameworks benchmark – Round 8 as a story · 2 points
HN discussionThere has also been some perf work done recently it seems http://www.stefankrause.net/wp/?p=301 I have to look a little closer at the tests to be able to interpret the data but taking it on face value it seems like they are doing good work.
Comment linking /wp/?p=301
on “React: Mixins Considered Harmful”Submitted JS web frameworks benchmark – Round 6 as a story · 2 points
HN discussionI'd like to see evidence for this. the JVM has been great at stack allocation for over a decade [1][2]. [1] http://www.stefankrause.net/wp/?p=64 [2] http://www.ibm.com/developerworks/library/j-jtp09275/
Comment linking /wp/?p=64
on “The State of Go: Where we are in February 2016”Submitted JS web frameworks benchmark – Round 5 as a story · 2 points
HN discussion>I'll bet that React will be a whole bunch faster than whatever DOM reconciliation library you build up from scraps of vanilla JS You don't have to bet, you can verify the results yourself. Look here at these benchmarks [0] and compare, Simulacra.js is 22-42% faster than React v15 (depending on whether you also use Redux or MobX). My "scraps of vanilla JS" performs faster! Vanilla without frameworks/libraries is and…
Comment linking /js-frameworks-benchmark6/webdriver-ts-results/table.html
on “Show HN: Under the hood ReactJS”Submitted Benchmarking JavaScript Web Frameworks as a story · 2 points
HN discussionYou literally said, "complexity is not my problem". You are the problem. This is how projects end up with millions of lines of black box dependencies. This is why `node_modules` folders that are hundreds of megabytes exist. Take a look at benchmarks [0] and tell me, if any framework performs faster than vanilla JS. They probably are faster than vanilla code that you'd be able to write on your own, but that says more…
Comment linking /js-frameworks-benchmark6/webdriver-ts-results/table.html
on “Show HN: Under the hood ReactJS”Submitted JS web frameworks benchmark – Round 4 as a story · 2 points
HN discussionYou're missing the point he's making. Preact is leaner than react. FF was leaner than mozilla. React isn't slow (yet?), but it's not hitting any universal limits, there's always scope for leaner, smaller and faster software (yes it is, see benchmark). benchmark: http://www.stefankrause.net/wp/?p=283 Edit: Added some reference benchmarks.
Comment linking /wp/?p=283
on “Preact, a fast 3k React alternative”Submitted JS web frameworks benchmark – Round 4 as a story · 2 points
HN discussion
