5 ms·

I don't think they're wrong. Open source does not work with product management. There will always be friction with what is on the roadmap vs what the communit

I don't think they're wrong. Open source does not work with product management. There will always be friction with what is on the roadmap vs what the community wants to add. Additionally, if Wolfram wants to monetize it somehow, they have to own supporting it--including the contributions that they don't necessarily want. If they anger the community, then the community forks the project and Wolfram loses complete control or is in the same place they were before they open sourced it (but now their IP is gone). I don't see how they (Wolfram) benefit from FOSS at this point.

mountainriver 5y ago
Huh? Open source absolutely works with product management, their are tons of companies doing this today. OSS is a great way to market and up sell to SaaS
- carry_bit 5y ago
  But then companies that make their money by upselling to SaaS really don't like it when Amazon comes along, takes the software, and undercuts them in the cloud. The company then scrambles to change their license to disallow that. Wolfram in that sense is just being honest about their motivations by having it be proprietary from the get-go.
  - mountainriver 5y ago
    There are ways of preventing that like what elastic did. If wolfram honestly wants to be the sole computation language no one is going to pay for that all the time
sodality2 5y ago
> There will always be friction with what is on the roadmap vs what the community wants to add. Open source does not necessitate listening to the community. Ever. Even if they were to release it under an OSS license, they could just turn off PRs. Or if it's "source available", same story.
- candiddevmike 5y ago
  Then the community forks the OSS project and you lose control/struggle to maintain parity/mindshare. Gogs/Gitea, VIM/Neovim, Bitwarden/Vaultwarden... The ones that succeed keep the community happy and either focus on adding value on top (open core, don't give away the special sauce) or deliver half assed products (package up the community leftovers and hope support contracts/services fill in the gaps).
  - smoldesu 5y ago
    > Then the community forks the OSS project and you lose control/struggle to maintain parity/mindshare That shouldn't matter if you're making a superior product.
    - monsieurbanana 5y ago
      Well, yeah. So what's in it for them?
      - smoldesu 5y ago
        Free QA/testing, a community of users who can submit patches, word-of-mouth marketing, a large install-base, opportunity to sell support to high-value clients.
        monsieurbanana 5y ago
        What's in it for them, if it turns out the community forks their project and do it better than them? I don't see it as a sound argument.
  - jdauriemma 5y ago
    Correct me if I’m wrong, but aren’t there open source licenses that don’t permit unauthorized distribution? If so, couldn’t they safely release the source code without worrying about competition from forks?

mountainriver 5y ago

Huh? Open source absolutely works with product management, their are tons of companies doing this today. OSS is a great way to market and up sell to SaaS

carry_bit 5y ago
But then companies that make their money by upselling to SaaS really don't like it when Amazon comes along, takes the software, and undercuts them in the cloud. The company then scrambles to change their license to disallow that. Wolfram in that sense is just being honest about their motivations by having it be proprietary from the get-go.
- mountainriver 5y ago
  There are ways of preventing that like what elastic did. If wolfram honestly wants to be the sole computation language no one is going to pay for that all the time

sodality2 5y ago

> There will always be friction with what is on the roadmap vs what the community wants to add. Open source does not necessitate listening to the community. Ever. Even if they were to release it under an OSS license, they could just turn off PRs. Or if it's "source available", same story.

candiddevmike 5y ago
Then the community forks the OSS project and you lose control/struggle to maintain parity/mindshare. Gogs/Gitea, VIM/Neovim, Bitwarden/Vaultwarden... The ones that succeed keep the community happy and either focus on adding value on top (open core, don't give away the special sauce) or deliver half assed products (package up the community leftovers and hope support contracts/services fill in the gaps).
- smoldesu 5y ago
  > Then the community forks the OSS project and you lose control/struggle to maintain parity/mindshare That shouldn't matter if you're making a superior product.
  - monsieurbanana 5y ago
    Well, yeah. So what's in it for them?
    - smoldesu 5y ago
      Free QA/testing, a community of users who can submit patches, word-of-mouth marketing, a large install-base, opportunity to sell support to high-value clients.
      - monsieurbanana 5y ago
        What's in it for them, if it turns out the community forks their project and do it better than them? I don't see it as a sound argument.
- jdauriemma 5y ago
  Correct me if I’m wrong, but aren’t there open source licenses that don’t permit unauthorized distribution? If so, couldn’t they safely release the source code without worrying about competition from forks?