Bazzite Post-Mortem
31–40 of 156 posts
Re: Bazzite Post-Mortem
#32I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy.
> "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project. e.g. cloudflare uses the tag for all of their incident reports ( https://blog.cloudflare.com/tag/post-mortem/ ), not as a signal…
I'm aware about the use in incident reports of course, but then you still don't call it " Post-Mortem" but use a more specific namespace.
Re: Bazzite Post-Mortem
#33I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy.
> "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project. e.g. cloudflare uses the tag for all of their incident reports ( https://blog.cloudflare.com/tag/post-mortem/ ), not as a signal…
That's what a post-mortem implies to me in the tech industry. A thing happened, it's over now, here are the lessons we learned to take into the future.
Re: Bazzite Post-Mortem
#34Re: Bazzite Post-Mortem
#35Personally I find that sticking to distros backed by companies or very large communities is just easier in the long term (Debian/Ubuntu/Fedora/Arch).
Re: Bazzite Post-Mortem
#36I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy.
> "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project. e.g. cloudflare uses the tag for all of their incident reports ( https://blog.cloudflare.com/tag/post-mortem/ ), not as a signal…
People should stop using it as a synonym, then. The Latin effectively means "after death", meaning its a poor synonym for "what happened wrong recently".
Re: Bazzite Post-Mortem
#37Earlier quoted context omitted.
[flagged]
was publicly being rude to the point of making other contributors leave (even after being asked to stop) and at least one case of using a slur they said it themselves in this post > Yes, I know I am hard to work with. Yes, I know that I pushed certain OSS contributors away. generally the kind of person that gives open source a bad reputation, you can be critical or anti-social without being an asshole
Re: Bazzite Post-Mortem
#38I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy.
Antheas was the #1 most active developer, and responsible for almost all low level integrations.
Re: Bazzite Post-Mortem
#39I got another one:
Look, follow the money, Microsoft knows Windows 11 on handhelds is a dumpster fire right now, and they are not ready to drop their own "Xbox Portable" yet
So how do they keep the market from moving to the alternative SteamOS/Valve?
They trojan horse the "alternative"
Think about it: Bazzite pops up, gains massive community "trust", every traditionally pro-MSFT media talk about it, and then coincidentally becomes the loudest voice trashing GPD's HW support, why would they do that?
It's a classic Embrace, Extend, Extinguish play
FUD: Use Bazzite as an "undercover" $MSFT project to make GPD look like a risky, unoptimized mess
Damage: GPD takes the hit because they are actually trying to innovate, while the "community" devs (who are definitely on a $MSFT gang) tell everyone to just buy an Rog Ally ($MSFT Partner) or wait for the next Microsoft Xbox handheld
Pivot: Once GPD is sidelined as a "niche hobbyist risk", Microsoft drops a polished Handheld UX for Windows, Bazzite magically "loses funding" or support, and everyone gets funneled back into the Game Pass ecosystem on "approved" hardware
Bazzite isn't a "community project", it's a trojan hose
GPD bet on the wrong horse thinking that community was neutral
Re: Bazzite Post-Mortem
#40Bazzite made it so easy to switch from windows. I first tried cachyos but bazzite’s gamemode worked perfectly from the start, hdr and vrr included, on nvidia. Turned an expensive PC into an expensive console and made me so happy. Just the fact I can sleep the system mid-game and resume is magic! Guess I gotta go back to cachy and try again. Bummer
Why? Because some guy was pushed out of the friend group?