[Bahamut]

It's possible to do the same with a framework - it is also likely that frameworks and various libraries will be more performant and account for cross-browser issues. For example, I am not going to handcode JS logic with generating SVG for a graph - I'm going to use d3.

[spyder81]

Well, sort of. It's possible if you're willing to take on maintenance of that library if/when they abandon it, and be able to dive into the guts to track down bugs or weird behaviour.

As a good example, we're on the verge of ditching JQuery.

[Bahamut]

Here's the rub though - code will not (likely) live forever. That's just the reality of software engineering.

I always have to dive into the guts of a library to figure out bugs regardless - I feel like that's essential for a software engineer to become well versed in, regardless of whether the work is in frontend or backend.

The cost of not producing at a fast enough rate is something almost no business can afford, especially in the startup world. The speed at which companies have to move are always on full thrust because if they don't move fast enough, then it costs sales, reputation, and gives competitors more of an opportunity for market entry.

Homerolling your own framework/library can be a dangerous operation, and you lose the benefits of the lessons that others have learned in maintaining open source frameworks/libraries.

[davidgerard]

> Here's the rub though - code will not (likely) live forever. That's just the reality of software engineering.

Yes. Only the code you wish wouldn't!

(seriously. I'm maintaining complex logic in ant. AUGH MY EYES)