loading...

Discussion on: Todo-MVP: Or 'Why You Shouldn't Use A Web Framework' - The Revenge

pizzapanther profile image
Paul Bailey

I agree you can do a lot without a framework. But you can do something more "professional" with a framework faster at least initially. To get to that uncomplicated code probably took years of experience. Most people even if they know the basics write bad code and it takes years to make it good and uncomplicated. A framework at least guides you along until your good enough to do those on your own. The real problem comes when trying to throw away the framework when you don't need it any more.

Abstractions are hard to get right. And an abstraction that has been vetted by a community and implemented in code is hard to beat.

Thread Thread
gypsydave5 profile image
David Wickes Author

Abstractions are hard to get right

Too right they are! Abstracting away a database - awesome. Abstracting away the underlying bytes of an HTTP response - I'm a fan.

But what does, say, Angular abstract? What is the underlying entity that is abstracted by Ruby on Rails?

In my opinion, they are not abstractions at all. They're tarballs of multiple abstractions, an attempt to generalize certain business requirements. I think you'll get so far with this, but in the end (as you rightly say):

The real problem comes when trying to throw away the framework when you don't need it any more.

Thread Thread
pizzapanther profile image
Paul Bailey

I would love to see a discussion about what frameworks have a good off ramp when you have out grown them. Do they exist? Or what are some techniques to do so? Or which frameworks are the most flexible and let you interchange the pieces?

Thread Thread
gypsydave5 profile image
David Wickes Author

I would love to see a discussion about what frameworks have a good off ramp when you have out grown them.

Now that is a great question. I think you could dip your toes by Googling 'How I migrated Angular to React' to get some idea.