I love deno so much and all of its ideas highlighted in the article (dependency management, security, performance) so much that I've build an entire framework around making scripting enterprise grade that is centered around deno support. The project is open-source [1], we even expose a web monaco editor and made the lsp support available using websocket and json-rpc. The goal here is to build enterprise-grade one-off script and workflows in deno, that can benefit from permissioned credentials, autogenerated UI (by parsing the main function parameters), a workflow engine similar to airflow/temporal, etc ...

We have a hub [2], centered around deno, that serves as our library of integration. An integration for us, is just a script that uses the right dependency to do an atomic action like fetching data or doing a POST.

We are betting big on deno, and are hoping with windmill to be the framework to make it enterprise-ready for other things than webservers (which most of the deno framework currently focus on).

[1]: https://github.com/windmill-labs/windmill [2]: https://hub.windmill.dev

I have quite a very same feeling. But as a way to review things, I also write flashcards when I think there's something useful I'd like to remember, or when I'm studying. Once you start remembering a flashcard, it will appear less and less often.

It's quite simple in Obsidian with the extension "Spaced Repetition":

What is foo? ? foo is bar

I’m tempted to go FastAPI over Django on my next project, even though I’ve been a big Django user. A little more performance and a little less coupling, and maybe you can survive longer as a Python monolith. Then convert to Rust/Go/something in the unlikely event of wild success.

It’s great what they did, very impressive and excellent product.

However, the article is a bit misleading, mainly for two reasons: “bootstrapped”, and “without spending a dime on marketing”.

They “bootstrapped” by financing the company with another profitable company. That technically means they were their own investors, but they weren’t limited only to the revenue that their email company was generating.

They didn’t spend “a dime on marketing”, but they did spend time promoting their product on several platforms, including producthunt, and they do have a blog (which is where the article is hosted), and they do have one full-time employee (out of four), in charge of marketing. So maybe what they truly meant is that they didn’t pay for advertising, but that’s different than not spending money on marketing, which they did, and in fact you could even say that it’s probably a significant part of their budget (given one of the only four team members is dedicated to marketing).