beautiful tech stack writeup, one of the best i've ever seen in my career. I always advocate that devtools companies write these up, because…

beautiful tech stack writeup, one of the best i've ever seen in my career. I always advocate that devtools companies write these up, because it fulfils multiple purposes: - tell users the care that goes into the product - tell hires that there's SOTA work here - tell competitors to give up - gives back to community - (nuanced) tell non-fits why they can't have what they want when they think it's an easy request few actually do this mostly because they don't actually have sufficient depth, or aren't sufficiently good at notetaking/systematic about problemsolving ('its just vibes' or 'honestly we just went with the first thing that worked' doesn't come across as well, so rather not say anything) so when you've done the work, show the work. bravo Raycast One app, two platforms, four programming languages. The things that look the simplest are often the hardest to build. @raycast is one of them. Here's a technical deep dive on how we built v2 👉 http://ray.so/v2-deep-dive

Source: Swyx (X) | 2026-05-14