Not my blog, but the author's experience reminded me of my own frustrations with Microsoft GitHub.

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 2 years ago (2 children)

There’s a reason they do that: Files can get big

Oh, boy. Wouldn't it be great if servers had a way to discover the size of the files on their storage without having to read them?

adding various code highlighting and interactivity costs performance

Somebody, quick, there's work to be done on language theory so that we learn how to do those things with a cost just proportional to the file size!

(No way! Who is that Chomsky guy you keep telling me about?)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago

    Dude, his point is that if you did not implement partial rendering on a big file, the browser will have to work extra hard to render that shit. Not to mention if you add any interactivity on the client side like variable highlighting that needs to be context aware for each language... that basically turns your browser into VSCode, at that point just launch the browser based vscode using the . shortcut.

    It's not a matter of the server side of things but rather on the client side of things.

  • source
  • parent