replygirl

wordle is just a copy of mastermind

this is common practice, works pretty well in my experience both to improve quality and reduce cost, and afaik is a naive version of what tools like coderabbit and greptile do internally

it was called brick on the ipod.

woz and jobs did work on breakout at atari

purple isn't real, there is only more blue.

reaction latency doesn't cover everything. the round trip from trigger to action is a few hundred ms at best, yes, but to enable that we are processing inputs at ~30hz minimum and integrating at ~5hz. you would total your car pretty quickly if you couldn't constantly adjust

the problem is that single-source advantage gradually falls away as you develop your software into something that feels good to use on each platform. and once you have a quality product you're left with perfunctory coupling that makes it harder to adopt the latest platform features

pair programming is when two people collaborate on engineering decisions while one of them codes.

the connection, schema, and migrations are all separated so looks pretty easy to swap in your own ORM or have another service own data

it's impossible to say, as v1.4 is in development and there has been no migration

just since 2025?

i'm saying all positive claims need to be justified, not that priors are exempt. there is one claim with a vast body of evidence supporting it, and a competing claim that must meet the same standard. the world is not so magically different now that we can't look at software engineering and computer science the same way we look at real (credentialist, regulated) science and engineering disciplines. really all i was implying is "peer review WAS vital" is jumping the gun

likewise, taking a wrecking ball to systems refined over centuries should come with some burden of proof for the positive claim that a tool can replace an institution. most times this has happened before, we've had to strengthen credentialing requirements to stop people from dying

OP says "you want to select a whole Markdown document built from SwiftUI primitives", but who wants that? what sort of product thinking tells us we want that? that sounds like a document editor, which has been hard to build for decades and sounds out of scope for an llm chat ui. everyone has landed on only supporting selection within each contiguous block, with a copy button for the entire message