"Ah no, reusable frameworks and libraries are a terrible idea. What you need is a bunch of very lightweight files that you can copy / paste from project to project"

- Mobile Architect, Large m.n.c, 10+ years experience.

Maybe he is right, i personally don't use any framework, but during my dev experiences i ended developing my own framework and i'm using it on evry project now.

I'm not saying that the open source frameworks are useless or anything, but i perfer coding my stuffs on my own so i can enhance my technical approaches.

Just a humble opinion.

@Baguette Well in this case I was referring to frameworks we had built to be shared and distributed, both open source and across our internal projects.

While I sometimes do as you said for the learning experience. The vast majority of the time it can be dangerous and irresponsible.

When building a large scale app for a huge company, going to be used by millions of users, I would never ignore the library that has been battle hardened by 10,000 developers.

Also if you are charging a client, I find it a little hard to justify adding an extra week or 2's work into the quote because I chose to not use the perfectly functional open source library and build my own, for no other reason than I wanted to.

@practiseSafeHex i see your point there, but i think we don't have the same definition of framework.

I do use extrernal libraries but zero framework, as i said i have developped my own framework that respond to my needs, and everytime i work a new project i try to improve my framework at the sametime.

Working on a huge scalable apps require a team work and a specific framework for the app, if you use an extrernal framework for a "huge scalable" app can be very dangerous as the app performance are dirictly related to the framework's.

Again i'm not saying frameworks are bad, but i think every framework is meant to serve and resolve certains problematics

In my opinion, big apps need to creat their own private framework ex : Facebook ( PHP HACK ).

I once worked with a team to creat a private framework, it was a good experience that allowed me to discovred how bad technically i was.

@Baguette Ok yes we have very different definitions of "framework". I very recently researched this due to confusion on our team.

While a little vague, the most accepted definition of "framework" makes it incredibly close to "library".

A library is a package, module, jar etc. that an app invokes, that returns a result that the app uses. E.g. think of a mathematics library that performs calculations.

A framework is also a package, module, jar etc. that an app invokes, but rather than returning a result, the framework asks for code, to be executed when a condition is met. E.g. networking module that requires passing in callback functions.

Apple use this definition, all of their packages are referred to as "frameworks", even though some are very small. Many frameworks are imported into an application or file, and serve 1 specific use case e.g. Networking call, AV capture, AV editing etc.

Framework is frequently used in place of "process", "toolset", "toolbox", "sdk" etc