Um excuse me time actually already ended in 1991

Except you can define a value with undefined and accessing that value will have different behavior than attempting to access an undefined value.

Should the NVD be deeply involved in all of them just to provide the most accurate security score? That’s an impossible ask.

This is a false dilemma. If the task is truly impossible, that’s not a valid excuse to try anyway and fail repeatedly, especially if doing so causes negative externalities. Numbered scores with decimal precision are not necessary to the core functionality of a CVE database and there are plenty of alternative solutions which would minimize harm and scale more economically.

Oh, bother…

You’ve assumed that I want to explain the root cause of the initial decline. This is not the case. Historically, SO has seen several periods of decline. What I’m actually addressing is the question of why the decline has not stopped, because the sustained nature of this decline is what makes it unusual. If you look at the various charts, you can see a brief rally which gets cut off in late Winter 2022 – this lines up rather nicely with the timing of ChatGPT’s release, I feel.

Let’s ignore that. Tell me more about your Google angle: what’s the basis of your hypothesis?

It’s too much to attribute to any one effect. 50% is a lot for a website of this size (don’t forget that Lemmy exploded from a migration of <5% Reddit usershare). Let’s KISS by attributing likely causes in order of magnitude:

1. ChatGPT became the world’s fastest growing website in a single month and it’s actually half-decent at being a code tutor
2. ChatGPT bots got unleashed on SO and diluted a lot of SO’s comparative advantages
3. Stack Overflow moderators went on strike, which further damaged content quality
4. Structurally speaking, SO is an environment which tends to become more elitist over time. As the userbase becomes progressively more self-selective, the population shrinks.
5. The SO format requires a stream of novel questions, but novel questions generally get rarer over time
6. Developer documentation has generally improved over time. On SO, asking about a well-documented thing is a short-circuit pathway to getting RTFM’d & discussion locked

Delicious gruvbox. Excellent choice with the focus highlight color (I do something similar).

If you use picom, try out this shadow config I made for a similar theme. It creates a neat accent effect that complements the focus border and gives a flatter look:

shadow = true;
shadow-radius = 1;
shadow-opacity = 0.50;
shadow-offset-x = 2;
shadow-offset-y = 2;
shadow-color = "#211521"

My comment is actually an unrelated in-joke forcibly coerced into the shape of a discussion about git. It’s a whole fictional magical universe thing with a lore wiki and stuff:

• “Odium”/“passion”: https://coppermind.net/wiki/Odium
• “invested”: https://coppermind.net/wiki/Investiture
• “Pushing”: https://coppermind.net/wiki/Steel#Allomantic_Use
• “Pulling”: https://coppermind.net/wiki/Iron#Allomantic_Use

Js is what you make of it. It can be a godawful mess but it also can be really awesome.

Agreed. It wasn’t always a great language, but by some miracle it eventually became pretty alright.

But it’s also a double edged sword because that means that novices can write absolute spaghetti code in it. That’s not the fault of the language though.

Disagree. The best languages are those which can be intuitively used without having to learn the pitfalls. Take Rust vs. C++, for example: both languages have pitfalls, but only Rust is intentionally designed to help you steer clear of them. JS is like C++ in this regard – decades of cruft have coalesced into tempting yet painful footguns, much to the chagrin of many a new learner.

An IDE written in Electron?? What a terrible idea! Nobody would ever be stupid enough to let something like that take off…

Pushing/Pulling might seem simple to you, Odium, but not everyone is so passionate or invested.

I’m a plaintext git patch sent via email and lost in the maintainer’s spam folder

Bold of you to assume that an Emacs user will have anything remotely resembling the default keymap by the time they’re proud enough to brag about it

That’s why my terminal is emacs

Just wait until 2024 and it won’t be deprecated anymore

Because you’ve finished configuring the evil package, obviously.

Here’s the current usershare breakdown by instance, if anyone’s curious:

Source: https://github.com/tgxn/lemmy-explorer/tree/main/frontend/public/data

Oh my god this comment gave me an aneurysm

With that being said… Lemmy is still a huge win for the /r/blind folks. Being able to fork the project puts the power to be better into their own hands. It’s also another glowing endorsement to the power of federation that blind community members will be able to browse any Lemmy/Kbin community while still enjoying the benefits of their fork’s accessibility enhancements.

The current state of the fork is already a better screenreader experience than browsing either version of the Reddit website. The fork has been running for 8 days compared to /r/blind being founded 15 years ago. I repeat my previous statement: their fork is already a better in-browser experience. What more needs to be said?

I quite enjoyed reading that quote. You can practically see the columnist rolling their eyes. Does this spokesperson not understand how to say “no comment”?