Patrick A. Lima

Today the @deno_land team joins @Cloudflare, congrats to the team, by the way! I've used Deno since its earliest versions, I have open issues in the repo, and I really loved #deno #deploy. But when it comes to building and maintaining a company, an entire team, paying salaries and so on, you need to be realistic and look at the situation the way it really is. I don't believe @Cloudflare bought @denoland to kill Deno. The numbers simply must not add up to keep the platform running. And that brings us to a reflection on the #opensource world: companies using this software without the money/profit made from it ever flowing back to the project. In March 2021, @deno_land raised a $4.9M Seed Funding round to revolutionize secure JavaScript & TypeScript runtimes. Five years later, here we are. They launched a lot of things: #deno #deploy, @jsr_io and Claw Patrol. Many open source projects, very little revenue potential. When Deno Deploy hit v1 on June 23, 2021, it was born as the first serverless platform to run Deno, similar to @Cloudflare's #workers. Then came v2, on February 3, 2026 (I took part in the beta, helped test and report bugs), and the platform changed drastically: only 2 regions, versus 32 in v1, which had been gradually reduced over time due to operational costs. What used to run only Deno and a few frameworks became a platform for deploying pretty much anything that runs on #nodejs. The platform got good, but the regions dropped dramatically and bugs started to show up. They moved from @GoogleCloud to @Vultr , and that's when problems started piling up, until the @discord channel about Deno Deploy simply died and people stopped replying. Then came silence, ever since version 2.9, released in June 2026. Deno has always offered a very generous free tier, and @jsr_io is completely free too. But all of this consumes a lot of resources, #storage #bandwidth #cdn #memory, and a bunch of other things that at the end of the month add up to a massive bill to offer something for free to other people. Sometimes that's a detail people using it never stop to think about. They also launched Deno Deploy Subhosting, a white label platform to run scripts and deploys for companies' customers, extending products and offering more features like #edge #functions. Some of their customers? @Netlify, @SlackHQ and @deco_cms. Other companies like @supabase and @BunnyCDN also use #deno to offer their serverless services, like Edge Functions. And one question remains: of all of them, many making serious money, did any of it ever flow back as a donation? Or even to support the enterprise plan and ensure the project's longevity? Maybe I'm being overly dramatic. Maybe the @deno_land team simply lost interest in continuing to work on Deno, which is a real shame. This reflection may not hold true for big projects: many, like @vuejs , have large donation funds, and @Cloudflare itself is in that picture too, the same company the #deno team is now joining. But that's not what happens with small and medium open source projects: tons of companies and services using them in production, making great revenue, while almost none of it comes back to the project in exchange for the usage. It's a reflection that's been made before, and one that in my opinion needs to be made again, not only about donations and sustainability, but also about the quality and continuity guarantees of these projects. After all, how many are abandoned due to lack of time or resources? I'll wrap up what I wanted to say here. And I'll also wrap up by saying that I now have several scripts, @gitlab #CI/#CD files and automations written using Deno to update and use #node. @deno joins my list of amazing projects that sadly died along the way: #firefoxOS, @ubuntuphoneUS @lagonapp, #WindowsPhone, @ubuntu #Unity, among a few others. PS: I'll keep and cherish my @deno_land mug. 🧡

Day 27. Sometimes we face complicated problems. When we're developing mobile apps with hybrid solutions like @capacitorjs, we will always have some limitations compared to native apps. I'm building an auto-rich memory system called "Engrams" for @TecsuAI, our #private and #encrypted #aiAssistant. Engrams are markdown files, edited only by the LLM. To make this easier, you can select text on screen and choose options like "Edit" or "Delete". The problem?Capacitor doesn't have a feature for this. After some testing and research, we now have a custom native text-selection menu.The menu is injected into iOS's WKWebView selection flow and contains custom actions such as Copy, Edit, Delete, Share, and Select All. The labels don't need to be hardcoded in Swift. JS can send localized labels to the Capacitor plugin. #buildInPublic #swift #ios #capacitorjs

Day 10. It's 11:27 PM here in Brazil, and a lot has happened in the past few hours, time to share more news about @TecsuAI, the AI chat app I'm building for the @RevenueCat #Shipaton. I'm using @DevinAI , of course, to help me develop this app at lightning speed. A lot is still missing, and today is already the 19th! But things are moving. I must confess I spent several hours customizing an Ionic theme based on #MD3, the current one is still #MD2, and in 2026 that's just unacceptable. The app ends up looking ugly compared to other apps... Even though I'm a developer, I'm also a designer, and these things really bother me. Despite that, I've probably spent more time than I should making some cool animations and a few Easter eggs for you to discover xD. As bad as that sounds, @devindesktop on my laptop and in the Cloud (image in the post) are helping me prepare the #iOS build and handle the SQLite database.Meanwhile, on my MacBook next to me, I'm fixing some bugs in the CMS and in my chat message renderer to get good performance, more details soon. I should be updating here more often, but it's been hard to keep up the pace with work, the #Shipaton, and everything else. But let's go! #privacy #buildInPublic #encryption #AI #personalAssistant #Shipaton