Introducing Claude Sonnet 5, our most agentic Sonnet yet.
It makes plans, uses tools like browsers and terminals, and runs autonomously at a level that just a few months ago required larger and more expensive models.
@thomasglopes The technology by itself is nice and can sparsely have interesting purposes
The main problems are the industrialization of it, the aggressive marketing, fear mongering, overhype and under delivering, … this I would love to freaking get rid of forever
Opinions along this line show a clear disconnect between those who use React only vs. those who don’t use React at all.
It’s easy to assume what makes sense for you makes sense for everyone because who cares about those who don’t use the same framework as mine?
But - Vite is framework agnostic, vendor agnostic, and we can’t go down that slippery slope. What if tomorrow we are going to add another 5mb for a Rust Vue compiler, and next week another for Svelte, Solid, and Astro? One can argue React is the most popular so it deserves special treatment, but where should that line be drawn? Why NOT other frameworks?
Vite is downloaded 12 millions a week, every uncached download consumes bandwidth and CI time. 5mb might not mean much for an individual end user, but it can result in meaningful difference at scale. If there is a way to optimize it, we should try that. It’s ironic that people complain about node_modules size while at the same time dismissing size optimization efforts.
🚀 Vite 8.1 is out
⚡ Experimental Full Bundle Mode: ~15x faster dev server startup & ~10x faster full reloads on large apps
🧩 Chunk Import Map to keep chunks stable & improve caching
🦀 WASM ESM integration
💡 Lightning CSS on the road to default
👀 and more!
Blog post below.
@andrii_sherman@dstaley I think it’s time for a v9 with less subpaths (either merged or split into subpackages)
But most importantly, dropping CJS is more than overdue and would at least halve the file size
But yeah for maintenance v8, npm will still have to solve this
The fallacy of this is that more creates more. More hours, more hiring, more something.
And it is true in a sense. If you put in more work, more work will happen. But I think for most startups, the leverage is really in how differently you approach the problem, how well you cultivate your team, and the strategy.
Any large company can outspend you on hours. They have thousands or tens of thousands more people, spending more hours. If hours worked were the metric, every large company and government organization would always win and do the best work. More hours, better output.
This thinking is often representative of younger founders, where the startup becomes their identity and life. They have a hard time doing anything else, and cannot understand that your work is not the person that is you. But activities outside of work can grow you as a person too and make you do better work.
I’ve never worked this way. As a designer, I always saw the need to take a step back, to take a break. At times, I might work 12 hours or 16 hours, or whatever amount was needed, but it wasn’t the norm. You just can't grind design, you need inspiration. But taking that step away from the work, would give me more perspective, inspiration and I could approach the problem differently or I could just see the solution.
Grinding is never good for any creative problem, and startups or creating new products are often mostly about creative problem solving. Grinding works ok for email jobs, or where you just executing on very clear playbook.
With Linear, we’ve never worked this way. We work reasonable hours, 5 days a week. All of us founders have families. Many of our employees have families. I personally stop every evening, spend time with the family, cook dinner for the family, eat dinner together, and focus on things outside of work. Sometimes I work in the late evenings or weekends, but to me the pride is that I don’t need to. Company should be succesful without it.
My goal is to build a company that is sustainable in the long term, and doesn’t require heroics or personal sacrifices every single day.
There are times when our team is heroic. Launches, incidents, some other work that just needs to be done. They will work late into the night because they know it is the right thing. But we don’t require that every day or every week, and the more this happens, the more I think it is a failure of our company and leadership. The team and the leaders should always keep a reserve to use when something is needed.
Our thinking was also that quality, which we value, doesn’t emerge from working more or stressing people more. It emerges when you create the conditions for it to emerge. Often it is the appreciation, space, time, and how the person feels. A person who is rested will do better work.
I wouldn’t attribute much of our success to working a lot. The success came from having clear thinking, ideas, and focus to do the right things.
I sometimes wish we could move the culture more toward a Zen master.
Real mastery is not exerting the most effort. It is achieving the outcome with the least necessary effort.
Say goodbye to svelte.config.js - you don't need it anymore!
The newest version of SvelteKit allows you to configure everything via its Vite plugin, and VS Code, svelte-check and SvelteKit itself can all read from it.
On file less cluttering your project root.
@richard__dev@pilcrowonpaper Yeah, this kind of lib wraps knowledge more than code length or difficulty
This or a copy paste tutorial to avoid having to think about it!