less about certain bugs and limitations, where I can understand that the problem is harder than it seems
and more about others, where I have to imagine a poor intern dragged around by bad advice for several sprints, finally marking the task done (forehead sweating and all), even though they did not really know what they were doing even for a minute.
Thank you for the post, especially the interview links; I'll check them out.
I’m sorry, but it is a software engineering term. Maybe not from the area you are familiar with, but cloud native was the raging buzzword…about 10 years ago
I guess my point would be the same, but conclusion is the opposite. Yes, I've heard "cloud native" tons of times, but that is the problem with buzzwords: because they are overused (and often used a lot by people who don't really know what they are talking about), for many people like me, they lose meaning in that period. It's like "AI" nowadays, or "NFT" few years ago. The term loses its specificity (if it ever had one), and collects all the "bad smell" from people overusing -- not just the term but sometimes also the methodology behind.
Honestly, for me rpm-ostree and Flatpak would be excellent terms to convey the architecture of Bazzite. I did have to go to here and to Wikipedia to learn that.
The suspicious part is that the "good folks making good shit" are defending it, and even doubling down because it makes people question the whole identity and of the project. (But I guess out that turned out after your post.)
(I recognize that it's by no means all of the Bazzite's good folks.)
Cloud native computing is an approach in software development that utilizes cloud computing
to its fullest due to its use of an open source software stack to deploy applications as microservices.
Typically, cloud native applications are built as a set of microservices that run in Docker containers,
orchestrated in Kubernetes and managed and deployed using DevOps and Git Ops workflows.
That term is extremely vague at best.
And guess what: If I just looked up the definition and ran with it, I would just shrug and toss the whole thing out. "Do I want to run my games as microservices in Kubernetes? I guess some niche group of people want..."
The whole reason we have this thread -- and where I've learned what Bazzite is about (mostly from its users) -- is because i did not fully trust the buzzword, and I already knew something about Bazzite in the first place.
The buzz word is not aimed at the regular gaming nerd. It is aimed at gaming nerds who are also developers.
I'm a gaming nerd and a developer and I did not get it.
Lot of explanations in this thread seem to be: "we just use cloud spec for testing and deployment". That's absolutely fine.
But context matters a lot. If I open a main page of the project, I don't have my developer's hat on. I will assume that the main page is intended to describe the core value of the project. What the heck does "cloud native" mean? To a gamer? Pretty much nothing. (At best they will think you want to run their games like Google Sheets, I guess). To a SW engineer with 8 years of experience in distro QE? Pretty much nothing. It's the kind of lingo you hear on meeting with C-suites. (Before you go back to your office, sit down with your PO and tech lead and try to decrypt/guess what they want us to do.) I mean, seriously, who talks like that? I'm pretty sure it's neither SW engineers nor gamers.
Don't get me wrong, I appreciate your explanation, it's really well written. Given what I've learned from this thread, Bazzite seems like worth trying out.
Just the marketing seems weird. I mean, the whole reason I even found the page is because I'm someone who cares about whose SW I'm using and how it's ran and maintained. And I do understand tech. Tossing around meaningless terms at me is not going to make me feel a lot of trust...
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...)
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.
netvor @ netvor @lemmy.world Posts 12Comments 276Joined 2 yr. ago
More nuanced reply: I do tend to complain