I'm not React dev although my last job was in React, previous was in Angular.js, the one before that in backbone.js and the one before that in jQuery, and the one before that in IE5.5 raw JavaScript.
JSX is pretty established and focused (optional) language extension which I was initially cautious about as well. Svelte extensions feel for me a bit more adhoc and mandatory.
I'm judging and comparing because I'm interested in frameworks and templating engines. Building stuff to judge something is fine but I have no need to build anything at the moment so I prefer now reading the code of stuff that other people have built and consider if it's a pleasant read for me. Svelte isn't same way angular.js wasn't. AppRun is, possibly even more than React was (at least the React before hooks).
EDIT
Hyperapp looks similar but as far as I can tell it doesn't have event bus.
I worked with one large project (google maps competitor) in raw JS that used event bus and it was really amazing how much you could understand about it just hooking yourself to the bus and inspecting all events that go through there, knowing that nothing happens behind your back.
So that's a clear win for me in AppRun vs hyperapp.
Although AppRun seems to have one event bus per component so hooking up to all of them might require a bit of effort and tickery.
Another thing is stateful components. Hyperapp doesn't have clear way of making stateful components. People are just winging it in various ways.
Hyperapp looks similar but as far as I can tell it doesn't have event bus.
I worked with one large project (google maps competitor) in raw JS that used event bus and it was really amazing how much you could understand about it just hooking yourself to the bus and inspecting all events that go through there, knowing that nothing happens behind your back.
So that's a clear win for me in AppRun vs hyperapp.
Another thing is components. Hyperapp doesn't have clear way of making stateful components. People are just winging it in various ways.
I didn’t pose hyperapp as a better framework, just pointed out that there are not really any new concepts in AppRun, in fact the initial versions of React, Preact, and hyperapp, apprun , Mithril etc are all very similar in spirit. So it’s like pointing to Backbone as an “alternative” to a modern framework - not wrong, but it’s missing the point.
What I really wanted to say is that if you take more than 5 minutes to evaluate one of these, you might have a much better idea of it’s capabilities and maybe even learn something new.
It’s clear you’re excited about the subject and that’s great, but very little of what you said is true - for example, one of hyperapp’s main value propositions is the built-in centralized state management, so yes you’ll have to “wing” local state because that’s shoehorning a foreign concept into it. You are looking for something that fits your existing mental models, and not really judging their goals and strengths.
Comments
I just came here to share what I learned yesterday about AppRun and about Svelte recently. Today I might read about hyperapp.
JSX in AppRun is optional. You can use lithtml or just html. https://apprun.js.org/docs/#/06-view-patterns
I'm not React dev although my last job was in React, previous was in Angular.js, the one before that in backbone.js and the one before that in jQuery, and the one before that in IE5.5 raw JavaScript.
JSX is pretty established and focused (optional) language extension which I was initially cautious about as well. Svelte extensions feel for me a bit more adhoc and mandatory.
I'm judging and comparing because I'm interested in frameworks and templating engines. Building stuff to judge something is fine but I have no need to build anything at the moment so I prefer now reading the code of stuff that other people have built and consider if it's a pleasant read for me. Svelte isn't same way angular.js wasn't. AppRun is, possibly even more than React was (at least the React before hooks).
EDIT
Hyperapp looks similar but as far as I can tell it doesn't have event bus.
I worked with one large project (google maps competitor) in raw JS that used event bus and it was really amazing how much you could understand about it just hooking yourself to the bus and inspecting all events that go through there, knowing that nothing happens behind your back.
So that's a clear win for me in AppRun vs hyperapp.
Although AppRun seems to have one event bus per component so hooking up to all of them might require a bit of effort and tickery.
Another thing is stateful components. Hyperapp doesn't have clear way of making stateful components. People are just winging it in various ways.
EDIT
Hyperapp looks similar but as far as I can tell it doesn't have event bus.
I worked with one large project (google maps competitor) in raw JS that used event bus and it was really amazing how much you could understand about it just hooking yourself to the bus and inspecting all events that go through there, knowing that nothing happens behind your back.
So that's a clear win for me in AppRun vs hyperapp.
Another thing is components. Hyperapp doesn't have clear way of making stateful components. People are just winging it in various ways.
I didn’t pose hyperapp as a better framework, just pointed out that there are not really any new concepts in AppRun, in fact the initial versions of React, Preact, and hyperapp, apprun , Mithril etc are all very similar in spirit. So it’s like pointing to Backbone as an “alternative” to a modern framework - not wrong, but it’s missing the point.
What I really wanted to say is that if you take more than 5 minutes to evaluate one of these, you might have a much better idea of it’s capabilities and maybe even learn something new.
It’s clear you’re excited about the subject and that’s great, but very little of what you said is true - for example, one of hyperapp’s main value propositions is the built-in centralized state management, so yes you’ll have to “wing” local state because that’s shoehorning a foreign concept into it. You are looking for something that fits your existing mental models, and not really judging their goals and strengths.