3 ms·
According to the dictionary, a framework is "an essential supporting structure of a building, vehicle, or object". In software it's the same thing. The framewo
by pnako 6y ago
According to the dictionary, a framework is "an essential supporting structure of a building, vehicle, or object".
In software it's the same thing. The framework defines the structure, you just fill in the blanks like you would fit floors, add wheels, etc.
The pro is that it's an easy way if you want to build an application that closely follows an existing type of application. But it's too constraining if you want to be able to customize the structure down the line; all of a sudden, you realize that it's defined outside, in a technology that is not your own and you don't understand.
- zenhack 6y agoBack when I was doing a lot of Python work I was a big fan of Flask. The reason is that it really just provided an integration layer for existing stand alone libraries; it didn't feel like I was buying in to some massive framework, just leaning on Flask to get rid of some of the boilerplate glue code that is otherwise need to write to e.g. find a jinja2 template, render data with it and then turn that into an http response. Just `return render_template(...)`. But if there wiring became inappropriate it's ultimately not doing that much, and it's easy enough to take that template and use it in a different context.