gluecodes-framework VS react-solid-state

Thanks. Well, it is interesting from technical point of view not so much as a SAAS product to be totally honest. We tried to tackle too many aspects of frontend dev and made a product which is terribly hard to sell haha. Don't get me wrong, it's based on many cool concepts I still use on my current projects but it's over-featured. I guess, I went through a typical anti-lean startup journey (lessons taken). Anyway, it's still online: https://www.glue.codes and it's freemium. The only reason it's not open source is that I can't find the time to document it, but I guess I could just open the repo to public... Who knows, maybe someone finds it useful.

I'm actually working on a rather large Solid project right now and will post it in our community when it's live. There are a lot of really neat things built on Solid, checkout Lume (https://github.com/lume/lume) which uses Solid for it's elements and even an IDE https://www.glue.codes/.

The below snippets are meant to work with GlueCodes Studio - the tool powering your every-day work in the ways you haven't seen elsewhere. It's for somebody who'd be pleased with loads of automation to deliver an extremely fast and scalable code i.e. build-time diffed JSX using SolidJS organised around an implicit uni-directional data flow. Obviously you can use it for FREE, so let's begin!

Promo video: https://youtu.be/_COe_s6oowY Website: https://www.glue.codes Product: https://ide.glue.codes

Static HTML has no built-in way to make it reactive. Hence GlueCodes Studio has a concept called extended tags which is named like: tagName + '-x' and has an embedded gc-as="listFieldPresenter" gc-provider="getCategories" gc-field="name" class="label">category name class="heading">Neighborhood class="filterSet"> gc-as="listItemPresenter" gc-provider="getNeighborhoods" class="filterItem"> type="radio"> gc-as="listFieldPresenter" gc-provider="getNeighborhoods" gc-field="name" class="label">neighborhood name class="heading">Language class="filterSet"> gc-as="listItemPresenter" gc-provider="getLanguages" class="filterItem"> type="radio"> gc-as="listFieldPresenter" gc-provider="getLanguages" gc-field="name" class="label">language name

On one hand I agree with it, don't go with Solid and expect that you will 100% find a Solid job. On the other hand I think that unlike a lot of other frameworks, learning Solid could be useful even if you don't end up using it. You could even end up using Solid as a really good state management library for React https://github.com/solidjs/react-solid-state (at it's core Solid is just a state management library)

[2]: https://github.com/solidjs/react-solid-state

There's https://github.com/solidjs/react-solid-state for enabling Solid reactivity in React components. My plan is wire up a lot of my state management with Solid and that and then just continue using whatever React dependencies we're reliant on. If one of the Solid headless ui component libraries got mature enough, we could probably port completely then.