How many Improvements needed for an Innovation?
A speculative question, perhaps. But it reveals a bare truth: improvements don't make innovations. Improvements are pieces of a puzzle. Refined and sharpened with every new version, they are absolu...

Source: DEV Community
A speculative question, perhaps. But it reveals a bare truth: improvements don't make innovations. Improvements are pieces of a puzzle. Refined and sharpened with every new version, they are absolutely necessary to form the puzzle. But no matter how polished they are, they remain pieces of a flat puzzle. Innovation is when multiple puzzles compose into a new structure. Back in 2009, Google was polishing the pieces of their remarkable V8 engine. Then Ryan Dahl proved once more that everything ingenious is simple - compose the V8 puzzle with other state-of-the-art puzzles, and a new structure emerges. That's an innovation. Today we have plenty of brilliantly polished, state-of-the-art frameworks. Each performs perfectly well on its own. Each with lot of features and few of limitations - each a complete puzzle in its own right. And that's entirely normal. Developers choose a preferred stack and excel in that direction. The ecosystem thrives on specialization - Vue devs feeling at home in