The kernel option is mitigations=off, if you want to try adding it to your Grub command line? From the testing I’ve done, provides no benefits whatsoever - no more frames in games, compilation runs no quicker, battery life on a laptop is no better.

https://wiki.archlinux.org/title/Improving_performance#Turn_off_CPU_exploit_mitigations

If you made memory access lines twice as wide, they’d take up more space. More space means (a) chips run slower, because it takes time for the electricity to get there (b) they’d be bigger and more expensive.

The main problem with 32-bit, as others have noticed, is that that’s not really so much RAM. CPUs do addition and subtraction the way we were taught at school - ‘carry the one’, they’ve an overflow bit that’s set when your sum doesn’t fit in the columns. On 8-bit CPUs, we were always checking back when adding up large numbers. On 64-bit CPUs, we can deal with truly massive numbers anyway, it’s not such a hassle. And they’re so fast at doing sums anyway and usually waiting for memory, it’s barely a hassle.

Moving to 128-bit would give us a truly minuscule, probably unmeasurable, benefit in exchange for significant downsides. We could make them, but it would be pointless.

Any decent conductor is going to to vary the beat based on how long it takes for sound to fill the venue in question. Beethoven’s choices for the music halls in Vienna might have made sense then, but not so much today.

One of the things that’s always annoyed the conductors that I’ve worked with is that we always ignore the dynamics in his music. Beethoven’s markings are expressive, subtle. And we always play his stuff louder than indicated.

I thought that it was encrypted if your home directory was encrypted? The impression that I got was that it was just a SQLite database stored in the clear. The user must certainly be able to make queries of that database in order for it to work, so even if it’s hosted by a non-user service, malware running locally will still be able to exfiltrate the data.

Nice insight, thank you.

I can see that there will be a range of markets for these. Installing them in the desert (efficiency not as important as pure cost-per-watt, long-term stability very important) is not the same as installing them on your roof (limited space but fairly easy access, payback time dominated by efficiency) and so the ‘customer’ sweet point for these will not be the same as the ‘industrial’ one.

Sorry if I was ambiguous - it was me that received a spectacular number of downvotes for a comment that I’d not think controversial in any way, and then realised that I might as well ignore all that because it doesn’t matter here.

There’s a few arseholes running bots that seem to downvote every post on a topic sometimes. Don’t let that get you down - no point putting more thought into it than they did. Your opinion matters, dude (-ette), don’t let anyone tell you otherwise.

Once you’ve posted a comment that implies that China is imperfect in some way and received a truly spectacular number of downvotes, and then realised that it makes no difference whatsoever because Lemmy votes only affect your ego and nothing else, then you can move on. We aren’t “the other website”.

That’s Amaranthe you’re thinking of. If you’re a fan of the Swedish metal ‘soprano and gravel’ sound they’re well worth a listen.

Not that I’m the biggest fan of CMake’s syntax, but they are fairly concise and standardised. The XZ backdoor hid in amongst thousands of lines of autotools jank that very few people would be able to audit. A short CMakeList that generates a Makefile is a much harder place to hide something nefarious.

Using LLMs for corporate communications - automatically-generated complaint responses, and the like - usually has swearing disabled, so if you want to fuck up their shit, be sure to express yourself with as many fucking swears as possible. Let’s get that shit into those cunt’s language models ASAP.

That’s almost exactly the problem. English uses helper words exclusively for future tense, and indeed, helper words like ‘to’ to form an infinitive. ‘Will’ is the helper word to show that something is a fact, that it is definite - grammatically, it is indicative. (The sun will rise tomorrow.) ‘Would’ is the helper word to show that something is an opinion, or dependent on something else - grammatically, it is subjunctive. (If you push that, it would fall; if it was cheaper, I would buy it.)

Spanish has both helper words for future tense (conjugations of ‘ir’, analogous to ‘going to’, often used in speech) and straight-up conjugations for future tense (doesn’t exist in English; often used in writing). It also conjugates verbs differently if they’re indicative, subjunctive, or imperative (asking or telling someone to do something). This is how Spanish manages to have fifty-odd ways to conjugate every verb, which is very confusing to English speakers who make do with three ways and helper words.

Translating a ‘future tense sentence’ for Duolingo requires you to have psychic powers about whether something is fact or opinion, which helper words are wanted, and so on, and it usually comes down to guessing between multiple ‘correct’ answers, which Duo will reject all but one of.

Absolutely this. I’d have argued that ‘every day’ is a more idiomatic translation than ‘daily’, and what native speakers would say, but that’s irrelevant. English tends to emphasise the end of sentences as the most important part, so all these translations are correct depending on the nuance that you intend:

• Daily in Hamburg, many ships arrive (as opposed to eg. cars, or few ships)
• Daily, many ships arrive in Hamburg / Many ships arrive daily in Hamburg (as opposed to eg. Bremen)
• Many ships arrive in Hamburg daily (as opposed to eg. weekly)

Wouldn’t question any of those constructions as a native speaker. In fact, original responders’ example was why I gave up on Duolingo myself originally, some years ago. Translating ‘future tense’ sentences from Spanish into English or back again is always going to be a matter of opinion, since English doesn’t have the verb conjugations that Spanish does. Guessing the ‘sanctified answer’ is tedious, when a lot of the time it’s not even the most natural form of a sentence.

Between ‘caps lock’ -> ‘actual control key’, ‘alt gr’ -> ‘compose’, and ‘right ctrl’ -> ‘virtualbox functions’, I’m running out of things that I actually need to remap, or have enough fingers to press without stopping touch-typing. But hey, might come in handy for something…

It’s tolerable if you’re writing something quite prescribed; business reports, perhaps. It’s too limited and obsessed with tedious bullshit if you’re writing prose, say. It wouldn’t do to express yourself.

‘Whom’ would be correct if we suspected it belonged to an individual, but ‘who’ is correct for a group, and we’re asking specifically about nations. Also, no-one would be confused by this, which makes your misguided, ill-mannered pedantry triply unnecessary.

Speaking as someone who has to use Google Cloud Platform most days; they also do some horrific stuff, and their documentation and support are miles behind the AWS and Azure equivalents. And having worse documentation than Azure is quite the achievement.

Was making a joke with you, about how much the Russian army loses in corruption and how their prices are not to be believed. Wasn’t having a go at you. Try to be a bit more chill?

By the time £3.999m has been siphoned off on bribes and corruption necessary overheads, you should be happy with the coathanger and a car battery, comrade.

Remove the update manager? Remove the bootloader and all kernels if you want to - you might if you’re preparing a container image, it won’t stop you. Remove glibc and init? Fine, if that’s what you want - might have no need for those if you’re prepping it up for embedded.

The price of having a computer that does exactly what it’s told is that you have to know what to tell it. But that’s well worth while.

Hey, just because 95% of them are worthless, doesn’t mean the other 5% aren’t too.