I believe it’s 1% for access to the “entire post-open ecosystem”, rather than 1% per project which would be unreasonable. So you could use one or thousands of projects under the Post-open banner, but still pay 1%.

It will take years to develop the post-open ecosystem to be something worth spending that much on.

This really got me, thank you!

Literally just bought what I believe to be last generation’s X13 on ebay for half the price of the new one. It’s been great so far, especially with the power efficiency of Ryzen CPUs. My one complaint is the soldered RAM, which judging by the new lineup is getting phased out, thankfully.

I’ve been programming for too long, my brain just autocorrected the typo so initially didn’t get the joke…

Again, this existed before AI. Typo squatting, supply chain attacks, automated package uploads, CI pipeline infection, they’re all known attack vectors. That’s not to say this isn’t a concern, just that it’s a known risk and the addition of “AI” doesn’t, to my eyes, increase that risk. If your SSH keys don’t require a password, you have taken the decision to make those keys less secure but more convenient to use. That’s pretty much always the tradeoff in security.

The risk here is slightly overblown or misrepresented. Just because a fork exists doesn’t mean that anyone has even read it, let alone run it on their system. For this to be a real threat they would have to publish packages with identical or similar names (ie typo-squatting) to public package repositories which this article didn’t have any information on but which is a known problem long before AI. The level of obfuscation and number of repos affected is impressive but ultimately unlikely to have widespread impact to anyone besides GitHub.

My take (having neither but building a NAS in the background of other jobs) is that if you don’t need the rack, don’t buy the rack. If you already have a NAS and you really want to play with the power that a rack would give you, go for the rack. If you don’t need it don’t buy it, simple as.

Personally I rename them to something meaningful and they get merged if there are no other references. PayPal is especially bad for completely meaningless rubbish in the payee field and they tend to be ad-hoc purchases so I don’t fiddle with them much. The category is the most relevant bit for me.

I think for most people it’s whatever you got used to first. I agree the hatred the GUIs get is overblown. I would always recommend people learn the command line but if you want to use a GUI, go for it, doesn’t affect me unless your commits are bad, in which case the CLI wouldn’t have helped anyway.

My friend and I are looking to make a game and the general consensus has been that perforce is still better than git LFS, so we’re setting up a perforce server. What is it about SVN and perforce that you miss? I’ve only ever used git professionally for VCS so I’m finding perforce’s always-online and exclusive-checkouts model just very strange (though I understand the need for it when working with binary files).

I’ve heard the argument as a positive of learning vim and while it did finally force me to touch type I can’t say that it had any impact on my programming speed.

I agree with those saying mailing lists are intimidating. I don’t know if others are using dedicated tools or something but I find web based mailing list UIs just incomprehensibly bad and difficult to navigate.

“Too slow to be viable” is a bit strong. I’ve had a fairphone 4 for at least a year now and I’ve had no issues.

The “Invaders Must Die” fight in Hi-Fi Rush had me beaming ear to ear. By that point in the game I was so in tune (intended) with the mechanics I just chewed through the fight, headbanging the whole time. One of my all time favourite gaming moments.