website VS shiki

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

This clarity makes examples more readable and easier to adapt—increasing the chances developers will implement your API correctly the first time. We use Shiki for our syntax highlighting.

shiki — Updated, more powerful syntax highlighting.

Shiki (https://shiki.style) might be good enough for your usecase, use the latest beta versions as it's the new fresh esm rewrite.

Finally the vanguard had arrived. A markdown renderer named Shiki.

Can I introduce you to our lord and savior Shiki? https://github.com/shikijs/shiki

Coincidentally, I recently looked into the slow startup time for shiki and it was mostly from parsing JSONC, not WASM: https://github.com/shikijs/shiki/issues/439.

Warning: This article refers to versions of Code Hike before 0.8.0. Since version 0.8.0, Code Hike uses lighter instead of Shiki. The approach presented in this article uses shiki's color replacement method, which no longer works with lighter.