[–] 13 points 4 months ago*

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.

  • source
  • [–] 5 points 4 months ago* (2 children)

    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?

  • source
  • [–] 2 points 4 months ago

    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.

  • source
  • [–] 10 points 5 months ago (1 child)

    The quoted text makes no sense. It has gaps. And the comment you dismissed seemingly pointed that out.

    Websites don't have a file system. They serve content as responses.

    PHP is not a filesystem. ASPNET is not a filesystem.

    You could be talking about managing files, you could be talking about sourcing web responses from local files, or you could be talking about something else.

  • source
  • parent
  • context
  • [–] 2 points 5 months ago*

    I would expect it to apply to everything. You don't want to hit the issues in the first place.

    It seems like a weighing of (safe) CPU support vs better generated instructions. If you don't care about a CPU generation, maybe because it's old enough, or your target environment is restricted/controlled, you don't enable it. If it's still out there and you want to or have to support it, you enable it.

    I would imagine a "CPU-Workaround--" or something, and if you enable it, it completely evades the instruction constellations that cause the issues and uses alternatives instead.

    Maybe it could have "evade completely" (same code runs on every CPU) and "generate cpu-checked workaround code branches" (faulty CPUs execute a different branch) as alternatives.

  • source
  • parent
  • context
  • [–] 4 points 5 months ago (3 children)

    Shouldn't compilers (in this case LLVM) cover such CPU bugs with flags? So users can commit to either evading CPU bugs or not.

    It'd also be a good entry-point and overview of what CPU bugs are out there. Without it, how are you supposed to know about and evaluate them?

  • source
  • [–] 5 points 5 months ago*

    ?utm_source=chatgpt.com on "W4 Games" link. Did they summarize or generate through chatgpt and copied from chatgpt? It certainly doesn't seem like deliberately designed link handling.

    Linksource tracking/marketing chatgptcom doesn't make sense to me on other websites. But it's interesting that it effectively produces distributed chatgpt-source links.

  • source
  • view more: ‹ prev next ›