Readit News logoReadit News
Snild commented on Microsoft forced me to switch to Linux   himthe.dev/blog/microsoft... · Posted by u/bobsterlobster
sedatk · 2 months ago
How old is the Atom? My CPU was about 10 years old at the time.
Snild · 2 months ago
I bought it in late 2013, so 12 years from purchase.

Intel lists the launch date of the CPU (Atom D2500) as Q3'11, making it 14 years old when OpenSUSE Leap 16 was released.

It looks like Intel was releasing Atom CPUs without SSE4.1/4.2 up until 2013, e.g. Atom Z2420.

Snild commented on Microsoft forced me to switch to Linux   himthe.dev/blog/microsoft... · Posted by u/bobsterlobster
sedatk · 2 months ago
My story is simpler. Microsoft dropped the support for Windows 10 and gave me no upgrade path to Windows 11 because my CPU was 5 years too old apparently.

So I installed Fedora on that machine, I learned the process, I went through the hurdles. It wasn’t seamless. But, Fedora never said “I can’t”. When it was over, it was fine.

Only if Microsoft had just let me install Windows 11 and suffer whatever the perf problem my CPU would bring. Then I could consider a hardware upgrade then, maybe.

But, “you can’t install unless you upgrade your CPU” forced me to adopt Linux. More importantly, it gave me a story to tell.

There is a marketing lesson there somewhere, like Torvalds’ famous “you don’t break userspace”, something along the lines of “you don’t break the upgrade path”.

Snild · 2 months ago
> “you can’t install unless you upgrade your CPU”

To be fair, I recently had to switch distros for my little Atom-based server because of a similar deal:

https://en.opensuse.org/openSUSE:X86-64-Architecture-Levels#...

Granted, I only had to convert to Tumbleweed (not trivial, but easier than reinstalling), and the open source nature means there will always be lots of other alternatives, too.

Snild commented on No strcpy either   daniel.haxx.se/blog/2025/... · Posted by u/firesteelrain
1f60c · 3 months ago
I think the submission originally had a typo ("strpy", with no C)
Snild · 3 months ago
Ah.
Snild commented on No strcpy either   daniel.haxx.se/blog/2025/... · Posted by u/firesteelrain
senthil_rajasek · 3 months ago
Title is :

No strcpy either

@dang

Snild · 3 months ago
I don't see a problem with that, but for the record, the title on the site is lower-case for me (both browser tab title, and the header when in reader mode).
Snild commented on Text rendering hates you (2019)   faultlore.com/blah/text-h... · Posted by u/andsoitis
Sesse__ · 3 months ago
> mostly obsolete

The Nordic languages beg to differ!

Snild · 3 months ago
Keep Swedish out of this, you dirty Danes!

Edit: Checked out your profile, correcting myself: "you silly north-Danes!"

Snild commented on Rob Pike goes nuclear over GenAI   skyview.social/?url=https... · Posted by u/christoph-heiss
y-curious · 3 months ago
Where is this spirit when AWS takes a FOSS project, puts it in the cloud and monetizes it?
Snild · 3 months ago
It exists, hence e.g. AGPL.

But for most open source licenses, that example would be within bounds. The grandparent comment objected to not respecting the license.

Snild commented on We replaced H.264 streaming with JPEG screenshots (and it worked better)   blog.helix.ml/p/we-mass-d... · Posted by u/quesobob
bambax · 3 months ago
Yeah, I'm thinking the same thing. Capture the text somehow and send that, and reconstruct it on the other end; and the best part is you only need to send each new character, not the whole screen, so it should be very small and lightning fast?
Snild · 3 months ago
Sounds kind of like https://asciinema.org/ (which I've never used, but it seems cool).
Snild commented on Debian's Git Transition   diziet.dreamwidth.org/204... · Posted by u/all-along
adastra22 · 3 months ago
How is that not literally the git history?
Snild · 3 months ago
It is, except after rebasing.
Snild commented on Debian's Git Transition   diziet.dreamwidth.org/204... · Posted by u/all-along
coryrc · 3 months ago
Gerrit introduces the concept of Commit-Id; essentially a uuid ties to the first review which merged a proposed commit into the trunk.

Cherry picks preserve that Commit-Id. And so do rebases; because they're just text in a commit message.

So you can track history of patches that way, if you needed to. Which you won't.

(PS some team at google didn't understand git or their true requirements, so they wasted SWE-decades at that point on some rebasing bullshit; I was at least able to help them make it slightly less bad and prevent other teams from copying it)

Snild · 3 months ago
But that Commit-Id footer has no functional effect. I don't see how it would help me if I have a clone of the repo, and my upstream (in this case, the debian maintainer) rebases.

> Which you won't.

Why not? Doesn't it make sense to be able to track the history of what patches have been applied for a debian package?

Snild commented on Debian's Git Transition   diziet.dreamwidth.org/204... · Posted by u/all-along
cryptonector · 3 months ago
What siblings say. What you want is `git rebase`, especially with the `--onto` and `--interactive` options. You might also want something like bisect-rebase.sh[0], though there are several other things like it now.

[0] https://gist.github.com/nicowilliams/ea2fa2b445c2db50d2ee650...

Snild · 3 months ago
Rebasing would mean there's no continuous versioning of the "patches on top", which might be undesirable. Also, the history rewriting might make cooperation difficult.

Merges would avoid those problems, but are harder to do if there are lots of conflicts, as you can't fix conflicts patch by patch.

Perhaps a workflow based on merges-of-rebases or rebase-and-overwrite-merge would work, but I don't think it's fair to say "oh just rebase".

u/Snild

KarmaCake day281February 18, 2020
About
Programming, music, video games.

Sweden.

View Original