murzynalbinos

This is nice. And yeah, I've crashed after 33 sec ;)

Same feeling. Besides, it took me a while to figure out which car was mine

The days of youth and internet cafes are back

One area that might be worth expanding in future sections is how these concepts scale when moving from single genes to whole-genome analysis and polygenic traits.

epubcheck doing its job perfectly while Adobe's ancient RMSDK (frozen somewhere around 2013) silently chokes on valid CSS4 like min() is peak digital publishing pain. The fact that Kobo routes normal .epub to the Adobe engine and only .kepub.epub gets the modern WebKit one feels almost malicious.

Good point. But I like the minimalism of this website, it's so charming ;)

https://hsr.in.net/ - My personal website

https://shrt.surf/ - and my latest project, a minimalistic URL shortener that doesn't track you, doesn't show ads, and doesn't ask for your email. Just pure utility.

Currently, the highlighter uses a simple keyword heuristic (line.includes('error')). It produces false positives (e.g., "no error found"). I plan to add regex-based custom highlighting to fix this. I treat the file like a video stream. Since the browser doesn't know the total line count of a 10GB file without reading it all (which defeats the purpose), a traditional scrollbar is hard to implement perfectly. The slider acts as a "seek bar". I'll consider adding Prev/Next Chunk buttons for finer control. The "~20MB" claim refers to the file buffer/chunk size held in memory by the FileReader, not the entire browser process footprint (React + DOM + V8 overhead). You are right that the baseline for a React app is higher (60MB+), but the key value proposition is that opening a 10GB file won't spike usage to 10GB—it stays flat relative to the baseline.

I appreciate you testing it out!