Comments on: When not to use a framework

By: Arconan

Arconan — Tue, 09 Sep 2008 19:39:49 +0000

Very good point, developers for some reason is not happy buying a part, they HAVE to buy the whole damn car.

Use only what you need, even when it comes to frameworks.

By: Trandafir

Trandafir — Sat, 06 Sep 2008 10:12:20 +0000

Your 579 argument is flawed. It was more like 579 lines of Ruby /plus Rails/.

By: Niyaz PK

Niyaz PK — Thu, 26 Jun 2008 14:27:02 +0000

Duncan,
Exactly what I was trying to say. As you pointed out, many enterprise solutions use these big frameworks simply for the sake of it.

By: Duncan

Duncan — Thu, 26 Jun 2008 13:54:12 +0000

Absolutely, I wonder that for even those enterprise apps that make extensive use of frameworks whether they get any real benefit out of them.

What’s the point in making something re-usable if you’re never going to re-use it?

And if you don’t follow it through ALL THE WAY (unit testing, mocking, documentation etc) then chances are it’s costing you more to develop, and you’re never going to get the payback you should.