bisby

Most people use stable to refer to something that doesn't crash or cause issues. Something that you might call "rock solid" which implies it's not going to fall over. Something to put on your server because you'll get great uptime without issues.

Debian is one of the few places where stable might crash more than unstable, because known bugs in Debian don't get backported unless they cause security issues.

I use Debian on my servers because "some testing" is nice and the only thing I run on my servers is docker. And ironically, I have to use a PPA for docker.

So for me, it's a stable enough base OS, but it "too stable" for anything that actually runs on the servers.

Debian is not all about "stability" in the sense of "doesn't crash". Debian is all about consistency. The platform doesn't change. That means if there is a bug that crashes the system for you... it's going to consistently be there.

For me, it was when stable was on kernel 3.16, and 3.18 was in testing, but the latest kernel was 3.19. And this was an era where AMD's drivers not fully OpenGL compliant yet. Which meant games would crash. And knowing "this game will always crash until 3 years from now when we finally get a newer kernel" was enough to chase me off.

debian's neovim package is 0.7.2. Sid is 0.7.2. Experimental is 0.9.5... If there are any bugfixes between 0.7.2 and 0.9.5 that are critical for your workflow... too bad. If its not a "security" release, its not getting updated. You can live with knowing the bug.

"Never change anything, stick to known good versions" only works if you know 100% that the "known good version" is actually bug free. No code is bug free, so inevitably the locked down versions in Debian will have still some flaws (and debian doesn't backport bugfixes, they only backport SECURITY fixes). For most use cases, the flaws will be minor enough to not matter. But inevitably, if a flaw exists, it affects SOMEONE.

If you actually want to do any sort of complicated computing, debian is not a great choice. if you want a unchanging base so you can run a web browser and processor, I'm sure it's great.

(although my ~15 years as a windows sysadmin probably bias my opinion)

So basically: it's not any harder in linux, but you have more than a decade of muscle memory in windows, so it's harder for you.

That's like saying "Japanese is a less efficient language than English, all of the words are different, and when I want to say a word, I have to learn it first, but in English I just know the words! English is so much better! (My 30 years speaking english probably bias my opinion)"

Things are certainly different, but its hard to compare which is "harder" for the advanced use cases.

There's no shame in having long term experience with one platform and having that shape your expectation about how a solution should look.

I never used the All feed on reddit. Way too much crap on that site.

On Lemmy though, it feels like the best way to get content. Make sure you have your language set... and then be ready to block some communities/instances if they are catered towards languages you don't speak (not maliciously, but yknow, if you don't speak a language 🤷 ). And then you have a huge stream of content.

There is often stuff that doesn't interest me... I don't really care about cat photos, but they also don't bother me, but I get to discover a lot of cool random stuff (I was looking at Beeper earlier today, which I only saw because you posted about it).

It's really extreme change in logic for me, because with reddit and twitter I absolutely did NOT want to see an all feed. I only ever used those sites in heavily curated ways. I'm sure if Lemmy continues growing, the noise will start to outweigh the signal and I'll have to change back, but for now, it's kinda nice.

Im not subscribed but I definitely see your stuff floating past in the All feed. Lemmy has less content, but also less bad content, so browsing all feels a lot more reasonable than r/all ever did. Which then enhances discovery of communities like this.

apparently having all the logic inside firmware (like Nvidia does)

Based on this part of the quote, the nvidia implementation has a lot of the functionality inside not open source binary firmware blobs. And that includes the functionality that the HDMI forum wants staying secret. It's in the closed source firmware, so this is ok, since the open source part only has to send instructions to the firmware, and not include the implementation.

AMD has less functionality inside the firmware. Which means the drivers are "more" open source. But any proprietary stuff that the HDMI forum wants staying secret would have to be in the open.

A developer shouldn't be able to do this thing either. So unless they were the person in charge of securing things, it's not their fault that it was even possible to do. Setup processes with oversight.

If a junior dev somehow finds a way to drop our prod database, that is on me, not them. Why did I give them access to do that?

I know someone who got to interview him once. He spent the whole time complaining about how he never wanted to be a celebrity and just wanted to do the science part of the job and that he hated having to do interviews and talk to the public.

They wound up obviously having no good material from the interview and didn't have anything to run. It was a very "don't meet your heroes" moment for my friend.

But yeah, according to himself, he DOESN'T want to share science or educate. It's a burden to him.

https://www.whitehouse.gov/oncd/briefing-room/2024/02/26/press-release-technical-report/

They might include it. Or they might not. If they don't have time to test it, they just won't, and you may wind up with 5.27 for longer than just the next year if you're waiting for debian's stable repos.

debian's neovim is on version 0.7.2 (even in trixie/sid, you have to go to experimental to get to 0.9.5, which is the current). If there are any bugfixes between 0.7.2 and 0.9.5 that aren't security backported... too bad. You aren't getting it any time soon, because it's not landing in Trixie, and it's not guaranteed to land in whatever is after that either.

Debian's "stable" refers to "predictable" like you said. Which includes bugs being predictable. Not resolved. Predictable. And if you have a bug that crashes your system, that bug will stay there unless it's a "security" issue. Predictable crashing. NOT the "doesn't crash" that people seem to think "stable" means.

I still find it super weird. A (remote) coworker bought an ioniq 5 after 9 months on a wait list... 3 months later, I went to a dealership. they had one on the lot (3 actually). Was able to get one with 0 wait.

Looking at their website, they have 4 2024 ioniq 5s available right now, an SEL, SE, and 2x Limited.

So apparently my local dealership is the sweet spot. Or is this purely a Canada vs US thing?

safari, and the app store aren't great.

I dont have a mac or an iphone, but actually follow tech, so Im at least aware of what apps exist... if I had to guess the rest:

calendar, contact book, video call, time machine backups (this one probably requires knowing that backups are a thing), some sort of e-reader, music app, launcher (macOS did the thing where they added an iOS type launcher when they started making "fullscreen" its own special thing right?), and given the final one is a stamp so... apple mail?

So unless I'm wrong, and we say safari, app store, time machine, and the launcher aren't clear. that's still 6/10 icons that ARE clear. Even if we take out the reader.... 5/10... it's still mostly recognizable

Compared to the FOSS side, which gets GIMP. 1/10.

and I agree there assumptions being made. Things like "App store" needs an A because English is not very inclusive, but I dont think that makes things soulless. If their assumptions were "we're making luxury items for affluent Americans (who generally speak English)" then they made a fine decision for reaching their target audience. I'd argue that the app store icon has the most "creativity" put into it.