|
|
|
|
|
|
by shubhamjain
4117 days ago
|
|
|
Except that you underestimate the effort in incorporating the "framework" in your new project. Sure it isn't hard per se, but the steps involved in learning every bit of a process that surrounds the framework kills the excitement at some point or other. Like in rails, learning all the routing, code generators, forms, asset pipelines just makes you quit at some point. I think things would be much easier if I had "grown" with rails as its features grew, but now, it being a behemoth, I would be pretty much disinterested in going in the effort of learning it just so I can make my shiny new project. The learning would be much easier, if I get to work on existing codebase but then again, it is a chicken-and-egg problem. |
|
|
I think it goes both ways. Makes some things a lot easier and others a lot harder. Django's admin for example, can often give you 90% of what you are looking for with very little effort. It doesn't take a lot of effort to learn it. The again, if your application falls outside that model, no point in trying to shoehorn it in.
I would also say that frameworks keep things consistent(I know Django well, so based on that). I recently added Django-rest-framework to my application. It took very little to learn that as they have tried to keep the coding style the same as the class based views. Using them is almost the same, so after the initial half day or so in the docs, everything just clicked into place.