It’s disingenuous to say, “oh it’s exactly the same phone”. It’s a narrow interpretation of “it’s the same design language and nothing revolutionary”. But compared to the S23 it’s a massive power overhaul on the processor. It has 12GB of ram. The screen is top notch LTPO, which the S23 didn’t have. The cameras are way improved, it can film 8K, which the S23 couldn’t. It has the toughest Gorilla screen to date. Sure, the changes year after year are nothing to write home about. But small incremental changes stack over time. The average person is keeping phones for 3 or more years. Compared to an S22 or S21, it’s a beast upgrade. I think those are the people they are marketing to, and it’s smart, no one sane is buying a new phone every single year and a lot of people value a new device over a refurbished or used one.

Yeah, that’s absolutely valid. But you run into the same problems again, what the hell is an ostree? Would ask the average gamer. Even some newer changes to bootc will make rpm-ostree unnecessary in the future. Flatpaks are not mandatory even. You could run bluefin or bazzite entirely on appimages.

At least the term cloud native is standardized by the cloud native computing foundation, it has a long story, it’s already known or familiar to a lot of people. And the most important, I think, it is technology agnostic. Even if docker dies and another tech takes its role, or if kubernets are replaced with something else, or even is rpm-ostren is no longer used, cloud native still means the same thing. As for bad smells, that’s just language, words can mean many things at once, we just live with it.

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 on the server side. Now it’s just a standard way to develop software and it’s part of the common parlance. It is the philosophical background, if you will, of snaps, flatpaks, kubernetes, docker, pods. I mean, the entire business model of AWS and dozens of cloud providers, data centers, mass hosting solutions, saas, etc. is based on the cloud native idea. You use the term and everyone in the room knows exactly which principles and development pipeline you’ll use.

Just like all language, it is just a shortcut to convey a complex meaning. Like, I don’t know what distro QE stands for. But that’s not my area of expertise. I bet there’s a good reason it is abbreviated and that you use it on your résumé. It might convey something to a recruiter or not, about what your general expertise and skills could be. Same here, it’s just a term that describes the important and distinctive part of the project. Because for everything else there’s nothing out of the ordinary on bazzite, not even the gaming stuff. The makers don’t even like to call it a distro because they use other people’s distros. What’s unique is the delivery pipeline and the config, and that sounds even worse, marketing wise. I’ll share you some interviews later.

This is an interview with Jorge, who was around here on the thread earlier answering questions.

And here’s an interview on the fedora podcast with bazzite makers.

Which app? Because it all depends of how much access and permissions the app needs. Managing volumes or changing devices is usually the problem. So far I’ve only had to layer two apps (on bazzite, though): veracrypt and vorta. To access old backups. Everything else works fine, even desktop integration. Although I prefer to use box buddy to handle distrobox as a UI, which runs as a flatpak without problem. It’s been great so far at resolving that kind of issues: bug, update, now it works.

Start here for everything Universal Blue. Read here to see how the sauce is made.

The buzz word is not aimed at the regular gaming nerd. It is aimed at gaming nerds who are also developers. Universal blue, the project behind Bazzite, Bluefin, and Aurora, aims to market to developers to use their systems first, on the basis of the tech backend. So then they make the cool FOSS things that the nerd public can use. Cloud native just means that something is engineered and made to make use of the container based devops pipeline.

For example, an atomic immutable OS that is meant to be developed and distributed via the container infrastructure (this is what Universal Blue is). So, instead of working on making an OS the regular way, collecting packages and manually connecting and tidying up absolutely every puzzle piece so it fits together, then pushing it through the installer packaging wizard, etc. This OSs are made by taking an already existing distribution, in this case Fedora atomic distros (but this is by no means mandatory), then customizing some things. Like installing libraries, applications, firmware, kernels and drivers. Then putting it all into a container image, like you would do with a docker or a podman server image. This way, on the user side, they don’t need to install the OS, instead they already have the minimal atomic system handling framework and just copy and boot into that OS image. This automates a lot of the efforts required for bundling and distributing an OS, and it makes new spins on existing distros really fast and efficient to make. It also means that users don’t need to be tech savvy about stuff like directory hierarchies or package management, and updates, installs, upgrades can all be automated to the point of the user barely even noticing them.

On a similar note, these distros, as development workstations, are usually pre-configured to make use of a container based dev pipeline. Everything is flatpacks and development is handled all via docker, pods, etc. Keeping the system clean from the usual development clutter that sediments over time on a traditional development cycle. As a happy coincidence, this makes the dreaded “works on my machine” issue less prevalent, making support of software a tad easier.

On most smartphones you can give titles to timers.

Using fomo and marketinp to force people into debt for a phone. Definitely the moral and sensible choice.

Where’s the “Apple is the only tech giant that respects your privacy” crowd? Just because your data isn’t being publicly auctioned doesn’t mean they aren’t harvesting it and infringing on your privacy.

Gnome is ugly IMO and the extensions and custom themes to make it pretty break at each and every update. I just don’t bother with it anymore. KDE was customized to my liking once and it stays that way through updates without any failure.

Try Aurora DX (it means the developer edition). It’s KDE but with a Fedora base and immutability. It means that even if an update breaks something (unlikely but still) you will always have a working system available to fall back to. It does mean that development is meant to be done via containers, but I find this solution to be way cleaner and easier to work with than traditional package conflicts madness. Give it a go.

Don’t want to think about your OS? Install Aurora. The hardest decision will be choosing your password. Install instructions are identical to any other Fedora installation. Auto updates to everything, never breaking system with bleeding edge software all the time. Superb documentation, zero maintenance, windows like desktop experience but better. That’s all.

Well, you see, this is in the US. So women have rights and autonomy only on paper. In practice and according to a lot of people, women, specially when pregnant, are mere objects to be treated as cattle. The drug tests are part of the quality assurance. You wouldn’t want damaged goods.

I doubt any higher up is “barely scraping by”. And as another comment brought up the recipes, this is most definitely a bot.

Except, that’s in the real world of physics. In this mathematical/philosophical hypothetical metaphysical scenario, x is infinite. Thus the probability is 1. It doesn’t just approach infinite, it is infinite.

It’s not close to 100%, it is by formal definition 100%. It’s a calculus thing, when there’s a y value that depends on an x value. And y approaches 1 when x approaches infinity, then y = 1 when x = infinite.

Indeed, the formal definition actually doesn’t specify how many monkeys will write what given an infinite number of monkeys, it’s unknowable (that’s just how probability is). We just know that it will almost surely happen, but that doesn’t mean it will happen an infinite amount of occurrences.

The infinite amount of time version is just as vague, one monkey will almost surely type a specific thing, eventually, given infinite time to type it. This is because when you throw infinites at probability, all probabilities tend to 1. Given an infinite amount of time, all things that can happen, will almost surely happen, eventually.

Almost surely, I’m quoting mathematicians. Because an infinite anything also includes events that exist but with probability zero. So, sure, the probability is 100% (more accurately, it tends to 1 as the number of monkeys approach infinite) but that doesn’t mean it will occur. Just like 0% doesn’t mean it won’t, because, well, infinity.

Calculus is a bitch.

In typical statistical mathematician fashion, it’s ambiguously “almost surely at least one”. Infinite is very large.

I used Mint for almost its entire existence so far, but recently I’ve started main driving immutables, and gotta say the experience is even more user friendly. That’s my current experimentation stage but, so far, it doesn’t feel experimental at all, it just works out the box, no issues.