• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle



  • Funnily enough, one of the few legitimately impactful non-enterprise uses of AVX512 I’m aware of is that it does a really good job of accelerating emulation of the Cell SPUs in RPCS3. But you’re absolutely right, those things are very funky and implementing their functions is by far the most difficult part of PS3 emulation.

    Luckily, I think most games either didn’t do much with them or left programming for them to middleware, so it would mostly be first- and second-party games that would need super-extensive customisation and testing. Sony could probably figure it out, if they were convinced there was sufficient demand and potential profit on the other side.


  • The Xbox 360 was based on the same weird, in-order PowerPC 970 derived CPU as the PS3, it just had three of them stuck together instead of one of them tied to seven weird Cell units. The TL;DR of how Xbox backwards compatibility has been achieved is that Microsoft’s whole approach with the Xbox has always been to create a PC-like environment which makes porting games to or from the Xbox simpler.

    The real star of the show here is the Windows NT kernel and DirectX. Microsoft’s core APIs have been designed to be portable and platform-agnostic since the beginning of the NT days (of course, that isn’t necessarily true of the rest of the Windows operating system we use on our PCs). Developers could still program their games mostly as though they were targeting a Windows PC using DirectX since all the same high-level APIs worked in basically the same way, just with less memory and some platform-specific optimisations to keep in mind (stuff like the 10MB of eDRAM, or that you could always assume three 3.2GHz in-order CPU cores with 2-way SMT).

    Xbox 360 games on the Xbox One seem to be run through something akin to Dolphin’s “Übershaders” - in this case, per-game optimised modifications of an entire Xenon GPU stack implemented in software running alongside the entire Xbox 360 operating environment in a hypervisor. This is aided by the integration of hardware-level support for certain texture and audio formats common in Xbox 360 games into the Xbox One’s CPU design, similarly to how Apple’s M-series SoCs integrate support for x86-style memory ordering to greatly accelerate Rosetta 2.

    Microsoft’s APIs for developers to target tend to be fairly platform-agnostic - see Windows CE, which could run on anything from ARM handhelds to the Hitachi SH-4 powered Sega Dreamcast. This enables developers who are mostly experienced in coding for x86 PCs running Windows to relatively easily start writing programs (or games) for other platforms using those APIs. This also has the beneficial side-effect of allowing Microsoft to, with their collective first-hand knowledge of those APIs, create compatibility layers on an x86 system that can run code targeted at a different platform.


  • Yeah, Windows’ bullshit is what drove me to Linux in the first place. I only have it on my gaming system, and only because Discord’s stupid screensharing doesn’t transmit audio on Linux, NVIDIA’s drivers for Linux suck balls (going AMD next time now that their cards are good again) and there are a couple of games my friends play that have issues on Linux. I’ve never run into a game on my everyday laptop that Linux couldn’t run, and the Steam Deck will take basically whatever you throw at it.

    Windows is a barely-functional rat’s nest of code spaghetti that falls apart at complete random. Sometimes your audio drivers will just stop working for no apparent reason. Sometimes your computer will just refuse to connect to the internet until you do a clean install. Windows Update apparently runs Prime95 in its spare time and so does the Antimalware Service Executable. I hate using it so much. I wish Windows would just curl up and die.






  • Did you read the article? Excerpts include:

    Generally, in business, it is sensible to provide your customers with what they want. With Twitter, the meme-makers’ favourite billionaire is doing the opposite. The cyber-trucker is trying his best to cull his customer base.

    Threads is what would happen if Twitter and Instagram made out in a bowling alley. It’s all their worst parts combined - but it may well succeed. Rocket-man Musk’s changes to Twitter have not exactly made it ‘brand friendly’. Threads, meanwhile, is shaping up to be a paradise for in-your-face brands - and the AdTech industry would love for you to join them

    and

    Threads’ naffness won’t stop its success. It’s data-scraping fluffily dressed up as substandard corporate twaddle. It’s a cringe-inducing privacy invasion. It’s not meant for users, but that doesn’t really matter: you’re not a user, you’re a product.

    It’s describing Threads as a product not for users, but advertisers. The perfect brand-friendly non-place for companies to stick their marketing crap. That doesn’t really come across as a ringing endorsement to me.


  • Been using LineageOS with microG on my phone for the last couple of years out of a general distrust for Google, using open-source apps in place of the Google ones. My phone stopped getting OEM updates after Android 12, so being able to use Android 13 through LineageOS is a plus. Main downsides are that some apps don’t play nice with microG and that unlocking the bootloader makes banking apps stop working.



  • In the case of the Surface Go family, there isn’t really anything comparable from other companies. It’s unironically the best compact tablet I’m aware of that you can put Linux on, and it runs Pop!_OS without issue once you disable Secure Boot. The only better Linux tablet for me would be an iPad Mini, but you can’t put Linux on one of those and even if you could it’s ARM-based so most proprietary apps won’t work on it.

    In general, your tablet options for something smaller and handier than full-size 2-in-1s are pretty limited if you don’t want to be running iPadOS, so excluding Microsoft’s devices from the running if you want to put Linux on your tablet is pointless. Yeah, buying a Surface Laptop to put Linux on there is a bit weird, but I can see the Surface Pro family yielding a good ARM Linux tablet some day.



  • Centralisation in this instance refers to control over the network and standard itself rather than control over what’s posted on it. There’s no single authority that can unilaterally change how every Fediverse instance and system works - for example, there isn’t anyone who can decree that from now on Lemmy will no longer allow connections from Canada, or that nobody is allowed to post pictures of capybaras any more.

    It’s intended to prevent a /u/spez or Elon Musk situation where one asshole can bring down the entire ecosystem built around an API. Nothing stops anyone else from hosting their own instance if they dislike lemmy.world, whereas if you don’t like Twitter, you can’t just host your own copy of it.





  • They really weren’t, though.

    Yeah, the Panzer III was better than a lot of the early-war British and French tanks, but that isn’t really saying a whole lot and it didn’t have any room left to grow after the long 50mm upgrade. It was arguably the best all-rounder tank in the world in 1939 with its torsion bar suspension and great ergonomics, and its chassis endured right to the end of the war in the form of derivatives like the StuG, but it wasn’t exceptional in any way.

    The Panzer IV became a pretty good medium tank around 1942-3, but by then the T-34 had overcome the worst of its early teething problems and received a less awful turret, and the M4 Sherman, which totally outmoded the Panzer IV was entering production. Plus it was still ultimately a 1930s design (if a rather forward-looking one) with crappy suspension.

    The Tiger I was a pretty good heavy tank for 1942 but still, ultimately, just a heavy tank. It was never intended to be a mass-production vehicle making up the bulk of a fighting force. It was a specialised tool that did its job pretty well, not a battle-winning wunderwaffe.

    The Panther was a 45-ton tank made out of parts designed for a 30-ton tank. Reasonably quick in a straight line, handled nicely when it worked, solid medium-calibre gun but it broke down frequently and was quite maintenance-intensive - this was less of a problem on the specialised Tiger I than on the Panther, a tank intended to replace the Panzer IV as the standard tank of the German army.

    The Tiger II was frankly insanity. All the Tiger II really needed to be was a streamlined Tiger I with sloped armour, a longer gun and a redesigned turret. Instead, it became an immobile 70-ton brick that was never available where it was needed and was generally a total waste of resources. Let’s not even talk about the Jagdtiger.

    Sure, the Germans had some very effective guns - the L/70 and the 88s - but it’s not like nobody else did. The British ended up with the very effective OQF 17-pounder, the Americans actually had the 76mm M1 and its derivatives pretty early on but didn’t much use it because the 75mm was more than “good enough” until Panthers started appearing in large numbers, and the Soviets had their own very effective 85mm and 100mm guns.

    The 128mm on the Jagdtiger was frankly absurd overkill considering the long 88 was already eminently capable of putting down the bulk of Allied armour at long ranges; the Jagdtiger really doesn’t offer much advantage over a Jagdpanther in practical terms outside of hypothetically fighting Allied counters to the Jagdtiger like the Tortoise, IS-4 and the various American super-heavies (T28/T95, T29,30,34). At least the IS-2’s 122mm cannon had the excuses of being an expedient use of surplus equipment and the larger shells being a better fit for infantry support since they could fit more HE filler.