They've got blog posts of we had to rewrite this whole thing because the performance was bad. If it was always hotspots that made your performance bad, you'd never have to rewrite the whole thing. So, we know that that doesn't work anymore.
Technologies from our community - CRDTs, sync engines, universal version control, and good old-fashioned open protocols and file formats - can give a nation more independence and control over its own critical software infrastructure.
I don't think anyone found it useful enough to like maintain a system to keep the specs and the code in sync versus just using the code as the source of truth always.
GPT 5.5 is the only model though that has the sense of agency and confidence to just like rip out old code and just like actually rewrite from first principles.
Here's a prediction. I'm pretty sure every coding model on the market will still do this in a year. Every coding model on the market will take that instruction seriously.
No new feature necessary. Just make sure that we can do that. And then that allow the business the company to just pour a whole bunch of hardware behind that and it will scale.
I go back to usually when people are unhappy it's because these things are a little bit out of sync. Like they want this big thing, but they don't actually they're not actually excited about what it takes to do that thing and therefore it's just going to be a mismatch.
Agentic and sync are natural complements because local-first is multiplayer by default, and agents are another sort of "player" in addition to human collaborators.
To read papers, I use Adobe Acrobat Reader and sync them in the cloud. This lets me read, highlight, and sync my papers across devices (work laptop, personal laptop, iPad). Instapaper does the same for online articles.
To read papers, I use Adobe Acrobat Reader and sync them in the cloud. This lets me read, highlight, and sync my papers across devices (work laptop, personal laptop, iPad). Instapaper does the same for online articles.
When you serve your pages over HTTP, anyone along the transport layer can do basically anything they want to your pages. More and more often it's becoming increasingly common for somebody in the chain of custody to do something to your pages that you don't want them to do.
I use Outlook to maintain my calendar and address book. I hate that program, too, but I can't find anything else that lets me sync locally to my iPhone without going through the cloud.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.