Seems fair to me. The VC-backed SQLite services have been shouting about their services as if they came up with the idea, and this only balances that out.
He's right that histories start too late, and I'd like to see more posts like this that trace the history back further than the last 5 years. Like for databases, a lot can go back 20+ years and it's good to read how the idea came about (independently from many people), how it developed over time and why.
Also "Blitz Street" with Tony Robinson, where they build a street of typical 1940s houses and slowly increase the WW2 bomb size to see the damage the would do.
I'm just about to build my own external temperature and humidity sensor, using a Sensiron SHT45 sensor with integrated PTFE filter.
I've had Tuya and Aqara sensors outside, undercover and out of direct rain for the past 3 years, and every one lasts about a year before the humidity sensor gets stuck at the maximum reading. Even bringing it indoors doesn't get it working again. I'm hoping the built-in heater on the SHT45 will help when we're sat in sea mist or sea fog and keep the sensor working for longer.
What would be the correct way to do benchmarking/profiling here? I ask as I've started to run some for Vinyl cache to see what performance issues I can find, and I've quickly learned just how hard it is to get good, repeatable benchmarks that isolate the right thing.
No easy answer! You’d have to have a myriad of different test suites that as closely resemble your real world usage as possible. Or ship it behind a gate and let your users give you real world feedback if you’re at SQLite (not turso) scale - they’ve done that with a lot of ambiguous optimizations.
Yeah many are trying to solve this. It's really not easy to get the UX right. Git changes can get deep and wide
I wanted to have a simple way to navigate my story in a tree form but cli is really not great in displaying those. Lazygit is the best imo but still not great. WebUIs are not really better
Looms seem to work a bit better, which is also what 1667 is based on. But still I don't know needs work
I like seeing what people create, and you've created something with some interesting features, particularly around the path map and keeping all drafts. I'm forever duplicating a paragraph and rewording it 6 or 7 times, then deleting the rest - and the next day think "no try #2 was better than the one I kept".
Ignore the haters, they're a HN rite of passage. Good luck with your writing!
I think you've built some awesome. Even if, as you said, it proves to be for an audience of one (you), I know some people out there are grateful for you sharing it. Comments are not reality most of the times. There is a silent portion which would like your idea and you just don't know. People here in HN tend to be very polarized towards a certain idea, come up with intellectual arguments to justify their emotional reactions. Of course you can find some light in negative comments, but still, to be taken with a grain of salt.
Someone said "a generation growing up without imagining. So depressing." This reads like old man yells to clouds. Through history you can find these comments about upcoming generations all over the place... We can make the same arguments in the past "oh you spend so much time reading others stories instead of writing your own? Yeah, you lack imagination kid, you're in big trouble."
To have nuance and avoid over-generalizing is a good exercise in today's society I guess.
Thank you. I didn't think this would be so controversial. A few people are in my email inbox with nasty comments. I've removed my email from the website. I'm not used such visceral hate.
Anyway I have children myself. They play, they write, they draw. And occasionally we do tech stuff like this. I use it as a choose-your-own-adventure with them. We also make up our own stories for bedtime. I don't see these things as exclusive
All of this, but underlying it I've come to the conclusion that Markdown isn't a good format for a writing environment beyond just simple prose. There's too much left up to the flavour of it and it's got weaknesses.
I've been experimenting with using Markdown (in Typora) in place of Word, but it (and others I've looked at) have zero support for image positioning or sizing, or a way to have different (pre-defined) styles on different tables.
Which is a shame because I like keeping my documents in plain text, in version control and efficiently read by my LLMs. LyX (https://www.lyx.org/) for LaTeX is the closest to what I'm thinking of that I know of, but maybe something exists for Asciidoc or Typst.
Can you say more? This sounds like it could be more useful than trying to build a knowledge base (say qmd) and then get the models to search it for the right context each time.
This is in fact what we do (with higher order abstractions now built on top of this). This builds self evolving interactive knowledge base and puts it into a QMD searchable index. The indexer is already open source: https://github.com/jibs/duffel
> I feel like this benchmark reiterates my disbelief that anyone uses the latest Anthropic models for any productive work. They seem to be the best at burning tokens and spawning unnecessary subagents even for well-defined and tightly scoped tasks.
I keep Claude around for some specific tasks:
- Linked up to Figma MCP to implement front-end stuff
- Data analysis, in the "Connect AI to a data source and ask questions" way. I've tried both Opus 4.8 high and GPT 5.5 high for this and Opus is stronger because it gets the intent in the question better
I used to keep it around for planning too, but the 4.8 plans have had more holes than swiss cheese.
He's right that histories start too late, and I'd like to see more posts like this that trace the history back further than the last 5 years. Like for databases, a lot can go back 20+ years and it's good to read how the idea came about (independently from many people), how it developed over time and why.