Hi, I'm John, Multi Startup Builder.
I enjoy both coding and marketing.
See all my 20 products here
→ johnrush.me
→ my BIO
→ Say Hi to me On Twit...
For further actions, you may consider blocking this person and/or reporting abuse
SolidJS is absent here. Would love to see it also in your list. Lots of upsides.
What about writing it yourself and submitting here?
Just Vanilla JavaScript
<todo-list>
in one page:Result
Tab, and wonder why you are still developing with Build and Compile steps...Note: This whole "comparison" of six frameworks ofcourse just is clickbait to mention MarsX
To compete with MarsX I would have added just one dependency (the custom element) and write only HTML:
But if you prefer more keyboard strokes; feel free to do it the MarsX way:
the key goal was to show very basic example for all 6,
In future articles I will dive in to routing, state and more
Having worked on many of these amazing libraries and frameworks for the better part of a decade now, I can confidently create something in just a few mere days, that in JQuery would have taken me hours.
:D
Astro is missing from this list
gonna add it into a new tutorial
Great post bro!!! Thank for sharing it.
However, with the "script setup" syntax of the Vue 3 Composition API, the script is reduced to just this:
new new one is short, but I still like the old one, still using vue3 with options api
XSS vulnerability though
I wish VanillaJS was in the mix. (Although I readily admit I'm partial to Elm.)
Why more dependencies with VanillaJS?
You can do it in 3 lines of fairly readable native JavaScript, see my comment below
It appears you are not familiar with VanillaJS.
Dude... SolidJS.
Which tool is best?
So, we can ask the same question about tools: Which tool is best?
well, my personal favourite is....
hammer for me
...but it should be reactive. Most important to write TODO's
I was hoping for some actual comparison of these frameworks and how they work, their strengths and weaknesses. This looks like something that ChatGPT could have generated...
honestly I had no idea anyone is gonna read my articles,
Now that lots of people read it, I will make more detailed articles, for all topics I covered with simple takes
Cool information on JS frameworks
thx
From time to time I read about Elm being inspired by Haskell. Always curious where this claim originated from. Elm's syntax looks much more similar to ML-family languages such as OCaml and F# than to Haskell.
Engaging and informative article, John. 👏 Loved the humor!
"Elm" - when you need extra job security :)
Cool comparison! 👍🏻
thx Chris
this is sleak :)
Great article. Also those are not apps but a very basic components. Which does not cover at least 10% of what a real SPA should be. State management? Component communication? Nah!
I would have to write a book size article to cover an app you describe.
But actually I will do it. Wait for in on Monday or Tuesday.
I built something for everyone.
It's the fastest,
We can prove over again.
It easy normal and nothing else.
No virtual Dom.
Welcome to cradova.
Here's a basic Todo app example.
No transpiliing needed, faster tooling as a result and more performant apps.
Cradova was originally built for performant pwa, but for that you can use it for any web project.
github.com/FridayCandour/cradova
I personally moved from Vue to Svelte, then from Svelte to Elm. The problem with Elm is that once you get a bite of that Functional Programming drug you can’t go back to JS or even TS 😉
I did the opposite. I went from Vue, to Elm, to Svelte. I had trouble getting some things to work with Vue and Elm that worked out easy with Svelte. Also, my Svelte code did more work with less code (after compiling Svelte). But, that was my experience. Mileage may vary.
Not really the opposite, as I also moved from Vue to Svelte, just without the Elm step 😉
So we agree we had a better developer experience with Svelte compared to Vue. I love Elm for its fearless refactoring capabilities and its ML-like syntax.
whats best tutorial to get into ELM?
Angular is king
Yea , as far as productivity doesn't matter.
or hiring new teammembers who actually understand Angular