458 karma · joined May 9, 2013
And Claude Code Pro is also similar to ChatGPT Pro, being used in a TUI does not mean it is equivalent to an API.
Man, you can really feel the anxiety and desperation in Adam's reply.
Part of me wants to say "look what evil VC money does to devs", but that's only a harsh critism of a bystander.
Monetization is a normal path that the successful OSS projects would take. Tailwind went big on the startup route, took a bunch of VC cash a couple of years back, but despite the massive impact on the dev world, they clearly didn't hit the revenue numbers investors expected. Now the valuation bubble popped, and they're forced into massive layoffs. Though to be fair, maintaining a CSS library probably doesn't require that many people anyway.
I really feel for Adam here. He didn't really do anything wrong. Eagering to build a startup after your project blows up is a totally natural ambition. But funding brings risks. Taking other people's money makes you go from being the owner to just another employee real quick. And once you hop on that VC train, you don't really call the shots anymore. Sometimes you can't stop raising or scaling as your own will.
If you find a solid business model, that's great. But if not, well, honestly, a 75% layoff is getting off lightly. At least they still have a chance to keep on.
But he obviously didn't foresee this coming. He’s getting torn between being an OSS maintainer and a CEO who have to be responsible for stackholders and employees. That internal conflict must be brutal. It’s pretty obvious he didn't reject the PR for technical reasons. It's just because the reality hit him hard, and he has to respond to it, even if it goes against his mind as a developer.
Really hope Tailwind pulls through this. Also, this is a lesson worth noting for the rest of us. As indie devs, if you ever get the chance to take VC money, you really gotta think hard about whether you're truly ready for the strings that come attached.
Once my original broke and I realized they weren't making that specific design anymore, I just lost interest in buying from the brand. The new models just don't have the same appeal.
They share a lot of similarities:
- Round dial
- Analog hands (though Round 2 simulates this with e-ink)
- Long battery life (Round 2 is ~2 weeks. I remember Withings lasting months on a coin battery)
- Thin and light
- No speaker, so no noise
These are the features I appreciate. I love gadgets, but for smartwatches, I want them to maintain a classic watch appearance. I don't want to worry about charging it every day, and I don't want too many features and notifications to distract me.
As for the "smart" part, I want the tech to focus on sensors, i.e. recording movement and sleep. The rest goes for aesthetics, like changing interesting watch faces now and then. That's really it. Most products on the market are no what I want because what the tech brings on them are interference and inconvenience.
I was happy to read this part at first, because it highlights what I hate most about Headless CMS. Hearing a company in the industry admit to this problem gave me hope that they are now going to fix it or have better solutions. But no, the rest of this article is just rambling about how 'you don't really know about CMS'. I mean, if you know better than us do, then why can't the experience of using Headless CMS be better? You are here to solve the problem, right?
In the AI era, the rec file seems to be a great choice for formatting text that will be feed into LLMs. Imagine converting an HTML table into a RAG file, the context will be much clearer.
I also feel that I could give Durable Stream's protocol spec to a coding agent, and it could blend into the best suited implementation for my current project (say, a Go repo). The simple yet sophisticated spec is more valuable than a bunch of SDKs.
Currently Claude Code is the best, but I don't think Anthropic would pivot it into what I described. Maybe we still need to wait for the next groundbreaking open-source coding agent to come out.