We provide both bun and deno as typescript runtimes for windmill.dev (oss retool alternative) and we get overwhelming feedback that people are confused by the little changes required to adapt to deno and would rather just stick to the node.js mode aka bun. Now that bun is getting close to 1:1 node.js support, I predict we will see a lot more bun everywhere.
@Jarred was super responsive to help me adapt bun to our distributed cache storage, so all props to him.
While it is sad, I can't help but agree. I've spent many, many years working with Node and tried picking up Deno recently. The small cuts quickly add up where getting even some of the official examples to work takes effort because they're ever so slightly out of date and things have changed in the interim.
I remember when the project started. I believe that the ability to learn the language as quickly as he did, get the feedback required and iterating quickly helped a lot! All of this was possible with Zig. People are amazing and great inspiration, it's not sad at all.
Is that still the case tho? Recent Deno releases have obscured how well it's Node compatibility mode is, I was just wondering if you have more details.
Thanks for building Windmill. I spin up a test instance and was blown away by the well-designed-ness.
I'm looking to investigate using Windmill as a website builder for some small internal system. Few questions:
- Is it possible to setup custom path for flows (to hack it into a REST API)
- How can we go and make authenticated flow
@Jarred was super responsive to help me adapt bun to our distributed cache storage, so all props to him.