5 ms·

Where does one draw the distinction between micro- and megaframeworks? Or, for that reference, just a "framework"?

• d0m 15y ago
  Things a company will ask you to know is a megaframeworks. Else, it's a micro or simply framework. Obviously, I'm not serious here; but there's some truth in it. I.e. You'll see some companies ask for django or rails developers; not for flask python hacker right ;-)
  • defnull 15y ago
    Your point is interesting, but I would look at it from a different angle: If you need a highly paid specialist with many years of experience to fully master a framework, call it mega-framework. If it fits your brain and can be learned over the weekend, its a micro framework. Everything in between is just a framework :)
• the_mitsuhiko 15y ago
  > Where does one draw the distinction between micro- and megaframeworks? Or, for that reference, just a "framework"? Here is how we (Flask developers) define microframework: http://flask.pocoo.org/docs/foreword/#what-does-micro-mean http://flask.pocoo.org/docs/foreword/#what-does-micro-mean
• DasIch 15y ago
  The difference between a library and a framework is simply that you call the library whereas the framework calls you. The framework provides a frame into which you put your code as opposed to a library which you use as part of your code. Generally I would consider any framework which requires (almost) no setup requirements to be a microframework. This is opposed to frameworks which require a basic configuration, directory layout or certain files to be present. However there are a lot of other people with other definitions regarding this, the distinction is not at all very clear for example there are people that consider being written in a single file to be a distinguishing feature of microframeworks.