open-saas VS solid-docs

For the even faster start, it also features Open SaaS - a 100% free and open-source boilerplate starter for React & Node.js. Just clone it and get a working app with auth, billing, Open AI API, user dashboard and more!

When building AI Blog Articles, I decided to get started as fast as possible. So I looked for a free boilerplate and stumbled upon Open SaaS, which used YC-backed Wasp. It is a full-stack React + NodeJS + Prisma that takes 8 hours to get started with.

In addition, their CLI can help you start faster too. By running wasp new, you can get yourself a custom template that fits your needs. For example, if you’re building up a new SaaS, you’ll probably find a fit with OpenSaaS or if you’re creating a more specific solution, an AI code generator can help you start quickly if nothing else fits.

9,500 stars and almost 3 years later, here we are today. Wasp is getting close to entering the elite 10,000 stars club on GitHub, next to the giants of the industry. The framework we started, and developed further with the invaluable feedback from the community, is being used by all kinds of developers - from weekend projects, to startups and top enterprises. Startups made with Wasp have been acquired. I just saw a job ad today on Upwork, where a company is hiring for Open SaaS (an open-source, free boilerplate starter for React & Node.js, powered by Wasp) developers 🤯.

These days, I'm building side projects, like Open SaaS pictured above, and working as a developer relations engineer.

Although some people could consider Wasp’s opinionated stance a negative thing, it is the driver behind Wasp’s numerous full-stack features. With Wasp, starting a full-stack project for a single developer or a small team is much easier, especially if you use one of the pre-made templates or OpenSaaS as your SaaS starter. Because the core of the project is well-defined, it is very easy to get started with a project and potentially, make your own full-stack SaaS in a couple of days! What’s also cool is the fact that most of the pre-existing knowledge of web developers for most of them still applies here, because the technologies that Wasp uses are established.

OpenSaaS – I was curious what the latest starter kit for building out SaaS apps looks like. I wrote my own a whole decade ago github.com/eddywashere/node-stripe-membership-saas.

We’ve launched 6 times on Product Hunt in the last 3 years, won “Top Product” awards (#1 and #5 of the day), and collected over 2,000 upvotes in total. We just finished our sixth launch with Open SaaS - an open-source alternative to $300+ SaaS starters, a week ago.

Hey,

a few people have asked me how we got our [open-source SaaS starter](https://github.com/wasp-lang/open-saas) to the front page of GitHub trending, so I thought I'd share the details:

1. started sharing a funny promo [video on twitter](https://x.com/hot_town/status/1752243248439910626?s=20) and reddit

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Solid.js is a very performant web framework that shares some similarities with React. For example, both use JSX, utilizing the function-based approach to components, but instead of using Virtual DOM, it converts your code to vanilla JS. Still, it is more famous for its approach to fine-grained reactivity by utilizing signals, memos, and effects. Still, the signal is the simplest and most known primitive of Solid. They contain value along with their getter and setter functions, allowing the framework to observe and update the changes as needed in the exact location in the DOM, unlike React, which re-renders the whole component.

Two well-known JavaScript frameworks and libraries used for creating user interfaces are React.js and Solid.js. Solid.js, a lightweight reactive library, prioritizes fine-grained reactivity and efficient rendering through a reactive programming model. However, React.js, which was developed by Facebook, is well known for its declarative architecture based on components and its handling of the virtual DOM (Document Object Model). Different approaches to state management and reactivity set these tools apart, even though they both enable developers to create dynamic and interactive web apps.

Solid.js like Svelte is quite new when compared to React, Angular, and Vue however it might be that pocket Hercules we've all been ignoring because we are so addicted to other frameworks. Solid.js is an interesting framework that deserves to be a part of this discussion. Solid.js pioneered the concept of signals when other Javascript frameworks made reactivity and state management a nightmare for developers, a factor that has contributed to the growth of Solid. Solid.js is incredibly easy to adopt and it aims for a simpler syntax and learning curve compared to other frameworks. It emphasizes the use of pure Javascript functions and avoids concepts like hooks.

React Server Components are the poster child for that trend, but other frameworks such as Solid or Qwik rethink client-server interactions from the ground up.

If you aren't married to the react paradigm, I had a great time with solid.

Frontend : SolidJs.