I have a 96 core one. While it’ll be fine as a desktop for compiling I’d stick with an AMD system.
The devkit has 6 memory channels, and you’ll want to fill them all - there’s a surprisingly high performance penalty if you don’t. Even then, compiling a code base which could be spread over hundreds of cores is still significantly slower on the ampere compared to my old 3970x.
I’m fine with that. I don’t want to talk with people - I just want an email address to write to.
And as soon as I learned about that I stopped using it. Turns out it was the right choice - since then more then one company had breaches where authenticator seeds extracted from a google account were used to bypass 2fa.
You still had a 4GB memory limit for processes, as well as a total memory limit of 64GB. Especially the first one was a problem for Java apps before AMD introduced 64bit extensions and a reason to use Sun servers for that.
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.
Everything is deployed via ansible - including nameservices. So I already have the description of my infra in ansible, and rest is just a matter of writing scripts to pull it in a more readable form, and maybe add a few comment labels that also get extracted for easily forgettable admin URLs.
As a non-Windows-user I see that as a good thing. LLMs are not going away - but that kind of nonsense at least will make sure all PCs will eventually have cheap and reasonably fast AI acceleration. Which is required for killing off centrally hosted LLMs (plus nvidias cash grabbing)
Even in this thread I’d rather phrase it explicitly to include everyone - I’ve seen statements like this interpreted by some individuals as “make it welcoming for women at all costs, which may include making it openly hostile for people not meeting my specific definition of woman”, which didn’t have a very pretty end result.
Make sure you’re helping make Lemmy a welcoming place for non-males
I’d phrase that as “make sure you’re helping make Lemmy a welcoming place for everybody”
Being active in a pretty friendly tech scene in the late 90s/early 00s I’ve seen things being ruined for quite a bunch of people who enjoyed being where nobody was judging them for who they were or wanted to be after a bunch of newly joined women decided to try force a bunch of “women only” policies.
Just don’t be dicks to each other, no matter who’s on the other end. And don’t try to force talking about who you are in places where nobody cares - there are specific groups for that.
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.