gluecodes-framework VS Svelte

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

Svelte and specifically, SvelteKit is an open source web framework that makes developing web applications easier.

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

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…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.