5 ms·

Sorry but this is the kind of attitude that hinders progress. I often hear people say "don't use a framework, make your own", well these guys did and they relea

by poxrud 12y ago

Sorry but this is the kind of attitude that hinders progress. I often hear people say "don't use a framework, make your own", well these guys did and they released it for free, I don't see the problem. No one is forcing you to use it. Even if T3 has one good new idea that gets integrated into another framework then it's already a win.

nostrademons 12y ago
The point of the "don't use a framework, make your own" is that your needs are different enough from everyone else's needs that it's worth writing code just for your needs. The problem with releasing a framework is that your needs are different enough from everyone else's that it's not worth releasing that code. Personally I'm glad that T3 released their framework - it doesn't harm me, after all, and they did all the work - but I think some people have unrealistic expectations on the value of code re-use. The problem is the economic incentives in the software market: chances are, if your problem is close enough to somebody else's problem that you can re-use the bulk of their UI code, your market is too undifferentiated for you to exist as a separate company. When frameworks do attain market success (eg. JQuery in 2006, when IE6 was the dominant browser, Firefox & Safari were brand new, and Chrome didn't exist), it's usually because the big company in charge of the overall platform has been asleep at the wheel, and then the need for a framework disappears once they get their act together and start moving the platform forward (eg. JQuery in 2014).
- rtpg 12y ago
  In the world of Enterprise software (which is where most of the money actually is), most peoples needs _aren't_ that different. Basically everyone is writing CRUD + data summaries. I'm curious as to why you think JQuery is a framework. From my view of things, it seems to be a library in all definitions I've encountered.

by poxrud 12y ago

nostrademons 12y ago

The point of the "don't use a framework, make your own" is that your needs are different enough from everyone else's needs that it's worth writing code just for your needs. The problem with releasing a framework is that your needs are different enough from everyone else's that it's not worth releasing that code. Personally I'm glad that T3 released their framework - it doesn't harm me, after all, and they did all the work - but I think some people have unrealistic expectations on the value of code re-use. The problem is the economic incentives in the software market: chances are, if your problem is close enough to somebody else's problem that you can re-use the bulk of their UI code, your market is too undifferentiated for you to exist as a separate company. When frameworks do attain market success (eg. JQuery in 2006, when IE6 was the dominant browser, Firefox & Safari were brand new, and Chrome didn't exist), it's usually because the big company in charge of the overall platform has been asleep at the wheel, and then the need for a framework disappears once they get their act together and start moving the platform forward (eg. JQuery in 2014).

rtpg 12y ago
In the world of Enterprise software (which is where most of the money actually is), most peoples needs _aren't_ that different. Basically everyone is writing CRUD + data summaries. I'm curious as to why you think JQuery is a framework. From my view of things, it seems to be a library in all definitions I've encountered.