I don't think there's a particular need to defuse into a productive discussion. Something like that, with no repro or respect - lock and close.
The first version included a 'Fuck you' but they edited it away.
I was wondering why it didn't show as a cross post in the lemmy-auto-linking discovery. The desc-linked source doesn't load at all for me.
I hope this isn't considered a "meme" by the rules. Kinda depends on the definition - which the rules has none of.
Depends on the spec/implementation. If it's random generated tokens then I imagine they're not [necessarily] one per user. You could generate an arbitrary number and get new ones arbitrarily, regularly.
Without some technical information, with only this press release, we can't tell.
The title is non-telling, the metadata page description is non-telling, no post description. What is this about?
This community's rule 3:
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
Looks like the video itself also has no useful description. Only an unlabeled ad.
Copying the generated AI summary from YouTube from the description section:
The PrimeTime analyzes claims made by Anthropic and Boris regarding the state of modern software development. By examining technical issues with Claude Code, this critique questions the narrative that coding is largely solved, suggesting that the current push toward fully agentic workflows might be misleading and potentially harmful to professional software engineers.
dead
Connection timed out Error code 522
What's the tl;dr? What's the language for?
I scrolled through, but it wasn't quite obvious.
Private Access Control Tokens (PACT) are designed to allow sites with strong knowledge of “personhood” to issue anonymous tokens.
A centralization of authorization. So that's why Google and Microsoft are interested.
If it's open enough, could still be a net-positive.
Depends on the mechanism though. Too weak and it can be automated and misused, losing "it's a human". Too strong and there's more concerns about privacy, control, and centralization of the selected auth providers and browsers making the selection.
Maybe hosters could use their own trust lists, like Firefox does for certs. But most will just go with the big and common default set.
I'd prefer skipping the anti-ai guards. But having to give a passwort to Google for it? I don't know. They'd have enough data on me to know I'm a human without it.
This is a press release. Is there more technical or concise information?
I'm sure you'll get a break once all questions have been answered
Metaverse First: Verse is designed for a future where code runs in a single global simulation—the metaverse. This influences every aspect of the language, from its strong compatibility guarantees to its effect system that tracks side effects and ensures safe concurrent execution. - Book of Verse
😕
As UE5 and UEFN merge into one editor, you will be able to ship traditional games and projects exactly as you do today. You’ll be able to ship directly in Fortnite, or ship to your own ecosystem, and optionally, make it compatible with ours. You’ll have an easy path from one to another.
Our philosophy through this transition is to bring existing projects along, not to force a hard break. Studios shipping on UE5 today should expect a manageable, and clear path forward when UE6 is ready for them. To allow for this, Actors and Blueprints will be in early versions of UE6. Eventually, these will be deprecated when the new framework is sufficiently mature, and you’ll have conversion tools to move projects from one framework to the other.
I'm surprised they're targeting a hard break. The goals seem to be platform onboarding, which can be considered an opposite goal to people who develop their own products.
What makes you think it's a lockfile issue? If they sighted a patch upgrade then updated the lockfiles but then noticed a breaking change, then lockfiles are irrelevant.
If it's actually like they claim, I understand the frustration. (Not that I know this project in particular or how it gets integrated.) Without clear versioning and/or changelogs/release notes managing upgrades is cumbersome, sometimes impossible.
In some cases I've had to ask for clarification in PRs because release notes were not clear, PR was not clear, and resolved ticket was also not clear on the thing or solution.
Apparently they had issues before, so maybe they could have expected "patch may not be patch-only".