267
relatable (ihatetehbsod.neocities.org)
submitted 1 year ago by to c/programmer_humor@programming.dev
21 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 27 points 1 year ago (6 children)

Is Ruby on Rails known for crashing often? I’ve been a developer for something like 15 years and don’t understand the backend portion of this meme. Am I missing something?

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 42 points 1 year ago (5 children)

    It’s been ages since I did Rails, but I remember that back then memory leaks were just a fact of life and you had to have a system that monitors the server processes and restarts them when the memory usage gets too high.

    I truly hope that’s not still the case.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 5 points 1 year ago (1 child)

    Lol with kubernetes et al style container orchestration + service architecture, I'd say this is almost becoming more common. It's just so easy to automatically recycle a pod if one of the processes starts being too greedy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago*

    Cattle, not pets.

    But also, stop building stupid and inefficient software. We have these immensely powerful platforms that pervade server farms and consumer devices alike fucking everywhere these days. One of the marked downsides is that now everyone who just wants to finish the MVP and doesn’t care about system efficiency, reliability, and robustness just throws a pile of ass-tier frameworks at the problem and calls it done.

    Use more Rust. It’s good for you. It’s good for the practice of computer science writ large. It’s good for the world.

  • permalink
  • fedilink
  • source
  • parent