Getting Ready for SolidJS

What is SolidJS

I had a carte-blanche API project recently, where I could choose the whole stack. I went or something crazy, Go+Postgresql+SolidJS. I had put Go in production but not with Postgresql, and for the frontend, SolidJS had just been nominated as a better ReactJS and it reminds me of the old SVN is a better CSV battle. (Which was not.)

I chose Go because of the speed of the development and the bare-mimimumness of the solution. I chose Postgresql because there were going to be millions of rows where I had to do pseudo-instant maths. I chose SolidJS because .. first because I wanted to find an alternative to ReactJS, which does the job, but not in a convenient way. (Memories of React Store pains anyone)


Fine-grained reactivity. Since SolidStart is a SolidJS meta-framework, it benefits from the fine-grained reactivity offered by SolidJS. Isomorphic, nested routing. You write the same routes regardless of whether the page is rendered on the client or server. Route nesting provides parent-child relationships that simplify application logic. Multiple rendering modes. SolidStart can be used to create CSR, SSR, streaming SSR, or SSG applications. Command Line Interface (CLI) and templates. Get up and running quickly with starters. Deployment adapters. SolidStart provides adapters to support deployment to your favorite platform—Netlify, Vercel, AWS, and Cloudflare, to name a few.