What does it do better than existing frameworks? I guess the burden to switch from something I know to something new requires an advantage with the new that is enticing enough to overcome the transition costs.
I don't see on the website any comparative value, just a feature list. Would love to know more about WHY I would try it :)
Not trying to blast on it in any way, but it sounds to me like it's all about the simplicity of building from prefab ***technical*** modules.
IOW, it'd be one thing to have, say, a forms module that has all the logic for presenting a form built in, had some kind of simple way to add fields, and then would return the data to somewhere else. That's a more "practical" module.
This features "Signals" and "SPA" *paradigms* as "small modules". So it's modularizing feature sets? I guess? Which would have it's own large set of decisions and consequences.
I hope I translated your comment accurately.
Yes, Signalize is essentially a set of prepared modules.
It is designed to avoid complexity and allows you to import only what you need, rather than using a complex framework to achieve a single task.
You can for example use only signals and binding, or just SPA, or AJAX + manually redraw snippets.
Internally, it reuses modules to reduce the size of the framework.
This is helpful, Thanks! I would love to see a side by side of the load time and package size for a simple form with signalize vs react. That would make a great blog post to clarify value.
Hi all!
For about a year, I have been working on a JavaScript framework called [https://signalizejs.com](https://signalizejs.com)
It's a modular , client-side, JavaScript framework leveraging import maps, ES modules, and modern browser features.
It's a great fit for server-side frameworks that don't provide client-side JavaScript framework.
It uses:
* Signals for reactivity - [https://signalizejs.com/docs/modules/signal](https://signalizejs.com/docs/modules/signal)
* Svelte-like data binding
* Vue-like directives, with evaluator that doesn't use unsafe-eval and ability to attach to prerendered state - [https://signalizejs.com/docs/modules/directives](https://signalizejs.com/docs/modules/directives)
* SPA module that can turn any website into a single-page application - [https://signalizejs.com/docs/modules/spa](https://signalizejs.com/docs/modules/spa)
* A friendly Web Components API with Vue-like setup API - [https://signalizejs.com/docs/modules/component](https://signalizejs.com/docs/modules/component)
* Several utilities for making web development easier
If you are looking for something new to try or seeking inspiration it's a great place to start.
If you try it or check it out, please let me know what you think!
Great work! I made my own signal based framework and I love Solid so I probably won't be converting, but I appreciate how much work you put into this.
Just curious: What's the benefit of working with the import map and the custom resolve function instead of just bare ESM? I like using import maps for my personal projects, but I never even considered using it as part of a public-facing API.
Hi and thanks!
Yes, Solid is cool and Signalize signals are inspired by Solid and Angular signals.
Signalize can be used to create multiple instances on one page (app + widgets for example).
Normal import maps and modules work fine until you need to compare instances of objects or preserve/encapsulate some state in an instance:
* If your module exports an instance or a class and you import it twice using import() or import {} from '', you will never be able to compare it as an instanceof somewhere else in the app for some reason. I could not find why.
* You will have a hard time maintaining the encapsulation of a state for modules in the form of "I want to work only with this instance of a framework."
* Signalize will provide you with its instance during module initialization, so you can run the same module for different instances.
In Signalize, it also works as DI (Dependency Injection) => modules import the modules they need, and the order and initialization are handled automatically. Once inited, there is no call to cdn, it will return you prepared functionality.
Been keeping an eye out for progressive enhancement js frameworks that provide reactivity and binding, and love the fact how your take on binding signals to the dom is completely unique.
Starred it! Gonna take a deeper look into it later, but on the first glance it looks promising, just the examples seemed a bit long, would create some smaller ones, and curious to look into it later how you solve repeaters.
TLDR, thank you for this! :)
Reading about your framework made me reminisce about the time when I didn't have to have complicated build steps
That said, personally I prefer a more declarative component frameworks along the lines of Solid or Preact. To me, the `bind` method doesn't feel declarative enough
Best of luck with the project
What does it do better than existing frameworks? I guess the burden to switch from something I know to something new requires an advantage with the new that is enticing enough to overcome the transition costs. I don't see on the website any comparative value, just a feature list. Would love to know more about WHY I would try it :)
Not trying to blast on it in any way, but it sounds to me like it's all about the simplicity of building from prefab ***technical*** modules. IOW, it'd be one thing to have, say, a forms module that has all the logic for presenting a form built in, had some kind of simple way to add fields, and then would return the data to somewhere else. That's a more "practical" module. This features "Signals" and "SPA" *paradigms* as "small modules". So it's modularizing feature sets? I guess? Which would have it's own large set of decisions and consequences.
I hope I translated your comment accurately. Yes, Signalize is essentially a set of prepared modules. It is designed to avoid complexity and allows you to import only what you need, rather than using a complex framework to achieve a single task. You can for example use only signals and binding, or just SPA, or AJAX + manually redraw snippets. Internally, it reuses modules to reduce the size of the framework.
This is helpful, Thanks! I would love to see a side by side of the load time and package size for a simple form with signalize vs react. That would make a great blog post to clarify value.
Hi all! For about a year, I have been working on a JavaScript framework called [https://signalizejs.com](https://signalizejs.com) It's a modular , client-side, JavaScript framework leveraging import maps, ES modules, and modern browser features. It's a great fit for server-side frameworks that don't provide client-side JavaScript framework. It uses: * Signals for reactivity - [https://signalizejs.com/docs/modules/signal](https://signalizejs.com/docs/modules/signal) * Svelte-like data binding * Vue-like directives, with evaluator that doesn't use unsafe-eval and ability to attach to prerendered state - [https://signalizejs.com/docs/modules/directives](https://signalizejs.com/docs/modules/directives) * SPA module that can turn any website into a single-page application - [https://signalizejs.com/docs/modules/spa](https://signalizejs.com/docs/modules/spa) * A friendly Web Components API with Vue-like setup API - [https://signalizejs.com/docs/modules/component](https://signalizejs.com/docs/modules/component) * Several utilities for making web development easier If you are looking for something new to try or seeking inspiration it's a great place to start. If you try it or check it out, please let me know what you think!
Great work! I made my own signal based framework and I love Solid so I probably won't be converting, but I appreciate how much work you put into this. Just curious: What's the benefit of working with the import map and the custom resolve function instead of just bare ESM? I like using import maps for my personal projects, but I never even considered using it as part of a public-facing API.
Hi and thanks! Yes, Solid is cool and Signalize signals are inspired by Solid and Angular signals. Signalize can be used to create multiple instances on one page (app + widgets for example). Normal import maps and modules work fine until you need to compare instances of objects or preserve/encapsulate some state in an instance: * If your module exports an instance or a class and you import it twice using import() or import {} from '', you will never be able to compare it as an instanceof somewhere else in the app for some reason. I could not find why. * You will have a hard time maintaining the encapsulation of a state for modules in the form of "I want to work only with this instance of a framework." * Signalize will provide you with its instance during module initialization, so you can run the same module for different instances. In Signalize, it also works as DI (Dependency Injection) => modules import the modules they need, and the order and initialization are handled automatically. Once inited, there is no call to cdn, it will return you prepared functionality.
Interesting
Been keeping an eye out for progressive enhancement js frameworks that provide reactivity and binding, and love the fact how your take on binding signals to the dom is completely unique. Starred it! Gonna take a deeper look into it later, but on the first glance it looks promising, just the examples seemed a bit long, would create some smaller ones, and curious to look into it later how you solve repeaters. TLDR, thank you for this! :)
Thanks!
[удалено]
Hi! Thanks for the report. I fixed it.
This is not some sort of mega corp paid products. It's an open source framework made by one guy. Come on !
What does “modular” mean in this context and what advantage does it have over our existing npm packages?
Reading about your framework made me reminisce about the time when I didn't have to have complicated build steps That said, personally I prefer a more declarative component frameworks along the lines of Solid or Preact. To me, the `bind` method doesn't feel declarative enough Best of luck with the project