Should have used Vim instead, that’s a real text editor. No-one who starts using it ever moves on to something else.

It’s a simple alphabet for computing because most of the early developers of computing developed using it and therefore it’s supported everywhere. If the Vikings had developed early computers then we could use the 24 futhark runes, wouldn’t have upper and lower case to worry about, and you wouldn’t need to render curves in fonts because it’s all straight lines.

But yeah, agreed. Very widely spoken. But don’t translate programming languages automatically; VBA does that for keywords and it’s an utter nightmare.

If you move past the ‘brute force’ method of solving into the ‘constraints’ level, it’s fairly easy to check whether there are multiple possible valid solutions. Using a programming language with a good sets implementation (Python!) makes this easy - for each cell, generate a set of all the values that could possibly go there. If there’s only one, fill it in and remove that value from all the sets in the same row/column/block. If there’s no cells left that only take a unique value, choose the cell with the fewest possibilities and evaluate all of them, recursively. Even a fairly dumb implementation will do the whole problem space in milliseconds. This is a very easy problem to parallelize, too, but it’s hardly worth it for 9x9 sodokus - maybe if you’re generating 16x16 or 25x25 ‘alphabet’ puzzles, but you’ll quickly generate problems beyond the ability of humans to solve.

The method in the article for generating ‘difficult’ puzzles seems mighty inefficient to me - generate a valid solution, and then randomly remove numbers until the puzzle is no longer ‘unique’. That’s a very calculation-heavy way of doing it, need to evaluate the whole puzzle at every step. It must be the case that a ‘unique’ sodoku has at least 8 unique numbers in the starting puzzle, because otherwise there will be at least two solutions, with the missing numbers swapped over. Preferring to remove numbers equal to values that you’ve already removed ought to get you to a hard puzzle faster?

That is a good read, thank you. Didn’t have procedures, had two different brokersge systems running at once because they’d no procedures to follow, lost a fortune.

I’m thinking it’s the "most expensive bug in history so far - haven’t seen an accurate total for CrowdStrike’s little faux pas, yet.

Man alive, I thought that Mozilla had been doing their own Personal Package Archives so that we didn’t have to deal with Ubuntu packaging it as a Snap anymore. And this is doubly disappointing.

Got this installed on all my work machines - if you’re wanting to stick a screenshot on Jira or Slack with a couple of arrows, wavy lines, or a bit blurred out then it’s dead quick and has just the functionality that you need. Yes, it’s simple and lacks a lot of ‘power tools’. Sometimes that’s just what you need, tho.

For some reason, I thought that was going to be a twenty-minute video, not a five-and-a-half hour sequence. Dang.

Been playing it on Arch all morning - runs beautifully straight out the box on a gaming desktop. Forgotten how (a) dark (b) bastard hard it is. Superb game, tho, and all the loading screens being essentially gone adds back a bit of pace it was missing.

And yeah, mapping the weird N64 controller to an xbox pad is always going to be strange - been wasting a lot of items when I’d been intending to look around.

I know you jest, but I’m going to guess it’s for the same reason that the RPCS3 developers didn’t just concentrate on the ‘popular’ games. If they know that all the janky broken games work properly, then they’ll have confidence that there’s no subtle issues hiding in the nearly-perfect ones. A rising tide lifts all boats.

They didn’t pull DMC2 just out of principle? Foolishness, Dante, foolishness.

Yeah; I’ve a 6700XT, and it appears to be a pretty even match for a 7600XT, looking at Phoronix’ graphs. Makes a pretty good job of 60 Hz / 1440p on recent games, maybe turn down a setting or two, and can usually do 144Hz / 1440p on games that are a few years old. If you can get one of those for substantially cheaper than one of these, I’d say go for it.

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.

Ah, I thought that some of these were being posted with the location of the studio - thought some of our bands might have recorded in the States once they got bigger, might have been some better-equipped studios over there. But it makes sense that it just a mistake. Priest are from Birmingham and Steel was recorded in Ascot, so middle and South of England. 100% British as you like.

Well now. A few things, here:

• there are not 9 × 9 × 9 × 9 × … possible ways to play. After the first move, 8 squares remain, and so on, so there’s at most 9 × 8 × 7 × … = 9! = 362880 ways that the game can be played, ignoring the fact that most of those can be eliminated as reflections and rotations, or as win positions before you fill the whole board.

• we don’t care how we got there. Each square can either be blank, a cross, or a nought, so 3^9 combos = 19683, and most of those are illegal, as only the boards where there’s (one or zero) more crosses than noughts are good. And you don’t need to store ‘the computer’s move’, just jump directly to letting the player go again. Let’s guess we need at most a quarter of that.

• we could have created a single web page with 5k anchor elements on it back in the HTML 1.0 days, ignoring the fact that it would have taken a while to download on our 28.8K modems. That wouldn’t have been 170 Mb of unnecessary tagging, even with the ‘lay it out with tables’ style we had at the time.

Google do seem to have a predilection for reinventing the past, poorly. I hear that their bonuses are based on inventing ‘new’ things, though, so it’s in their interest to pass it off?

Exactly this. It is of course possible to fix anything, given spares, skills and time, but if you have to ask, then you probably don’t have the skills already.

Kitchen equipment tends to be quite simple to repair - burned out heating elements generally just unscrew, motors and valves in washing machines tend to be modular, and just swap out - but if you’re not confident with a multimeter then you won’t be able to diagnose it. They tend to be high-power appliances too, which are the riskiest when things go wrong.

If the alternative to fixing it is just to replace it, then feel free to take it to bits and see if you can decide what’s wrong. If there’s very obviously a burned-out part and it’s easy to swap out, then go for it. Otherwise, you can learn about that the parts are and how it all fits together - every day is a school day.

Ah - that’s happened to me before. Making banana wine, crushed and boiled my fruit selection, didn’t filter it very well before fermenting, blocked the airtrap in my demijon, first I knew about it was an almighty bang and then I had to repaint the kitchen.

Joy of homebrewing, am afraid. Sometimes you do stupid things and they turn out amazing, and sometimes you do sensible things and just forget one tiny but essential step. I heartily recommend making snakebite-and-black homebrew, btw - lager kit, cider kit, couple of bottles of blackcurrant juice all in your fermenter; loses all its sweetness and most of its purple colour and the result is a very tasty brew.

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

Annoying - the demo was really good, and ran great on Linux using Proton. Guess I’m going to be holding off on buying till it’s removed and on sale, then - there’s no point in buying a game early and it running like shit.

The side channel resistance includes such matters as ensuring that the cypher takes the same amount of time, regardless of the key, but also such super-sneaky insights as the amount of power used to run the cypher, which can be measured from the CPU temperature. Every bit of the cypher that you can be sure of makes it easier to guess the rest. And even if you coded this algorithm in assembly, the CPU will interpret it as microcode and run that, potentially leaving you vulnerable - this is not straightforward stuff.

Like vzq says, implementing this properly is for a cross-disciplinary team of experts in their fields.