website VS js-framework-benchmark

Graphics programming analysis done using examples written in WebGL–genius. Hypertext that takes full advantage of the medium. This reminds me of something I'd see on https://pudding.cool/, but it goes far more in depth than anything there. Absolutely fantastic article.

I've been using MSAAx4 in my rendering engine for some time and only recently have considered switching to a FXAA / TAA implementation. I'm actually not sure I'm going to go through with that now. I definitely learned a lot here, and will probably use the analytical approach for UI items, I hadn't heard about that anywhere.

Not often you see graphics-programming stuff on HN. For anyone interested in more graphics write-ups, this list of frame breakdowns is one of my favorite resources:

https://www.adriancourreges.com/blog/

I think NY Times started long back and this style was kinda "cool" that goes well with the narrative. Then, there is https://pudding.cool that does this pretty well. Now, many just copy and tries without a meaningful treatment and is just there - kinda not working-out in most cases.

Tip: Try reading with Reader Mode.

Also check out https://pudding.cool if you’re unfamiliar and enjoy extremely high effort visualizations alongside editorial and educational text content.

Hello all, I am a JS beginner and I am passionate for creating data-driven stories on a website, like Pudding. I have watched some YT videos and learned that Python is a basic skill for dealing with data. However, I am confused about what Python does in such website? I know JS and it libraries like D3.js are used for front-end development and interactive data display, then what's the role of Python? For the website backend (such as Django)? Or is used for data cleaning and analysis? Or others? Or python is not actually required for making a data-driven story website?

https://pudding.cool/ ?

The main reason why I've got interested in frontend is that (1) it seems to be a field that can be much more diverse and collaborative across different fields (ex: working with designers) and (2) it directly interacts with users. Interactive journalism, data visualization, data storytelling (as in The New York Times or The Pudding) are my main interests currently, so it is more accurate to say I got interested in frontend with focus on those specific fields.

pudding.cool, statistical analysis of things like rap lyrics

I had similar concerns when I made the jump from a custom data class (with methods like `set`, `get`, `increment`, `push`, etc) to a transparent `Proxy` around native JavaScript objects. I did some quick benchmarks back then, and concluded that it was actually not meaningfully slower. Modern JavaScript engines are awesome! :-)

Aberdeen is not in js-framework-benchmark yet, but I've done a pull request https://github.com/krausest/js-framework-benchmark/pull/1877 -- By my own testing, performance is similar to something like react (while of course destroying React on time-to-first-paint, bytes transferred, etc). However, this test is not a particular good fit for Aberdeen, as lists in Aberdeen are always sorted by a given key (it maintains an ordered skiplist for the data). The test only requires the easy case: sort by creation time. So Aberdeen is doing some extra work here.

With regard to reactive data transforms: Aberdeen provides some (reactively 'streaming') helper functions for that (`map`, `multiMap`, `partition`, `count`). But these are mostly based on the `onEach` primitive, for reactive iteration. Take a look at the `map` implementation, for instance: https://github.com/vanviegen/aberdeen/blob/a390ce952686da875...

Is past projects, we've been using things like this a lot. Pretty easy and fast!

I have a number of ember projects on vite if anyone wants to take a look:

- https://github.com/krausest/js-framework-benchmark/pull/1835...

📌 Benchmark: In the JS Framework Benchmark tests, Vue shows very good handling of rendering and DOM operations, positioning itself between React and Svelte in terms of speed.

i do a lot of JS benchmarking and whole-program measurement is key. sometimes optimization in one hotspot changes the whole profile, not just shifts the bottleneck to the next biggest thing in the original profile. GC behaves differently in different JS vms. sometimes if you benchmark something like CSV parsers which can stress the GC, Benchmark.js does a poor job by not letting the GC collect properly between cycles. there's a lengthy discussion about why i wrote my own benchmark tool for this purpose [1]. i can recommend js-framework-benchmark [2] as a good example of one that is done well, also WebKit's speedometer [3].

[1] https://github.com/leeoniya/uDSV/issues/2

[2] https://github.com/krausest/js-framework-benchmark

[3] https://github.com/WebKit/Speedometer

This article was inspired, of course, by my experience working with the js-framework-benchmark repository, which, in my opinion, very clearly shows why speed is important today. In fact, people want websites to load faster - that's a fact. Today, most modern popular frameworks and libraries are slow in fact. It may even seem to someone that speed is crap, but it is not. If you put everything together, then with such "optimizations" web applications will work several times worse. Therefore, I think that something like this.

Hey everyone! I spent 2.5 years solving the speed problem in the js-framework-benchmark repository, and I don't regret it, because there is a super interesting observation that I recently noticed.

You can compare performance in a more rigorous way by consulting Stefan Krause's js-framework-benchmark project. Here are results based on the latest snapshot: