Your hands and wrists must not hurt yet. You'll eventually come to see writing code as tedium.

Other way around, actually; C was one of several languages proposed to model UNIX without having to write assembly on every line, and has steadily increased in abstraction. Today, C is specified relative to a high-level abstract machine and doesn't really resemble any modern processing units' capabilities.

Incidentally, coming to understand this is precisely what the OP meme is about.

C'mon, I think you have better reading comprehension than that. He's a professional data scientist specializing in machine learning. He went to grad school, then to big industry, then to startups, and is currently running a consultancy. He is very clearly not "on the side of the road." He's merely telling executives to fuck off with their AI grift.

I think they're saying that e.g. you shouldn't index a natural key unless you know that you're going to search/collate by that key as a column. Telling the database that a certain column contains (a component of) the primary key is adding a restriction to that column.

This shit is why I cannot recommend Truffle/Graal. Yes, it's cool technology. Yes, it works well. Yes, I remember Chris Seaton. Yes, most of it is Free Software. However, Oracle is still the fucking lawnmower, and it's not safe to build upon anything they can convince a judge they might own.

Alternatives include RPython (my preference) and also GNU Lightning.

Well, the bad news is that its license bites. The good news is that PLT Redex exists and has a much better license along with better formal tooling and presentation.

RPython.

Direct rendering infrastructure in Linux predates widespread use of "digital rights management" as a term of art by about two or three years. "We were here first," as the saying goes. That said, the specific concept of direct rendering managers is a little newer, and probably was a mistake on its own merits, regardless of the name.

Oracle Ruined America's Cup (Larry Ellison)

Yes, if that's the only reason one is using fail2ban. Honestly, I won't miss it.

PyPy exists. (This is news to around 95% of the community.)

With no more details? I'd go with Dulwich. libgit2 is overly picky about inputs and can't be hacked apart at all, and this affects its bindings too. I recently found myself monkey-patching Dulwich to allow otherwise-forbidden characters in refs, and this would have been fundamentally impossible with anything on top of libgit2.

It's the other way around. Nix sucks. (Guix sucks too.) However, every other build system I've used, as well as every other package manager and every other distro, sucks more.

You're doing fine. Slow down. Forget "installation"; it's not a concept Nix uses. If jumping directly to NixOS is overwhelming, it might be easier to go back to Arch, Ubuntu, or something else you know and are comfortable with, and use Nix from a familiar distro; build up idioms for working with your preferred tools, development environments, and configuration. When you're ready, you can try NixOS again, and hopefully it will make more sense.

nix-env must evaluate all of nixpkgs and the reference implementation of Nix is not very fast. It's not a big mystery, although it appears that a rewrite of Nix will be required to improve it.

Sarcasm needs to be humorous; you're merely rattling off insults. Anyway, it's pretty uncommon that somebody literally "can't contribute code;" anybody who can learn how to use a computer and post juvenile horseshit to Lemmy can learn how to write code. I'm a former professional musician; writing code is my backup career, taking less practice and effort than playing the piano. I encourage you to try putting in some effort; for the same time it takes to write around 500 comments/month on Lemmy, you could probably build a program that automates or simplifies some portion of your life.

And seriously, by doubling down on the idea that being Neanderthal is bad or deficient, you're spouting some nasty rhetoric. It doesn't matter whether you're serious or not; eventually, you'll forget that you were being ironic. "Those who play with the devil's toys will be brought by degrees to wield his sword" and all that.

As a hardware hacker, I've experienced Apple's anti-FLOSS behavior. I was there when Apple was trying to discourage iPodLinux. In contrast, when we wanted to upstream support for the Didj, LeapFrog gave us documentation and their kernel hackers joined our IRC channel. It's the same reason that people prefer ATI/AMD to nVidia, literally anybody to Broadcom, etc.

Your "entire fucking point" is obvious from the top-level comment you replied to; you've taken offense to somebody pointing out that writing FLOSS on Apple hardware is oxymoronic. And it's a bad point, given that such a FLOSS hacker is going to use Homebrew or Nix in order to get a decent userland that hasn't been nerfed repeatedly by an owner with a GPLv3 allergy and a fetish for controlling filesystem layouts. Darwin is a weird exception, not one of the easy-to-handle BSDs.

Also, what, are you not anti-Apple? Do you really think that a fashion company is going to reward you for being fake-angry on Lemmy?

At their most general, they are "data processors." In common parlance, they're often called "algorithms," although some folks insist that that is reserved for programs with trivial control flow. For disambiguation and comparison:

• A service is an API surface and a contract promising that the surface has certain behaviors; data processing may be part of how the API is implemented. In practice, a service is e.g. an HTTPS endpoint and an OpenAPI specification.
• A capability is a copyable token which simultaneously authorizes its holder to perform an action and designates the holder as having the authority to perform that action. This won't be part of your normal curriculum and training; see this post for an introduction, or this story for motivation.
• A controller is a modulator for a (distributed) system. Typically a controller is anything which is actuated by a control loop, although sometimes a controller can sit outside of the system. Common examples include MVC patterns, k8s components, and video-game controllers.

Steps 8, 9, and 11 assume that the filesystem is in a Linux-compatible state and Windows-compatible state simultaneously.

You're literally posting from the SDF's instance. If you're not going to support FLOSS, then consider migrating to a server which reflects your beliefs. (Also, go take an anthropology course so that you don't embarrass yourself by dehumanizing people online.)