Hacker News new | past | comments | ask | show | jobs | submit login

To me, Handsontable's position is much more understandable than Elastic's, because Elastic could (and do) monetize as a service. That's not really practical for Handsontable.

The only way I see to get money out of someone for a product like Handsontable, while maintaining an open souruce version is by withholding some features + extended support. That's what they've been doing and they've said it hasn't been bringing in the return they need.

In Elastic's case, they have a product that is easy to monetize while keeping an open source version: you offer your product as a (hosted) service + extended support, so if people don't want to deal with setting it up themselves, they pay you. Docker seems to be a good example of this. The open source version is still fully availiable and can be used however you like, but comes without that extra support (and maybe a few features).

Instead, Elastic has stuck a bunch of proprietary code on Github, seemingly to bait people into use it, when they're not allowed to. Handsontable aren't doing anything like that. Once they go proprietary, they're archiving the repo. It's still there if people want to use it, but it's not being maintained. That's really no different to any other random piece of abandoned code on Github (of which there is plenty).




> Elastic has stuck a bunch of proprietary code on Github, seemingly to bait people into use it, when they're not allowed to. Handsontable aren't doing anything like that. Once they go proprietary, they're archiving the repo.

That's not true, last month https://github.com/handsontable/handsontable/ was MIT licensed, today it is proprietary. Handsontable is attempting the same sort of "baiting" that Elastic did. There is no evidence they are archiving the old repo, and in fact they are archiving the proprietary repo and merging it into the open source one:

> The Handsontable Pro package on NPM is marked as deprecated and the repository on GitHub is archived (made read-only)




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: