Archbee (www.archbee.io) | Bucharest, Romania / Remote EU
Hiring for Frontend Developer (React), Content Writer (developer focued), Growth Marketer.
Open positions here: https://www.linkedin.com/company/archbee/jobs
HN user
Archbee (www.archbee.io) | Bucharest, Romania / Remote EU
Hiring for Frontend Developer (React), Content Writer (developer focued), Growth Marketer.
Open positions here: https://www.linkedin.com/company/archbee/jobs
I felt the same way, until I found a friend who has been doing the same, so we vent to each other almost daily.
I'm still solo, but he built a team (and got to YC while I got rejected) so there is a lot to go at :)
I believe no party is in the wrong here.
Elastic has the right to take the code private. Basically they are making a fork.
AWS also has the right to create their fork and contribute to it.
If we're playing the game of "who's the bigger dickhead" I would say it's Elastic. Before these 2 forks, many companies benefitted from hosting Elasticsearch for their customers. From their reasoning, it seems that only they should benefit from the code. Which is not Elastic's by the way. It belongs to the world.