this post was submitted on 12 Jun 2023
617 points (100.0% liked)
Technology
37734 readers
600 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It’s entirely possible that they’ve made some assumptions about what a “normal” level of traffic looks like when writing code for their backend, which has caused some things to break when that has changed.
Not our fault if their code is shit.
How is that an example of bad code?
Honestly, it’s probably not - if I’m actually right this is likely an issue that Reddit’s engineers never predicted would happen so never planned for it. I was being hyperbolic.
It's not reactive. A proper reactive system can handle fluctuations in usage patterns more robustly.
I'm having a hard time believing the claim that Reddit's code isn't reactive.
Wouldn't be surprised if it's just a gigantic, mess of nested if-else statements.
Gotos all the way down
Maybe, but this was a huge increase in usage. Reddit never expected to deal with anywhere near thousands of subs going private simultaneously.