|
|
|
|
|
by bhousel
5547 days ago
|
|
This article is somewhat blogospam. But it does raise a point that I wanted to mention. In many cases (and Windsoc is such a case) when you are trying to sell to developers, your competition isn't the developer's wish to "do it myself". Your actual competition is the plethora of open source tools that already do the thing that you're trying to sell. Software development has changed, and those vendors trying to build a business selling libraries and toolkits are going to find it difficult to stay relevant. Protip: If a search on http://ruby-toolbox.com/ turns up half a dozen gems that do the same thing that you're trying to sell, well, you're doing it wrong. |
|
1. Libraries are static, with versioning and upgrades, whereas platforms are real-time.
2. Libraries are based on a one-time usage, whereas platforms depend on providing constant value to maintain users.
3. Libraries do not generally offload any work to other servers, whereas platforms can provide efficiencies.
4. Libraries are platform, language, and version specific, whereas platforms can be built through protocols like REST and JSON that are known to most stacks.
That being said, open source libraries aren't always free when it comes to support and technical costs, and not all platforms are closed-source.