• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle
  • 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.


  • 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.


  • The ArchWiki is the best hand-holding that you’re going to get on Linux, it’s the finest system administration documentation that the OS has available. But Arch doesn’t “do things for you automatically”, that’s not their ethos. So it’s hard mode until you’ve developed enough sysadmin skills to understand what the docs are telling you, and then it’s easy mode because it all works great together and you’ve a phenomenal reference source.

    We run SUSE at work; and when SUSE is working, it’s a damn fine Linux - secure by default, up-to-date, efficient. But if it stops working, man alive, I wish we were using Arch instead. (Admittedly, we just redeploy anything on SUSE that stops working, which takes moments, whereas fixing Arch takes a while but at least you can fix it.)





  • 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.