Most likely. Some fossils are, although very hard, rather brittle as well.

The RAE is not a prescriptive institution at all. They fight people on social media over that. They’re not shaming anyone for spelling a word different, just describing what the language users are doing.

It’s all about composition

Alca torda, aka razorbill.

Entirely different things, and I think the meme actually correctly corresponds to orthopedics. It’s a pediatric specialty, and unfortunately, most of the treatments are some form or another of restraining body parts so they grow straight. Hence the snake tied to the rod in order to remain straight instead of wrapping and slithering around.

It’s a catch-22 situation. You are supposed to disclose if you wrote the thing you’re citing, but also cite in third person, and also it should be obfuscated for the peer review. So, what happens is that you write something like “in the author’s previous work (yourownname, 2017)…” then that gets censored by yourself or whoever is in charge of the peer review, “in (blank) previous work (blank)…”. Now, if you’re experienced in reviews you can probably guess it is the author of the paper you’re reviewing quoting themselves. But you still don’t know who it is, and you could never guess right whether it is Ruth Gotian or not. So you’re back to the tweet’s situation.

Why does every mobile keyboard developer have some controversial shit. I just want to text in peace.

Fuck cars

Ok listen. That is the way governments want you to think in order to get away with erasing your right to privacy. It’s the old “I have nothing to hide” argument.

But here’s the thing. You have a butthole. I have a butthole. Everyone in the planet has a butthole. Having a butthole is nothing to be ashamed of, it is not a crime to have a butthole. No one will prosecute you for having a butthole. But that doesn’t mean it is ok for the government to see everyone’s butthole. That’s your right to privacy.

If you want to protect children, you turn to social scientists to understand the problems and identify the ways in which to catch and prosecute offenders. Weaponizing surveillance on everyone in order to catch a very tiny percentage of population who might be committing a crime is hurting everyone.

Privacy is not about empowering pedos, it is about protecting everyone’s rights. Erode one right and you erode all rights. Once the system is in place, then political surveillance to destroy democracy and install fascism is what follows.

Ironically, the global fascism is currently run by pedophiles.

If you know how xerygraphy works, which is what the most popular fax machines used before laser printers, that statement is actually not far off. Heat drums were the first piece to fail in them.

Neat project, shame on the basic premise. Just remember to delete your second brain once in a while, for the health of your first one, and actually use it for something creative once in a while.

Oh we do measure why’s, that’s the point of social sciences. You just have to accept that purpose and intent don’t exist in a vacuum and are the result of human perception and expression then study it as such. As a human phenomenon. From philosophy to psychology, there’s a vast body of analysis on the why of many things. Cultural artifacts for example are the equivalent of batteries, where meaning is concentrated, captured and can be measured, studied and analysed.

Is this fish but with plants?

They are geolocked though. Not free world wide. Just for a small subset of the global west.

In the Soviet Union, the Proletariat had taken control

Then why did they kill so many peasants and workers?

The outcome was quite positive for the Working Class.

Except for the ones who are dead.

[…] implementation of the dictatorship [of the proletariat] was clearly defined by Lenin as early as in 1906, when he argued it must involve “unlimited power based on force and not on law,” power that is “absolutely unrestricted by any rules whatever and based directly on violence.”

Leszek Kołakowski

Never idolize anyone. I think the lack of certainty in the number of deaths Lenin was responsible for adds more horror to his decisions. No matter how pretty his ideas were, or how cute he looked with a cat, an oligarch is an oligarch, and as soon as a revolutionary acquires power, they become the oppressor.

The package manager way of delivering distro management, updates and upgrades is an archaic and dumb idea. Doomed to fail since inception and the reason Linux never broke the 1% of users in forever. It’s a bad model.

Atomic and immutable distribution of an OS is the preferred and successful model for the average user who wants a PC to be a tool and not a hobby on itself. I don’t think the traditional package manager will ever go away. But there are alternatives now.

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.

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.