2 ms·
Too bad, it was a good product. It appeared around the same time we launched QuantifiedCode, which was a static analysis & automated refactoring SaaS. Our learn
by ThePhysicist 5y ago
Too bad, it was a good product. It appeared around the same time we launched QuantifiedCode, which was a static analysis & automated refactoring SaaS. Our learning was that developer tools are really hard to monetize, except maybe from the security/compliance/productivity angle (which doesn't really target developers though, more their superiors). Developers are just used to "everything" being free & open-source and large organizations like Github/Microsoft keep pushing this angle, as they can monetize their products differently in the long term.
Not sure if this will be good for the developer community though, it seems right now the large cloud players are trying to lock them into a closed ecosystem from which it will be hard to escape. Most open-source code already lives on Github and I'd wager that in 5-10 years most development will take place in cloud solutions, as the complexity of systems increases and makes local development harder. When that has happened I think it's not unreasonable the large players will tighten the screws on developers a bit and start squeezing out more money from them, since it will become very hard to migrate away from that entire ecosystem.
- fxtentacle 5y agoIn my opinion, everyone who's willing to pay for a good IDE is already subscribed to JetBrains. And since they have static analysis, excellent refactoring, and plenty of navigation aids for foreign source code, I never got frustrated enough to start DuckDuck-ing for another external tool that might help. Accordingly, I believe that new developer tools are difficult to monetize because the established ones are already exceptionally good. There's no customer pain to alleviate.