There was the 386DX and significantly cheaper SX - first was full 32 bit, second just 32bit instruction set with smaller external busses.
Then you could add the math coprocessor. And of course RAM and disks were expensive. 16MB RAM was way above normal for that time.
About 20 years ago I made a script that converts pictures to HTML tables. Back then RAM was a severe problem for this, and even for more powerful hardware browsers tended to just crash on larger pictures.
I checked it again a few years later, and things looked way better. I guess using CSS it'd be rather trivial nowadays to do the same with a short video by just cycling through showing/hiding tables of each frame.
Paid and FOSS are not mutually exclusive. You can always build packages yourself if you don't want to pay. A well executed implementation might allow some projects to drop or reduce their play store efforts.
Ukraine took hundreds of prisoners so far, and a fair share of that probably are conscripts. That already is a bit of a mess he'll have to solve.
the "whatever that might be" in that context meant "the machine dependent format could be anything, and it wouldn't matter for B"
Haengt halt von deiner Vogelpopulation ab - Tauben sind doof, gegen die hilft das. Kraehen, Elstern und andere Rabenvoegel bekommen die eventuell zerlegt, und benutzen die dann zum Nestbau. Lustigerweise scheinen die teilweise die Spikes im Nest zur Abwehr von anderen Voegeln zu nutzen.
x230 with x220 keyboard also is pretty nice - but unfortunately no longer suitable as main notebook. As nothing useful came out of lenovo after that, others are even worse, nobody has a decent trackpoint and sensible amount of RAM only exist for macs I ended up with one of those for work few months ago.
Pretty much same here - I kept an x230 alive until I had to accept earlier this year that it just is bad for overall productivity, and ended up getting a macbook. None of the newer thinkpads are good - and they're still one of the less bad manufacturers.
There's also enough stuff I don't like about the mac - but the current keyboard is one of the better notebook keyboards available right now, and if you want long battery life, lots of RAM and a lot of CPU power available in a compact device they're the only manufacturer currently offering that.
Im Homeoffice mach ich neben dem Fruehstuecken die ganzen Nervtasks die keine volle Aufmerksamkeit brauchen - Mails checken, Monitoringzeug durchgehen, ...
Dafuer sitz ich dann auch gerne mal ne Stunde am Fruehstuecken bevor ich an den "richtigen" Rechner gehe - ist ein entspanntes Fruehstueck, und ein entspannter Start in den Tag.
Oder ich beeil mich halt dass ich ins Buero komme, und bin dann halt genervt dass ich jetzt den ganzen Aufwand hatte nur um die erste Stunde im Buero nix nuetzliches zu machen.
I’m not super familiar with MacOS, but do you know if Gatekeeper or XProtect run at ring 0?
Gatekeeper does mainly signature checking. XProtect does signature checking on an applications first launch. Both of those things would be pretty stupid to implement in ring 0, so I'm pretty sure they are not.
If they do run at ring 0, would you consider that anticompetitive?
No, as they're not doing any active monitoring. They're pretty much the "you downloaded this file from the internet, do you really want to run it?" of MacOS.
I’m almost certain Apple will move or did move to depreciate kernel extensions. Which means it would be the same situation Microsoft wanted to force as you described.
That is indeed the case, but I'm not aware of any Apple products relying on being a kernel extension. Apple is facing action from the EU for locking down devices from device owners, though - mainly applying to phones/tablets. On Macs you can turn pretty much everything off and do whatever you want.
The other argument with Defender is you could at least have a choice to use it or not.
Without providing a proper API Defender (both the free one, and the paid one offering more features) would be able to provide more features than 3rd parties. Microsoft also wouldn't have an incentive to fix the APIs, as bugs don't impact them.
The correct way forward here is introducing an API, and moving Defender to it as well - and recent comments from Microsoft point in that direction. If they don't they'll probably be forced by the EU in the long run - back then it was just a decision on fair competition, without looking at the technical details: Typically those rulings are just "look, you need to give everybody the same access you have, but we'll leave it up to you how to do it". Now we have a lot of damage, so now another department will get active and say "you've proven that you can't make the correct technical decision, so we'll make it for you".
A recent precedent for that would be the USB-C charger cable mandate - originally this was "guys, agree on something, we don't care what", which mostly worked - we first had pretty much everything micro USB, and then everything USB-C. But as Apple refused the EU went "look, you had a decade to sort it out, so now we're just telling you that you have to use USB-C"
That's bullshit. Microsoft wanted to force others to use an API, while keep using kernel level access for Defender (which for enterprise use is a paid product). That's text book anti competitive. Nobody ever had a problem of Microsoft rolling out and enforcing an API for that if they restrict their own security products to that API as well.
With my N900 I used to travel with 6 to 10 charged batteries to have a few days of runtime. Things got better now with powerbanks - but for something like hiking just carrying a few spares would still be smaller and lighter.