Linear is probably starting to hit enshittification territory. The feature bload is immense and they are trying extremely hard to not be left behind on the AI wave.
Why are we treating LLM evaluation like a vibe check rather than an engineering problem?
Most "Model X > Model Y" takes on HN these days (and everywhere) seem based on an hour of unscientific manual prompting. Are we actually running rigorous, version-controlled evals, or just making architectural decisions based on whether a model nailed a regex on the first try this morning?
For me, GitHub CLI is the prime example of this. This CLI is so incredibly powerful when combined with regular command line tools. Agents know how to use head, tail, jq and so on to only extract the parts it needs.
The best selling point of CLIs is the ability to chain, transform and combine. MCP cannot do this.
I agree. If you strictly follow the syntax of "Example 1" in JavaScript (calling and awaiting on the same line), the observable output is identical to Python.
I suppose the author meant to say that if you first called your async function and then later did `await` you would have different behavior.
I think something like the matrix protocol would be better. I would be especially interested in not storing unencrypted user messages. Matrix would be a good choice for this.
I've been thinking a lot about building an open source dating app as a non-profit offering.
I have a sense that succesful dating contributes highly to overall human happiness. It should be a public service similar to wikipedia or libraries.
Free forever, fair and safe, and responsibly managed. It's probably not that expensive to run. But idunno, i'm kinda frightened to "compete" in this market
bluesky https://bsky.app/profile/mikkelam.bsky.social
website: https://mikkelam.com
Software @ Reshape Biotech YC W21