zild3d

maybe a bit, but 360 panoramic image still doesn't really address things out of direct line of sight. e.g. in a house, go through a door to a room, come back it's a different room :P

or even if you have a vast line of sight but a guy goes behind a tree

ah yes, the ol' bury your head in the sand approach

they are separate questions about the input. One question can be "is this a complaint?" and another "Should we flag this email to security" and a third "Is the sender a Bush era republican?"

90% of the {muse,grokbot,instinct,dots,...} fuss is just that your {aunt,cousin,neighbor's dad} probably doesn't have a good codex or claude code setup, and probably does not have a great local machine to run them from anyway.

So everyone is trying to give the aunts, cousins, neighbor's dads some of the agent capabilities that developers have been closer to.

That said, there's the other 10% here that is not necessarily new capability unlocks vs codex, but general product experience that can have some benefit to people already used to what the latest models can do

> I'm never in need of a tablet.

Apple sold something like 60M ipads in 2025. Perhaps you are not the target audience

just a quick thank you for steak-hard, smiling over here

well its not a free as in beer color space

I think you'd want to remove e.g. knowledge of harry potter universe and ancient egypt. Training on a bunch of high quality java code bases is still likely to improve your python model.

> What about AI research itself? Is OpenAI close to automating its human staff out of a job?

It's more like they've already automated the parts of the jobs that the humans most closely thought of as the "their job"

> Imagine if you were given a layer of abstraction that randomly flipped bits from time to time... That's not an abstraction, it's random programming.

Computing has never really been deterministic all the way down. Storage gets corrupted, RAM has soft errors, networks drop/reorder packets, schedulers race, caches go stale, distributed systems partition, query planners change plans, ...

Obviously those become tolerable because we've developed layers of contracts and understanding the bounds around them. Error correcting codes, checksums, retries, consensus, idempotency, false-positive rates, SLAs, etc.

If the abstraction is “delegate this task to a junior engineer, analyst, lawyer, designer, or support rep,” you dont expect deterministic behavior. There's review, constraints, escalation, checklists, tests, and accountability.

Iran's 10-point plan (that no one else has agreed to)

whats surprising about that? most of the minor version updates from all the labs are post training updates / not changing knowledge cutoff