> The first time I saw it was in a mildly heated debate about whether we should use React. I lost the argument and that org chose Knockout.js with JSPs instead.

> The first time I saw it was in a mildly heated debate about whether we should use React. I lost the argument and that org chose Knockout.js with JSPs instead. You can guess how expensive that "pragmatic" decision turned out. This is an interesting one to me from the opposite side of the decision: I was at a young startup that was a very early adopter of React, and I felt like it slowed the team down at that time. Even though it eventually became dominant, the ecosystem had pretty limited tooling early on, and it seemed like our team spent a lot of time coming up with in-house solutions for things that were eventually solved by definitive libraries (e.g. Redux). From my point of view it had a pretty tangible impact on our time to market for some important features vs using something less shiny. I’m not sure I’d have chosen Knockout and JSP instead (though I was a fan of Knockout at the time for small projects and feel like Vue is a great spiritual successor to it), but the experience certainly colored my decision making in the years since.