Not Another Framework

Re:Not Another Framework by Chyzwar on Thursday January 27, 2022 @05:43PM (#30108058)

I will not touch remix with 10 foot pole. It is from react-router authors, it is only open source that bring my worst emotions.

[ Parent | on HN ]

Re:Not Another Framework by midrus on Friday January 28, 2022 @01:25AM (#30111309)

Same. Got burned so badly by it. And I'm pretty sure same thing will happen with this framework.

Can see how 1 year from now it is a totally different thing impossible to update without rewriting everything because they've got a new idea.

[ Parent | on HN ]

Re:Not Another Framework by pandesal on Thursday January 27, 2022 @06:07PM (#30108341)

Why?

[ Parent | on HN ]

Re:Not Another Framework by ithrow on Thursday January 27, 2022 @07:00PM (#30108853)

Every new release was like "we broke backwards compatibility but we got it right this time", rinse and repeat

[ Parent | on HN ]

Re:Not Another Framework by dmitriid on Friday January 28, 2022 @12:41AM (#30111024)

The upgrade docs for the latest release is like War and Peace.

For a frigging router. With lots of things like "we renamed this or that option or component for literally no reason"

[ Parent | on HN ]

Re:Not Another Framework by doteka on Friday January 28, 2022 @06:40AM (#30113413)

What do you mean for no reason? The authors run a consulting shop and give trainings on this library. They are clearly incentivized to break things regularly.

[ Parent | on HN ]