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

They had Elastic as an example to work off of (and how badly that was received). They did it anyway. No sympathy.



I would take the continued fall of the dominoes (Mongo, Elastic, Hashi, Redis...) as a sign that the impact on the businesses who do this is positive or neutral, and it's just the HN bubble that creates the sense that there was an outsized public outcry over the changes that should make other companies wary. These guys aren't following suit blissfully unaware of the backlash against similar moves: as they measure it the backlash was weak enough that the business folks decided it was worth it to follow suit.

In my experience working in the industry, I wouldn't even have noticed that any of these license changes had happened if I weren't on HN. My company uses all of Mongo, Elastic, and Terraform and there hasn't even been a whisper of switching away from any of them.


So how do you interpret that Elastic has switched back to a FOSS license?


That they're being fully honest and open about the fact that it doesn't matter anymore and they would rather be open source if possible? I don't have any compelling reason not to take them at their word when it comes to their motives, because no data I can find suggests that the switch was bad for them.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: