OpenSearch: AWS fork of Elasticsearch and Kibana

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by marvindanig on Monday April 12, 2021 @06:30PM (#26785987)

Coincidentally, AWS hasn't open-sourced anything that they use internally. Zilch. Nada. And yet they are using 'open source' developed by another firm (smaller is inconsequential here) to market themselves.

IMO, FOSS licensing is completely broken. Its definitions (of what is free/open) are from a boomer's era that is no longer sustainable. At least I wouldn’t want any of my FOSS projects become “corporate strategy” of any particular proto-nation.

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by pas on Monday April 12, 2021 @09:03PM (#26787063)

That made me wonder which megacorp did? Google published a lot of papers about their architecture, but no code. They have many open source projects modeled after internal tools (eg. bazel), but there's no search/GFS/mapreduce/monorepo OSS project from them. MS has VSCode, that's great, and they even open sourced .NET. But Azure is a full black box, just like (almost) every Windows component. (Finally calc.exe is OSS!)

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by zokier on Tuesday April 13, 2021 @04:15AM (#26789516)

> Coincidentally, AWS hasn't open-sourced anything that they use internally. Zilch. Nada.

Firecracker. s2n.

Not much, I agree

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by PHGamer on Tuesday April 13, 2021 @12:40AM (#26788186)

gplv3 was supposed to fix this though no?

[ Parent | on HN ]