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

help-circle
  • Screen is another thing - but I can live with that, mostly - it’s a bit hard to find x86 notebooks with decent resolution (not talking retina style, just better than “1080p on a 14 inch display”). And while the screen itself is nice on the apples I’d prefer a lower resolution one if I can get a matte screen instead.

    But fact is that nobody wants to sell you a proper x86 notebook. It’s almost impossible to find something with more than 32GB of RAM, and while there are a few with more than 64GB they’re all xeon based monsters larger than 16", as far as I can tell can’t really be ordered, and have a price tag equal or larger to a full spec 14" mac book pro. And obviously you can’t really think about battery life with intels space heaters.

    It’s especially sad as current mobile Ryzen CPUs could very well compete with Apples ARM CPUs - the one thing Apple is better at is the absolute low power state, as soon as it has too actually do something the power (and TDP) curve is very close to mobile Ryzen. But pretty much every manufacturer fucks up the thermal design, or gimps it in other ways.




  • The space used by the smallest solar charger I’ve seen on Amazon seems to be similar to 6 or more batteries in the format the N900 was taking - so if you look at space, slow charging from solar charger, and reliance on sun conditions taking individual batteries seems to be the better option for a few days hike. It’s also easier to stow individual batteries to wherever you still have space left.





  • AMD keeps some older generations in production as their budget options - and as they had excellent CPUs for multiple generations now you also get pretty good computers out of that. Even better - with some planning you’ll be able to upgrade to another CPU later when checking chipset lifecycle.

    AMD has established by now that they deliver what they promise - and intel couldn’t compete with them for a few generations over pretty much the complete product line - so they can afford now to have the bleeding edge hardware at higher prices. It’s still far away from what intel was charging when they were dominant 10 years ago - and if you need that performance for work well worth the money. For most private systems I’d always recommend getting last gen, though.



  • This doesn’t have anything to do with user control - modern windows versions need drivers to be WHQL signed to get that kind of access. Alternatively you’ll need to enable developer mode on your system, and install your own developer certificate into its keyring for running own code, which has its own drawbacks.

    Crowdstrike is implemented as a device driver - but as there is no device Microsoft could’ve argued that this is abusing the APIs, and refused the WHQL certification. Microsofts own security solution (Defender) also is implemented as a device driver, though, and that’s what the EU ruling is about: Microsoft needs to provide the same access they’re using in their own products to competitors. Which is a good thing - but if Microsoft didn’t have Defender, or they’d have done it without that type of access it’d have been fully legal for them to deny the certification for Crowdstrike.

    Both MacOS and Linux have the ability to run the type of thing that requires those privileges on Windows in an unprivileged process - and on newer Linux versions Crowdstrike is using that (older versions got broken by them the same way they now broke Windows). So Microsoft now trying to blame the EU can be seen as an attempt to keep people from questioning why Microsoft didn’t implement a low privilege API as well, which would’ve prevented this whole mess.






  • Unless you are gunning for a job in infrastructure you don’t need to go into kubernetes or terraform or anything like that,

    Even then knowing when not to use k8s or similar things is often more valuable than having deep knowledge of those - a lot of stuff where I see k8s or similar stuff used doesn’t have the uptime requirements to warrant the complexity. If I have something that just should be up during working hours, and have reliable monitoring plus the ability to re-deploy it via ansible within 10 minutes if it goes poof maybe putting a few additional layers that can blow up in between isn’t the best idea.