yazz VS Svelte

Shameless plug. My own one of course :)

https://github.com/yazz/yazz

You can also try one I am building, a cross between Visual Basic and Microsoft Access here:

https://yazz.com/

i am working on such a thing myself at https://github.com/yazz/yazz. Also there are many other people trying to build something similar

I keep hacking away on Yazz for over 10 years now.... even if there is zero payoff I keep hacking... and that is what hackers do... we are not doing for the money... https://github.com/yazz/yazz

I really loved this talk and feel for Evan. As someone who was a VC/Angel investor in the space (I was the initial angel investor for something called LightTable/Eve) back in the day, worked for a couple of years at Red Hat, and am working on my own Open Source Language here: https://github.com/yazz/yazz (so yes, you could say I am a VC trying to build a low code product with my own hands), so I feel I have a valid opinions on this. I think that it is possible to make money in opensource as a little guy, but you need to have a combination of consulting, hosting, and support services. If your product is not able to encapsulate being sold and packaged as something that is possible to demo and sell to customers then you will most likely struggle to make a living from it

I am actually trying to make an open source successor, but using Javascript instead of Basic, at https://github.com/yazz/yazz and a demo at yazz.com

I'm still building a low code system with an easy to use component marketplace where you can edit components within the low code tool. Still a work in progress: https://github.com/yazz/yazz

Author of a framework that also stores it's code in IPFS for easy sharing (https://github.com/yazz/yazz). ScrapScript is a really nice concept with how it stores code. I originally got the idea for storing the code as a hash of the contents from Unison, and it looks like the idea is really starting to catch on with more and more languages now. Well done!

I’m working on a low core project that is already using content addressable source code that is stored in IPFS at https://github.com/yazz/yazz so it can be done

There are already some Dbos type systems out there. I built one which stores program state in SQLite databases and process state and programs are also stored in SQLite. In the oat I believe things like silver stream did the same too. The project I made is open source too: https://github.com/yazz/yazz

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.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.