Which is strange, because Azure’s documentation is complete dogshit.

We were trying to solve something at work (send SMTP messages using OAuth authentication, not rocket science) and Azure’s own chatbot kept on making up non-existent server commands, rest endpoints that don’t exist, and phantom permissions that needed to be added to the account.

Seriously; fuck Azure, fuck Copilot. Made a task that should have taken hours, take weeks.

Each package has an average of 1.1 Gb of binaries? Maybe delete a few of the old versions, then. But I think the most serious ask there is the network infrastructure - lots of big downloads around the world soon add up.

The Arch linux package is about 150 Mb; they’ve a few larger ones, but most come in at a few megabytes. (Have just checked my Pacoloco shared cache - average of 773 packages is 5.8 Mb. That serves a network server, a gaming desktop, my personal development laptop and my work development laptop, so it’s a cross section.)

Nice! I switched my parents over to Firefox and OpenOffice years ago, so switching them over to Linux Mint was just a matter of showing them where the update button was now. (Their laptops are completely functional for their purposes, but couldn’t be “upgraded” from Windows 10 to 11.) Scratch another few off the MS list forever.

Audio codecs like MP3 usually do a Fourier transform to move the sound into the frequency domain, discard any frequencies that you’re unlikely to notice, and encode ‘rate of change’ for the remaining ones. So the encoding problem is usually sound with fast changes in intensity or frequency, which is basically what percussion is.

System is quite percussion heavy, so will sound bad.

Recently moved from Spotify to Qobuz, because fuck Dan Ek, and the fact that they’ve got better bitrates across the board really makes the difference for jazz and jazzy stuff. Neglected, sounds crap on Spotify. Sounds great on Qobuz. But that’s the change from ‘bad’ to ‘quite good’ bitrates; additional bits are very much a case of diminishing returns.

Lemmyvision song contest? Then that means it’s time to link Feddit UK’s original submission, the Northern Boys with the phenomenal Sexy Train:

https://youtube.com/watch?v=4VXKhJfRQ7k&list=RD4VXKhJfRQ7k&start_radio=1&pp=ygUYbm9ydGhlcm4gYm95cyBzZXh5IHRyYWluoAcB

Yes, very happy with mine. Started it up to see the preinstalled version of Linux and then restarted it to install Arch btw instead, but it’s a great wee machine, exactly what I wanted and will be replacing it with another like it when the time comes.

It is certainly true that TempleOS won’t be identifying with one of the common browser user agents when surfing the internet.

If you’ve any suggestion on how to implement that, then it’s a million-dollar idea.

The “I’m a human” test that only takes a few seconds and then lets you do what you like for an hour was always vulnerable to ‘auth farms’. Pay some poor bastards in the third world a pittance to pass the test a thousand times an hour, let the bots run wild. And the bots have gained the ability to pass the tests themselves, at least by boiling the oceans in some datacentre while the VC money holds out.

Finding the people running the bots, fitting them with some very heavy boots and then seeing if they can swim in the deep ocean is probably needlessly cruel, but I’d be up for tarring and feathering a few. Once the videos got out, the rest might think harder about their life choices…

I dunno. Oxygen Not Included looks crisp on a 4K monitor. And it makes my job easier, being able to have an absolute tonne of code on-screen and readable. I reckon I could probably use an 8K monitor for those things.

Yeah, I generally have FSR running on any 3D game made in about the last decade - even if I can run it at 4K at a reasonable framerate, my computer fans start to sound like a hoover and the whole room starts warming up. But upscaling seems a better solution than having separate monitors for work and play.

If you think you might want to leave early, more polite not to disturb the other patrons. If there were any other patrons, of course.

100% of supercomputers, 80% of mobile devices (as Android), 4 or 5% of desktops depending on whether you count ChromeOS. Desktop share is a few percent higher if you just count gaming PCs, eg. the Steam survey, since it’s more widely used at home than on business machines.

The rate of adoption is accelerating, too - slowly but steadily.

Oof. The second-hand market is full of stuff that businesses are throwing out since they won’t run Win11, but which run Linux perfectly well. I’ve just recently replaced my NAS / home server with a £20 core i5 mini-PC that if anything is a bit overpowered for the job. Runs Mint desktop very nicely.

I’d imagine that if you’re spending a hundred times as much, then you don’t just have “web and office” in mind, though…

Well, having not played the Xbox version… ;-) Once you’ve got it running, it remains one of the finest games of all time.

Getting it running is the real sands of time, tho. It has a particular hatred of multi-core CPUs, requires a graphics card that supports both hardware transform & lighting but also truly ancient versions of DirectX, and is obstinately not-widescreen. You’ll be wanting a fan patch; last time I tried one, it was a bit of a crash-fest (it wasn’t, back in the day) and some of the SFX looked plain wrong.

Graphics still held up perfectly - the art style is very strong - and the story remains charming. All I wanted from a remake was the damned thing to start up in a modern screen resolution, and it seems they’ve managed to spend years on it without even managing that.

“If you make noise in real life, then the alien will hear you in game.”. As if A:I needed to be any more terrifying than it is.

Still - it’s a very expensive bit of hardware to implement the microphone feature that eg. the Famicom had, and the ‘tracking’ functionality only benefits a couple of games. Bizarre decision to make it mandatory as part of the console.

AmigaOS is still available and able to run all your Linux favourite applications as well as ‘classic Amiga software’, except of course it requires you to be running a PPC processor. Plus it costs money. So you’d have to invest £lots in ‘most of a new PC’ to see whether it even works for you.

Now, if we could open-source it and get it running on x64, I’d love to be running workbench again. It was ahead of its time.

https://amigaos.net/

Dark Souls 3 is a great game to play at SL1. You’ve got quite a selection of weapons and armour that you can equip, plus one spell, so it’s a bit of a puzzler to find optimum combinations of stuff to beat all the bosses.

Dark Souls 1 is okay to play at SL1. You’re limited to being a pyromancer and have a good selection of flame spells that you can cast, but you’re limited to weapons with fairly boring movesets, and you’ll be doing a lot of running back to Blightown to get pyromancies and level up your flame.

Dark Souls 2 is goddamned brutal to play at SL1. Your dodging is tied to your agility, which means you’re a sitting duck until you get some stat boosting gear. Start the game by murdering Cale for his hat of +3 dexterity, grab the work hook and the ladle to swap out in your off-hand for their small stat boosts, and get yourself to Tseldora to grind the peasant set for its small adaptability bonus. I hope you’re good at beating end-game bosses with a rapier, no shield, and bad rolls - maximum four in a row due to your low stamina, which makes throne watcher / defender hellish.

Scholar obviously has all of the pain of 2, plus you can’t rush into the DLC areas for their high-powered rings. By the time you get the ring of the embedded for its massive SL1 stat boost, you’ll have most certainly earned it.

Yes, I did play through all four at SL1 in preparation for the release of Elden Ring. DS3 is fun at SL1, but I also do not recommend the others to anyone. Elden Ring is quite good at RL1 - it still allows some quite varied builds, and it forces you to learn the bosses rather than just “DPS race” them like you do normally.

Proving a thing that’s only known empirically is extremely valuable, too. We’ve an enormous amount of evidence that the Riemann hypothesis is correct - we can produce an infinite amount of points on the line, in fact - but proving it is a different matter.

Interesting, but misguided, I think.

If you’ve selected Python as your programming language, then your problem is likely either to do some text processing, a server-side lambda, or to provide a quick user interface. If you’re using it for eg. Numpy, then you’re really using Python to load and format some data before handing it to a dedicated maths library for evaluation.

If you’ve selected Go as your programming language, then your problem is likely to be either networking related - perhaps to provide a microservice that mediates between network and database - or orchestration of some kind. Kubernetes is the famous one, but a lot of system configuration tools use it to manipulate a variety of other services.

What these uses have in common is that they’re usually disk- or network- limited and spend most of their time waiting, so it doesn’t matter so much if they’re not super efficient. If you are planning to peg the CPU at 100% for hours on end, you wouldn’t choose them - you’d reach for C / C++ / Rust. Although Swift does remarkably well, too.

Seeing how quickly you can solve Fannkuch-Redux using Python is a bit like seeing how quickly you can drive nails into a wall using a screwdriver. Interesting in its way, but you’d be better picking up the correct tool in the first place.

Back when I owned an XPS, one of the driver options was ‘compressed screen updates’, which only updated the part that had changed. As far as I could tell, made no difference to battery life whatsoever - turning down the screen brightness even a notch did much more.

Daily driver laptop for nearly ten years, and the part that finally failed was the CPU fan, which wasn’t easy to obtain replacement parts for, so treated myself to a new laptop entirely. Mind you, the power connection was a PoS, would have been as well keeping that on an annual reorder for how often it failed. Pretty good laptop otherwise.

A controversial take. Every new feature added to Github has made it more unpleasant to use, and a lot of that is down to Copilot, for me. Only way to get rid of it is to wait for Github to go down again, which is the only thing it does reliably at the moment.