The self-contained electron app works better for most people I think.

Didn’t they effectively kill the oculus rifts with required logins and no more support?

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!

I for one am frequently so close to my very good friends that my nose is pressed against theirs, my eyes only able to see theirs, the world not existing around us, while discussing in a platonic way how their day is going.

I’ve not built anything beyond simple scripts in rust but I’m looking at some of the cosmic codebase to see what I can do.

That works until all* games come with root level anti cheat. It was the same with micro transactions which people still defend despite being utter shit.

• Realistically this will never be 100% but it will be enough of the mass market AAA games like CoD etc to mean that if you functionally want to play a game made in the last X number of years you will need to accept this or stop playing games altogether. I think most people will continue to play games. Most people will continue to install root level anti cheat, knowingly or otherwise, and all of them will get fucked by an exploit of that software. They may never even know about it.

Helldivers 2 does the same thing. If this continues it will be extremely advisable to move any non-gaming use-cases to a different computer as you have no idea what the “anti-cheat” is doing with that level of authority over your computer.

I would be curious how this actually works in practice. What counts as “in progress”? Encounters? Plot points? Knowledge that a goblin has? If all of those things are “in progress” and you can only have so many things in the “in progress” column, I feel like you’d very quickly have to break that rule and then everything becomes “in progress”.

Coming from a country that doesn’t have this sort of thing it’s really weird as an outside observer. Students have to swear allegiance to the flag every morning too which is the sort of thing I would imagine happens in north Korea or dictator states.

Kind of surprised this is getting so much criticism. It’s a thought experiment, not a call for a fundamental change to all PC UX. My only real argument against the idea is that it’s framed as being “for efficiency”. If you want efficiency above all else you would just go full command line.

How’s the battery life? I was considering one recently but saw some claim that the battery would only last 4-6 hours and that put me off.

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…

I’m in a team of 4 developers and we demand automated testing. Ok that’s part of a slightly bigger development team but even our QC team have automated tests that they run for integration testing.

You do you. People generally discourage rebase because it rewrites history but that’s what you’re doing anyway. You can achieve the same result with revase --interactive and following the instructions to squash all your in progress commits into a single commit. That way you don’t have to figure out how many commits between your in progress and dev(for your reset command) as the rebase will handle it for you.

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.

I’ve only used helm and hadn’t considered kustomize as an equivalent, what about kustomize makes it bette in your opinion?

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.