166
Dealing with YOLO Vibelord colleagues
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Mar 2026
166 points (97.7% liked)
Programming
26135 readers
326 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
browsers are quite capable of rendering text, even images!
But they're bad at it. Especially in performance and amount.
Edit: drag&drop kernel.log in your brower, if you don't believe me.
Not true. Browsers are definitely faster handling text than your average terminal emulator without GPU capabilities, they just use more resources.
That said, GitHub diff viewer specifically is a sluggish mess. But that's not because of the browser.
What, you think the usual text editor renders all lines just because? No, they load the lines that are currently visible + some more for scrolling. At least the ones that don't choke on a mere 100k lines. And they don't need GPU for this.
But webbrowser engines just aren't made for this, but for DOM rendering.
So does a browser. Modern browsers don't even need to receive the whole HTML to start rendering things.
There's a lot of engineering effort put into browsers, much more than in terminal emulators because they need to do much more than just rendering text.
Ok, maybe i have a slight bias, because editors in-browser are usually a system-in-system(-in-system) JS mess.