Or, use the smallest denomination. In the US, that’s typically tenths of a penny. So, $1 = 1000. Then everything uses integer arithmetic.

Of course, JS doesn’t actually have integers, so yeah, strings are probably best.

It sounds like they’re just encrypting it twice (once with each algorithm), but I could be wrong.

Elon doesn’t spend time with his children. They are meat shields to him.

“We had a couple boos”

Lol, you are in complete denial, lady. Nobody likes your swasticar.

Cool, I don’t want it. Like, at all. Not one bit.

Learn the fundamentals and try to use as few libraries as possible, is always my approach.

I sometimes make videos on how to use one of my libraries. They’re often outdated a year later.

Only several thousand? There was a guy when I worked for Facebook who pushed a config change incrementing a timeout from 5 seconds to 30 seconds in the caching layer. Config changes roll out instantly. Brought down all of Facebook for about two hours. Probably cost them many millions. I mean, good for him.

According to the law (the thing that determines if something is or isn’t illegal) it’s illegal. Zuck is a criminal.

You’re a hero.

That’s a great response. Makes me really respect the people who run Codeberg.

Simple solution: buy a smart TV and never connect it to the internet.

That depends on the mail server, but usually yes. The same mail server can handle multiple domains.

Yes. Email uses different DNS records than websites, so you can use your second level domain for both.

When you set it up, you’ll create MX records that point to your mail server(s), and A records that point to your web server(s).

If it’s using AI, I’m not interested. AI is garbage and produces garbage code. I definitely don’t want some LLM fucking up my database.

The models in my project have several ways of doing it. On the server side, there’s a function that accepts data from the DB, and a function that accepts data from the frontend. Same with serializing. One function to serialize the data for the DB and one to serialize for the frontend. On the frontend, it’s simpler, since it only sends/receives to/from the server.

That’s mostly abstracted away in a top level class called “Entity”. It’s only if you need to do something special that you’d reimplement those functions. My data abstraction library is open source at https://nymph.io/ if you wanna check it out. It’s what runs my email service, https://port87.com/.

You might want to think about running a “stable” or “LTS” OS and spin up things in Docker instead. That way you only have to do OS level updates very rarely.

Right now, not very. Basically only open source software can run on it, and only if it’s either exceptionally portable or has been tweaked to compile for it.

In the future, hopefully this is usable for general computing, but right now it’s basically only usable for R&D or niche applications.

The path forward for RISC-V is getting it into more developers’ hands though, so having it available for really nice hardware like the Framework is awesome.

Well, kind of 3 companies.

Intel and AMD both have rights to x86_64, since they both held patents used by it. In 2021, AMD’s patents expired.

Then there’s ARM, which is solely owned by Arm Holdings.

But yes, it’s still very much a big problem, and I really hope RISC-V succeeds to solve that problem. Licensing core designs is a much better motive and business model than licensing an entire ISA.

Edit: oh wait, you said two architectures, not two companies. Never mind, you’re right. :)

Whoever*

Whom is an object, who is a subject. An object usually follows prepositions like “to”, so it’s good instinct to use whomever here, but in this case the object is the entire clause “whoever invented …”, so the whoever is the subject of the verb invented.