So a CRM that replicates Salesforce APIs? Sales people don’t want a Salesforce FOSS version, that’s why they green light salesforce. It’s about trend not practical software. Only dev teams that have been implementing Salesforce for 5 years want a FOSS version.
Salesforce's biggest value proposition is the partner ecosystem, which Salesforce has cultivated for like 20+ years. Some platform companies (Shopify comes to mind) cannibalize their plugin ecosystem by adding similar functionality to the core platform, but Salesforce deliberately avoids competing with software/services in the partner ecosystem. It's such a safe bet to build on top of Salesforce, because there's basi…
> Some platform companies (Shopify comes to mind) cannibalize their plugin ecosystem by adding similar functionality to the core platform, but Salesforce deliberately avoids competing with software/services in the partner ecosystem When do you compete, and when do you cultivate? Are some business sectors better at one versus the other?
Also insert the standard HN comment of “I can’t believe it’s [CURRENT_YEAR] and this functionality isn’t part of the core platform itself”
So a CRM that replicates Salesforce APIs? Sales people don’t want a Salesforce FOSS version, that’s why they green light salesforce. It’s about trend not practical software. Only dev teams that have been implementing Salesforce for 5 years want a FOSS version.
Salesforce is a generic application platform today, and this is how see it. Openkoda is not a drop-in replacement for Salesforce CRM, it is a useful replacement when you want to build your core business application a) retaining full source code ownership and ability to get any Java/JS team to work on it and run anywhere you want, b) without becoming dependent on technology and commercial limitations of working with big S.
In true enterprise fashion, they went with Java. Enterprise, confirmed.
Honest question, what's wrong with Java? It's performant, has mature libraries, good documentation, and supported pretty much everywhere.
There's plenty I'd like to improve but it's honestly in a very good shape. There's a reason enterprise picks Java - it's battle tested and there are enough quality developers around. Frameworks like Spring for webdev are top notch. Unless you've got a very specific reason to pick something else (python or rust or whatever) Java is the safe bet (along with c# but Java is an order of magnitude bigger I think).
It's just people taking memes seriously. Java is great and continuously improving.
So a CRM that replicates Salesforce APIs? Sales people don’t want a Salesforce FOSS version, that’s why they green light salesforce. It’s about trend not practical software. Only dev teams that have been implementing Salesforce for 5 years want a FOSS version.
Well, there is Odoo. Which is pretty much exactly what OpenKoda is (FOSS ERP).
Odoo is doing quite well. It made Fabien Panckaers the youngest billionaire in Belgium.
So a CRM that replicates Salesforce APIs? Sales people don’t want a Salesforce FOSS version, that’s why they green light salesforce. It’s about trend not practical software. Only dev teams that have been implementing Salesforce for 5 years want a FOSS version.
Well, there is Odoo. Which is pretty much exactly what OpenKoda is (FOSS ERP). Odoo is doing quite well. It made Fabien Panckaers the youngest billionaire in Belgium.
Yes, I think you could compare Openkoda with Odoo, but well... we are nowhere near being billionaires ;)
So a CRM that replicates Salesforce APIs? Sales people don’t want a Salesforce FOSS version, that’s why they green light salesforce. It’s about trend not practical software. Only dev teams that have been implementing Salesforce for 5 years want a FOSS version.
Well, there is Odoo. Which is pretty much exactly what OpenKoda is (FOSS ERP). Odoo is doing quite well. It made Fabien Panckaers the youngest billionaire in Belgium.
Odoo's quest for monetization from open source has been a bit off-putting. I stopped using it a few quarters back due to that. Community and Enterprise are becoming too disjointed.