• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle















  • The only time I ever had memory problems with Firefox was when I tried to run it on a potato. That complaint has always been bullshit.

    Edit to add: The aforementioned incident was in 2010, on a machine with only 512MB of RAM. Like I said, potato. Chrome back then was somewhat more memory-efficient than Firefox, and could support three open tabs on that machine before it started thrashing, whereas Firefox would thrash with just one. Both browsers performed abysmally under such a severe RAM shortage, but Chrome was slightly less abysmal. Slightly. I seriously doubt the current version of either browser would be usable on that machine, although I don’t have it (I gave it away soon after this incident) so I can’t check.




  • Isomorphic rendering seems horribly inelegant.

    My first instinct is to just use server-side rendering for this, although that may not be possible since posting a comment involves rendering part of the page on the client side.

    In light of that, my second instinct is to render entirely on the client side, but then Lemmy won’t work without JS, which may or may not be a problem. Mastodon seems to get away with it, but I dunno if Lemmy can. Also, client-side rendering makes it difficult to avoid breaking the back button, which the UI currently does.

    Sheesh. Web development is such a mess.