points by rumblefrog 2 weeks ago

Looks interesting, what's their revenue model? Or how do we know it won't be abandoned in the near future?

shimman 2 weeks ago

The same as any other dev tool startup, once money gets tight they will monetize and users will rightfully revolt.

Evan You won't break the cycle, tale as old as time.

  • manniL 2 weeks ago

    VoidZero's business model is in Void, their deployment platform. Open source projects will always stay open source. This was announced at the very beginning.

    • shimman 2 weeks ago

      Yes, nothing different from any other VC dev tool startup. When the community fractures people simply move on to something else. See rome -> biome for a very recent example.

  • lioeters 2 weeks ago

    After getting burned so many times on libraries, frameworks, services and platforms, even entire languages - one learns to be wary of critical dependencies. Every new project offers convenience in exchange for you giving up control of part of the software stack, and the power dynamic is often exploited sooner or later as revenue source. You can't trust anything that becomes irreplaceable, or that you can't write it (or at least understand it) yourself.

    • chrisweekly 2 weeks ago

      I mostly agree. But without argument, I can point out that a modern webapp requires tooling for capabilities like testing, linting, formatting, and bundling. Vite (and its ecosystem) has proven its mettle, and when it comes to being able to understand your dependencies, I'll take fewer, and simpler, and way faster, and more coherent, and more independent of misaligned corporate influence, every time. It's not even a trade-off, it's just better. I have deep expertise in wrangling eslint plugins and prettier configs and webpack, and am so grateful that's all in the rear-view mirror. An astonishing percentage of the world's most popular websites are built on a fragile and nearly-incomprehensible stack which no sane developer would choose. VoidZero (and TanStack, FWIW) are a breath of fresh air in making it possible to reason about your frontend tooling and architecture, and stepping away from unnecessary complexity and/or vendor lock-in. Of course it will eventually change. But as someone who's been building and improving web-based experiences for a living since the late 90's (for tiny startups and F500 enterprises and everything between), this is as good as it's ever been, and I recommend it without reservation.