Yeah, we’ve replaced “you can build your own kernel and install own grub” with “it’s cloud native”.

Not sure it’s better…

lemme guess… and inject would close it again?

Let’s make 2025 2008 again!

Being able to use a keyboard without looking at it is a good thing.

Only thing that makes it “different situation” for smartphone is that they just don’t have the keyboards. (And some of us kinda accepted that…)

I get it, but a gentle reminder, often the best way for society to have an awesome projects is to have a lot of projects.

Or…

…or in 30? That’s how it would work for me since I’m a very slow (distracted!) reader.

I get the point, though. Thanks.

There’s nothing cloud about it. It’s a bad marketing term.

…you mean, what if … what if the cool Linux/FOSS hackers are somehow also very bad at marketing?

Bazzite was assembled, by some very cool people

but then again, why these cool people keep saying things like “cloud native”… is a mystery to me…

Funny enough I had not fully realized this about Steam Deck myself, because I kind of made a special exception for Steam Deck to prevent myself from nerding out on it too much: this is strictly for fun!

(That’s why I only changed hostname, replaced the default terminal emulator and set up Syncthing. Oh, and SSH access but that’s it, I promise! :D)

I suspect the “cloud native” marketing term in this context just means you can run the same image file in a vm, vps, bare metal, whatever.

…yeah that’s what makes it suspicious. Alone it can be a good thing but why rush to mention it for a fricking gaming/home distro? As if running gaming/home distro anywhere else than as close to the hardware as possible was somehow inherently normal or even good.

(The idea of cleanly separating “user user space” does sound inherently good, if achievable…)

Again, who are they marketing to?

Thanks, I think I’ve already heard about this architecture, although I don’t think there was any standard term for that. Maybe it’s time to try one of these out one day…

It’s still weird that hey would sprinkle “cloud native” all over the place just to confuse people like me. (But then again, maybe I’ve been living under a rock…)

Thanks for sharing, I haven’t read it yet but it looks like there’s lot of interesting stuff there. (Definitely not a “14 min read” 😉 )

I moved from (10+ years) Vim to Neovim about last year an I actually used Kickstart, but honestly, while it’s nice to give you a start (especially from people coming from other, more “rich-by-default” editors), there definitely is the problem that I don’t get to really understand how my own config works. …which makes it harder to debug problems but also to ask for help.

And problems will inevitably come, especially with such an active ecosystem of plugins.

I’ve been planning to do a deeper dive into my config–perhaps even rewrite parts of it—so your article is going to be a good source.

Maybe I’m more like a bovine when it comes to digesting.

I graze on stuff, then later I will regurgitate it and slowly chew and process it again. (…and sometimes again, etc… until I suddenly realize that I’ve learned something…) The grazing is separate process, and my greed makes it already unpredictable enough. (The thing with Internet meadows is, there’s always another meadow nearby.)

Yeah I have bad attention span but all that means is that even if the article is 5 minute I will be googling every other word and and opening every other link, and THAT’s far more significant than the length of the article.

After all, there’s a reason I did not end up reading the original “14 min article” (which by the way got rated almost an hour by Firefox reader mode, go figure) and went on to post this… :D

How does the estimate help you decide?

I don’t get it. If I’m interested in something, I’m interested in it regardless of the length of an article, right?

I mean, maybe I’m not interested in all of it, but then I can just spend, say, 30 seconds evaluating whether the article is any good and whether it spends a paragraph or two on the very topic I’m curious about. Length of the article does not have much bearing on that, it’s more about whether I know the terms I’m looking for and can spot them. (Of course, massive length may hint I will spend more time sifting through, but peeking at scrollbar is enough to realize that.)

If the thing I’m interested in is buried in a massive wall of text, so what? I can ignore the rest of the article as much as I can ignore the rest of the blog (or the internet…)

The real unpredictable thing for me is always that even if I’m looking for topic X, I might actually need to learn about W first, and often I’m underestimating the relevancy of W and its own depth. So I could spend 1 minute reading about X but still find myself unable to use the knowledge. That’s regardless of whether the knowledge was in a 1h long article or 10 min.