DEV Community

loading...

Choose Your Own Framework: The Curse of JavaScript Fatigue

David Neal
Family man, musician, illustrator, software developer, and Microsoft MVP living in North GA. Runs on a high-octane mixture of caffeine and JavaScript, and is made entirely of bacon.
・1 min read

How will your project die? Choose from 2,147,483,647 possible endings!

How will your project die?

Discussion (3)

Collapse
nektro profile image
Meghan (she/her)

I really love Vanilla.js™

Collapse
reactiveintent profile image
Mvsica Donvm Dei

My project would die if I use an existing framework, due them all being based on a component approach that leads to data and event limitations. I favor an approach where logic and state are extracted and more loosely coupled. IMO, data-flow and control along with state machines are a better way to go.

Slowly but surely I have considered and vetoed to bypass the popular frameworks and instead build the framework my app requires. This strategy is looking good and it is now clear that I am engineering a new way to build apps. These days JS is great and RxJS is wonderful and template solutions like lit-html are perfect.

Collapse
cat profile image
Cat

The suffering. It is 2real4me.