@brandur I think so.
Fwiw, I did find a niche use case for it, e.g.,
func (s *State) GetFlag[T any](name string) (T, error)
https://t.co/UX2e4ITgL9
Not sure if it's justified, but might as well if it's in the language.
@thinkwithmark Maybe something silly .. let the user "mark" the page number where they start, then mark the last page when done.
That gives me the time/day of the session and start/end pages, so I can build some neat metrics around reading pace, pages per session, streaks, etc.
Today, we’re open-sourcing the draft specification for DESIGN.md, so it can be used across any tool or platform. We’re also adding new capabilities.
DESIGN.md lets you easily export and import your design rules from project to project. Instead of guessing intent, agents know exactly what a color is for and can even validate their choices against WCAG accessibility rules.
Watch David East break down this shared visual language in action👇. New capabilities and links in 🧵
🤯BREAKING: Alibaba just proved that AI Coding isn't taking your job, it's just writing the legacy code that will keep you employed fixing it for the next decade. 🤣
Passing a coding test once is easy. Maintaining that code for 8 months without it exploding? Apparently, it’s nearly impossible for AI.
Alibaba tested 18 AI agents on 100 real codebases over 233-day cycles. They didn't just look for "quick fixes"—they looked for long-term survival.
The results were a bloodbath:
75% of models broke previously working code during maintenance.
Only Claude Opus 4.5/4.6 maintained a >50% zero-regression rate.
Every other model accumulated technical debt that compounded until the codebase collapsed.
We’ve been using "snapshot" benchmarks like HumanEval that only ask "Does it work right now?"
The new SWE-CI benchmark asks: "Does it still work after 8 months of evolution?"
Most AI agents are "Quick-Fix Artists." They write brittle code that passes tests today but becomes a maintenance nightmare tomorrow. They aren't building software; they're building a house of cards.
The narrative just got honest: Most models can write code. Almost none can maintain it.
@bentlegen lol, no. There’s an open source cli tool called goose I’ve been maintaining for years.
But pretty sure the goose everyone knows nowadays…
https://t.co/1yZTMF7UM2
@bthdonohue@rattasupernote Ohhh curious how this goes.
I’ve now watched hundreds of hours on eink tablets from ReMarkable to Supernote to everything in between.
But haven’t pulled the trigger. 😬