It's not literally everyone.

Immunocompromised people who have managed to survive are often still afraid of catching Covid. How little most people care means that those who are worried have a difficult time existing in public spaces. Especially with the constant social pressure to act like Covid is over. You're not going to see people who are worried about Covid as often, because... they are worried about Covid.

This was the case early on, too, though! Covid is _much_ more likely to kill people in marginalized groups. And while marginalized deaths still show up statistically, they are going to be more hidden in the day to day.

New Covid variants still cause severe long-term effects. From what I’ve read, the consensus seems to be “we have no idea what all of the long-term consequences will be, but they’re looking worrisome.” Covid is not reported on as much now, but this information isn't from like, fringe sources or anything. There is less news about Covid now because nobody wants to think or read about Covid anymore.

e.g. a quick search gives me: https://www.cbc.ca/news/health/researchers-are-still-untangl...

So, while most people may have moved on, I think the RTO movement is still hostile and coercive. Honestly, imo most people having moved on is also largely due to coercive forces.

    fn five() -> i32 {
        return 5;
    }

    fn five() -> i32 {
        5;
        return ();
    }

    error[E0308]: mismatched types
     --> src/main.rs:1:14
      |
    1 | fn test() -> i32 {
      |    ----      ^^^ expected `i32`, found `()`
      |    |
      |    implicitly returns `()` as its body has no tail or `return` expression
    2 |     5;
      |      - help: remove this semicolon to return this value

    let dx = {
        let prev_x = x;
        x = get_x();
        x - prev_x
    };

    let x = {
        3
    };
    let y = {
        3;
    };
    assert_eq!(x, 3);
    assert_eq!(y, ());

i think it'd also help a lot to have some gifs of the state machine operating on stuff

or maybe you could have something with "syntax" highlighting. a navigable timeline that changes the highlighting based on the current ignore lists and / or stack contents as you step through the code could be neat

this thread's turning into a decent example of why i hate talking to people about music. no matter how polite or reasonable someone is otherwise, there's like a 90% chance they have all these weird value judgements tied up in what people are listening to. it's incredibly tedious.

the indexing step is basically building this db in the background, it's just kept out of view / hidden unless you're building ide plugins or whatever.

our current system is so broken and evil that i wonder if just getting rid of it entirely wouldn't actually be better and more ethical. even with the problem of releasing however many violent offenders back in the wild. "it might be even more beaurocratic" isn't really going to convince me of anything.

i dont know what the best alternative solution is, im a software engineer. i just know that the current solution is depraved and should be torn down and replaced.

also, there are no spelling mistakes in my comment. perhaps consider learning about how words are spelled in british english vs american english? :)

idk about the author, but when i was younger, some people's pedantry and pettiness over grammar / capitalisation / more casual chatting got me to switch sides and deliberately stop using it as much. now it's also an aesthetic preference

i think there's potentially a valid point about accessibility concerns, but blog posts, chatrooms, and internet comments are also very informal modes of discourse

"good" or "bad" is sort of irrelevant

(what i've usually done for hunting down coroutine errors is use a tracing profiler, or i guess just printf debugging. it is probably the worst part still, tho)