Really interesting article and perspective for devs in the OSS world looking for greater financial stability. I’m curious, how do you strike a balance between dual licensing and building trust and adoption early on?

I built this project about 10 years ago just to learn JavaScript. For a long time, it was a completely free, and I lost interest in it after a while.

Later, when I quit my full time job to build my own startup, I needed something for survival. The first project I picked up again was lightGallery. It was already quite popular back then, so I decided to rewrite it from scratch and implement dual licensing.

So, basically the trust and adoption were built over years when it was free. The monetization came much later.

Okay, it’s a bit of a stretch, but this guy’s code is probably included in almost every web component, and I wanted to shine some light on him and give him credit.

The report seems somewhat biased due to the massive Mistral AI round, but it still contains plenty of interesting insights and counterintuitive takes.

Really cool article, we might give it a try at our company. Any recommendations regarding common pitfalls when working with Bitmapist?

Thank you! Starting with the Redis server is a solid choice. However, if you're aiming to support a large user base or handle many events (like billions), I highly recommend considering the setup of bitmapist-server, our Go server. You can find it here: https://github.com/Doist/bitmapist-server — it will do a 400x+ reduction in memory used.

Really interesting take. I'd love to see what you're exploring.

I'm building a new kind of product: a DOM-first IDE that will define a whole new generation of UX-expanding tools for coding. Check out https://github.com/bablr-lang.

We're preparing a major release announcement.

If anyone knows anyone at Mozilla who might be interested in a thing like this, I'd still be eager to talk to them.

This is why I’ve always felt that the "engineer" part of "software engineer" is the most important, and I’ve never liked the term "developer."

Thanks for sharing your impressive journey. It's always refreshing to see a story that promotes grit and resilience, rather than the instant exponential growth often glorified by wannabe millionaires online.

Glad to hear it resonated. And also glad I didn't start this project with the expectation of quick success, hype, or exponential growth. If I had, there's no way I would have made it through the slower early years.