HackerTrans
TopNewTrendsCommentsPastAskShowJobs

drakaal

no profile record

comments

drakaal
·13 anni fa·discuss
At our shop we don't use frame works, well at least none that came from anyone else.

The problem with frame works is that if you need to modify them, then you no longer can just update them when everyone else does. You are stuck always making changes to the framework ever after as they new ones come out.

But also you don't often fully know what the code does. If you have code that does something you don't understand then you end up not understanding how it changed later.

With Front End Development things like TwitterBootStrap get you a great looking site very quickly, that is nice. But if you want to tweak things suddenly your version isn't going to be the same as the stock version and you can't have it be cached from some fast CDN, and so your site is slower than it should be.

With BackEnd small changes to the official version of a framework can introduce bugs. Sure this is also true of things like Minor Revs to the language. (A lot of people got burned by moving to PHP 5.4 before WordPress was ready for it, and had only decided to enable auto updates to PHP because WordPress 3.2 required PHP 5.1) (And I'm not fond of PHP or WordPress so don't flame me because this is my example, it was one of many, but one that a great many people experienced so I figured the enormity of the event made it a good example)

The moral of the story is OWN YOUR CODE. The more you rely on other people's code the less you are the master of your own fate.