Merlijn Vos

I remember playing this on a laptop and the keybindings were awful, making it particularly hard 😅

@CloudflareDev @astrodotbuild @bytesdotdev there goes your multi-year Netlify prediction

Astro + Cloudflare The @astrodotbuild team is joining Cloudflare! Together we're doubling down on making Astro the best framework to build content-driven websites. Read more on the blog: blog.cloudflare.com/astro-joins-cl…

POV: you ask Claude Code for only one big task 🥲

Coming from @Neovim it has always bugged me that panes and layouts are flying everywhere, often inconsistently, while I was used to have full-focus no clutter windows. This seems like a step in the right direction

For anyone thinking to put this (more or less) directly into AGENTS.md or CLAUDE.md, a reminder that you should not overload on context 👉 humanlayer.dev/blog/writing-a…

@jorgemanru @yurilimak9 Wanted to save it to my watch later but because it’s published as a video for children I can’t save it due to regulation 😅

@yurilimak9 It is there too! youtu.be/dvPXFnX60cg?fe…

As promised: a video talking about how we architect Rails apps and Fizzy. Includes thoughts on Domain Driven Design, service objects, callbacks, and concerns. I will record more of these, but probably not as long!

@jorgemanru Definitely curious for your quickest and/or unobvious wins on improving UX with hotwire/stimulus for common interactions

I’m going to record a video walking through some Fizzy code to discuss design and architecture in Rails apps. I’ve written about similar topics here: dev.37signals.com/series/code-i-…. Now that the Fizzy source is available, I think screencasts could be a great way to share approaches and techniques. If there are specific things you’d like me to cover let me know!

dunno if it's because I've been using too much Tailwind or I'm getting old but my mind can't produce this kind of CSS. Like, you like at the page and you think 'right, this calls for the 'ol :is + clamp + cqi unit'

@jasonfried Have you seen fair source? It’s a similar setup for companies publishing their source code but with some protections fair.io

People have been asking what happens to ONCE now that Fizzy is both SaaS and Open Source? Are we going to make any more ONCE products? First some quick background. In September of 2023 we announced ONCE. ONCE was the reintroduction of an old idea. Rather than subscribe to software in perpetuity, you could just pay for it once and own it rather than rent it. It came with all the code too, so you could run it yourself and modify it for your own use. We launched two products under the ONCE umbrella. Campfire, a group chat tool. And Writebook, an online book publishing tool. Campfire was $399 (once), and Writebook was completely free (forever). Just recently we made Campfire free, too. Today both are available as open source under the MIT license. (Repo links) So now that both products are free and open source, what does that mean for ONCE itself? While we didn’t know it at the time, we’ve since discovered that ONCE was more a direction than a destination. And now that we know where we’re headed, we’ve decided to wind down the ONCE model, and wind up something better: A new model combining the best of SaaS and Open Source. You can pay us to host and support the software for you, or you can run and modify it yourself for free. Companies like Wordpress, Ghost, Plausible, and Gitlab offer software under this model already. We’re proud to join these pioneers. We think this is the right way forward. Fizzy is the first product we’ll be releasing under this model at 37signals. Practically, this means Fizzy will be available two ways right from the get go: 1. Traditional SaaS. Sold by us, hosted by us, supported by us. Free option + paid plan. 2. Open Source. Entirely free, hosted by you. Change it to fit you better, fork it, or, even better, collaborate with us, submit PRs, and improve it for everyone. A 1-2 punch, the best of both worlds. As a company, we’ve been building SaaS software for more than two decades. Basecamp, Backpack, Highrise, Campfire, HEY, and others. We were among the early pioneers in SaaS, so we know it intimately. We’ve also been making open source software for more than two decades. From Rails to Hotwire to Kamal to Trix to Omarchy to a couple hundred other repos, we’re soaked in open source. We’re built on it. But we’ve never married the two. We’ve never offered a commercial SaaS product as open source as well. Fizzy, a fresh take on kanban, is our first. We’ve put an enormous about of effort getting Fizzy 1.0 right while purposefully leaving it wide open to all sorts of potential features, futures, and integrations. So we’re inviting the community to help us build Fizzy into an absolute powerhouse of a platform. And with that, we invite you to check out Fizzy at Fizzy.do. It’s a new era. Let’s go!

One thing I cannot stand when using Cursor/VS Code is having lots of panes open at the same time. I basically want to only do one thing at a time, whether that's code, agent view, file tree, or the terminal. To make the terminal always use full screen, you can override the default cmd+j of Cursor:

.@neogoose_btw the search results of fff.nvim are so much better than telescope and others I can't believe I ever settled for how it worked before

.@Cloudflare stepping up the war against @vercel with their new landing page

@jasonfried Is Fizzy meant to be used completely separate from Basecamp? Or is there some overlap/sync?

As we work on Basecamp 5 (and use it internally while we build it), we're tracking issues & ideas in Fizzy. I'm biased here, but it's so nice to use software with some life, texture, and color! Such a contrast to the sterility that's snuck into most biz software today.

🎉 Uppy 5.0 is here! After a year of development, our file upload library now features headless components and hooks - the most requested feature of all time. Build truly customizable upload experiences with React, Vue, and Svelte support. uppy.io/blog/uppy-5.0/

While I initially ran into the problem, the deep dive was performed by @remcohaszing, who also already made a PR for Next.js, an issue to Preact, and clarifications to TS docs 💯 github.com/preactjs/preac… github.com/vercel/next.js…

First of all Uppy is removing preact/compat from its usage, as it can easily just rely on preact, to immediately resolve problems Next.js should change from "preserve" to "react-jsx", as it actually compiles to automatic preact/compat should not declare the React UMD namespace

A new release of @uppy_io uncovered a rabbit hole of JSX type issues in the ecosystem between @preactjs, @nextjs, and @typescript A refresher on the TS "jsx" option, what Next.js and Preact are doing wrong, and what's next 👇