Why Your social.org Files Can Have Millions of Lines Without Any Performance Issues
8 points by andros
8 points by andros
This sounds interesting, but alas, a common fault with blog posts like this is to assume that readers will already know what it's about. I have no idea what Org Social is, and the fault is mine, but a quick explanatory link near the top of the article would make it much easier for people to enjoy this if they don't already have the context.
This post really suffers from the obvious use of an LLM to write it -- I wish the author had just explained the interesting bits in their own words, since there are a few in there! (And indeed there seem to be other posts on this blog that don't have this problem, and are lots better?)
As it stands this is borderline spam, to say nothing of the fact that the author might be violating the site self-promo guidelines; I really don't enjoy reading an LLM laboriously explain how some algorithm works devoid of all context or human touch.
I used LLM to do some translations, correct spelling mistakes, and create some (not all) diagrams. It is actually a compilation of various parts of the documentation with some connecting text in between. I invite you to explore it. I apologize that it does not have as human a tone as other articles; my intention was to answer a question in a technical way.
All the things stuck to the viewport make this site a miserable reading experience. Less than half my screen was left as usable reading space.
Reader mode to the rescue, though in Firefox the graphs don't render (get to see the raw mermaid code) and in Safari it's just black boxes. But hey, still a better experience.
Even if reader mode didn’t break the content, I wouldn’t have finished reading it. If the author prioritises self-promotion over the reading experience that drastically in their site design, it’s a good indication the content won’t be worth the time it takes to read.
Unsurprisingly I just noticed the author is also falling afoul of self-promotion rules on here. Flagged.
I'm sorry to hear about your bad experience with reading. What parts of the design did you find unpleasant? How could I improve your future visits? What self-promotion rule have I broken?
The header, nav, and social buttons should be part of the normal page flow, not stuck to the viewport. At most readers will tolerate one on the viewport.
From the site guidelines
Self-promotion: It's great to have authors participate in the community, but not to exploit it as a write-only tool for product announcements or driving traffic to their work. As a rule of thumb, self-promo should be less than a quarter of one's stories and comments.
It’s fine to post and comment your own things, as long as you are genuinely engaging with other things
These are visual preferences; there are no strict rules in this world. However, I will take note in case I can temporarily hide some parts while reading. Thank you for your feedback. The purpose of this article is to showcase HTTP optimizations that have been used on the client side, which may serve as inspiration for you to use in your own projects. That is why I provide so many technical details, tricks and diagrams.
I'm sorry to hear about your bad experience. What was the problem? What resolution do you use? I'm still working on the website.