2 ms·

Frameworks and libraries are tools of our trade. The reason to use them or not to use them depends on the context. While it is foolish to become a 'Backbone spe

by arocks 13y ago

Frameworks and libraries are tools of our trade. The reason to use them or not to use them depends on the context. While it is foolish to become a 'Backbone specialist' and look at every project with those eyes; it is equally foolish to dismiss frameworks as prototyping tools. Lots of frameworks interoperate well and are amenable to customisations. The good ones are more than sufficient for most client needs, even for prolonged production usage. Most open source frameworks are results of thousands of man-hours of effort by specialists from different backgrounds. Many aspects like security, modularity and functionality are examined by hundreds of eyes. It is perhaps naive to assume that one's knowledge of the domain is so good that they can roll out their own framework much better than what anyone else has produced. In fact, if that person is so capable, they should be encouraged to post their code for a public review and help others (or possibly be severely critiqued for their questionable design choices).

_getify 13y ago
I post all my tools/libraries publicly on github. I would never have so much hubris as to post some "framework" I created for some site as "The Getify Framework" that everyone else should use. That's completely contrary to the message I'm trying to get out. Ironically, the site I vaguely referred to in the post WAS actually fully open-sourced. But NOT so that people could look at that code and say "Ah, he's saying that I should always do that same thing with every site I build".
- arocks 13y ago
  I get the impression that you perceive building a "framework" as a self-aggrandising exercise created for the sole purpose of standardising software development into creating run-of-the-mill products. Such view would be too hard on the not-so-trivial amount of effort that goes into creating a framework that can be applied to a broad range of use-cases, far beyond what it was originally conceived for. In fact, the truth is that it is too easy in programming to skip the painstaking effort of reading and adapting to someone else's codebase. It is simply convenient to throw everything away and start from scratch embracing the (in)famous "Not Invented Here" syndrome.

by arocks 13y ago

_getify 13y ago

I post all my tools/libraries publicly on github. I would never have so much hubris as to post some "framework" I created for some site as "The Getify Framework" that everyone else should use. That's completely contrary to the message I'm trying to get out. Ironically, the site I vaguely referred to in the post WAS actually fully open-sourced. But NOT so that people could look at that code and say "Ah, he's saying that I should always do that same thing with every site I build".

arocks 13y ago
I get the impression that you perceive building a "framework" as a self-aggrandising exercise created for the sole purpose of standardising software development into creating run-of-the-mill products. Such view would be too hard on the not-so-trivial amount of effort that goes into creating a framework that can be applied to a broad range of use-cases, far beyond what it was originally conceived for. In fact, the truth is that it is too easy in programming to skip the painstaking effort of reading and adapting to someone else's codebase. It is simply convenient to throw everything away and start from scratch embracing the (in)famous "Not Invented Here" syndrome.