[csbrooks]

Ranting gets attention, so people rant.

I've noticed people will use some library or platform or language, and at first they'll love it. Then two or three years on, all they can see are the places it falls short in the domain they're working in. I've personally experienced a disconnect when I'm still in the honeymoon phase, and the speaker has progressed to the "I-hate-this-it's-terrible-throw-it-out" stage.

[sanderjd]

I think this is just because of the classic leaky abstraction problem. At first a new abstraction seems amazing, but after using it long enough you've seen enough of its leaks to become disenchanted.

[csbrooks]

Interesting. I'll have to think about that some more.

I've been assuming it's because of human nature: when something's new and shiny, we see all the cool new things it will do for us. After being around it for long enough, we tend to only see the flaws, and forget all the benefits.

[endersshadow]

It could also be a combination of the two--they're not exactly mutually exclusive.

[k__]

Maybe people need to use fewer libs/frameworks?

The first company I worked as a dev for, while I was studying, wrote most stuff they used themself.

This led libraries and frameworks to just "fit".

But the company structure probably was different.

There was the development, who implemented frameworks and there were the consultants who implemented the end user stuff and installed/maintained it.

Most other companies I know just had a few consultants for customer-admin-stuff and planning and the devs did everything else...

[scuba7183]

Or use a 3rd party framework until you see it's problems and more fully understand it's actual use. Then you can write your own

[k__]

Or this, yes.

The problems I see, are, you have to get fluent in the new framework and sometimes this requires as much time as writing your own stuff :\

[cnlwsu]

Just hang on until the "stockholm" phase.