DEV Community

Discussion on: Should I write a new JavaScript framework?

Collapse
 
lexlohr profile image
Alex Lohr • Edited

I'm happy to say that I never finished or released the framework I once started to write, because while it would have gone in the same direction, it would never been as good as solid.js, which is now my favorite framework. I did help with the earlier versions of riot.js and wrote a few smaller libraries. In recent months, I wrote a few primitives for solid.js and one of them is already in production code and proven to work better than the alternatives (far smaller, faster, less bug-prone).

Still, I disagree with your sentiment. If you want a learning experience or an interesting hobby, by all means, write a framework or library. Just don't ever release it unless you can reliably prove that it does its job better than most others available on npmjs. And if it's not that good, don't feel bad about it. The best frameworks have grown over years and had the help of many very talented devs. You can't expect to best them so easily. Don't give up, you'll improve over time.

Collapse
 
hyrumwhite profile image
hyrumwhite

What's the harm in releasing it?

Collapse
 
lexlohr profile image
Alex Lohr

If it's not good, you're basically littering the package ecosystem with a bad package. You're responsible for all the problems arising from that.

Collapse
 
fridaycandours profile image
Friday candour

Nice

Some comments have been hidden by the post's author - find out more