291–300 of 438 posts
Perfect case for a megacorp destroying open source plus business models. I start to hate amazon with a passion. Craziest thing is they are not paying taxes in Europe though they dominate the market. Amazon needs be broken up. It's too big and too mighty.
It's not too difficult to wait an extra day or two for products.
Will be interesting to see the resources that AWS will throw at this. You can get a sense of the resource that elastic.co is throwing at elasticsearch at https://public-001.gitsense.com/insights/github/repos?r=gith... I'm currently indexing the fork, so in about an hour or two, I'll provide the insights for the fork as well.
I scrolled back through the commits. It looks like they've been removing traces of x-pack, Elastic branding, licensing checks, etc. since the beginning of March. So far it looks like one person is doing the bulk of all that work. If there are new features, I haven't seen any. The real question is do they have a team for new feature work that they are putting together or is this just a fork that is doomed to fall behi…
Earlier quoted context omitted.
It may be relative but it isn't proportionate. A 11B market cap company can field a similarly competent legal department as a 2T market cap company can. I, with 25k, absolutely could not afford the same lawyer someone with 1M.
Have you considered that guy with $1M won't be willing to drop like $50k (2x your net worth) on a lawyer just to squash you? He must have possibility to earn $100k in process to do that. Well unless you really pissed him off. If you earn $25k a year and he spends $50k in one year to take your cake. Well unless he really is your competitor that can make use of your defeat he still needs 2 years to get even. Then it pr…
There is no way on earth that I would look at my "value" and compare it with a £50K "value" to decide on my legal "battle-worthiness." It is quite likely that we both have similar (to the same power of 10) insurance for whatever it is we are duking it out over. Anyway this is all a bit circumspect.
Against a company with billions to play with? I'll just keep my head down and crack on and hope not to be noticed 8)
How did that became an 'ethical position' ? If I am OSS dev, why should I contribute to them vs OpenSearch?
I feel Amazon took the feedback from the DocumentDB/MongoDB fiasco to heart and made positive change in their approach. DocumentDB is a closed source proprietary database created by Amazon to emulate the MongoDB API. Think Google's Dalvik runtime vs Sun/Oracle's JVM. This time around we have an open source fork of ES with big backers all contributing and very permissive licensing. In both cases, Amazon gets to implem…
On the other hand, MongoDB is already sort of obsolete and trending towards death by the time that all ended up happening while ElasticSearch is hot and "new".
Earlier quoted context omitted.
Could you provide a link to explain how it violates "Rules 1, 5, 6 & 9 of the OSD"? Thanks
Common freaking sense reading. https://opensource.org/osd If you can't use the software because you're a cloud provider, that's rules 1, 5 and 6 easy. If using it forces you to relicense all of your code under the SSPL that's rule 9. It is well known at this point that the SSPL withdrew their request for recognition to the OSI because they do not meet the rules of the OSD.
Earlier quoted context omitted.
When I think of Google I think of Go, Angular, protobuf, Bazel, Dart, Flutter, Android, Chromium, Kubernetes, Tensorflow, etc. When I think of MS I think of C#, TypeScript, VSCode, .NET When I think of Facebook I think of React, Flux, Jest, PyTorch, GraphQL, Haxl When I think of Apple I think of Swift, WebKit When I think of Amazon...I can't really think of anything
I would add Kotlin to Google's credit. But I think it's important to note that these companies don't contribute to open source out of any moral obligation, do they? I think they do it to tie more developers and development around their eco-systems and products. Maybe Amazon should get smart and start doing something similar. Or maybe they don't need that. But in any case I don't hold it morally against them that they…
Earlier quoted context omitted.
> they can invest more resources into developing it than the original team ever could. I know this is a popular narrative, but as someone who works on AWS, I think you would be shocked by how small the individual dev teams are that build and maintain the services that everyone uses. I'm not going to downplay the network effects involved. Of course AWS has a tremendous advantage in being able to standardize the custom…
Could you please shed some light on how many people would be behind a product like AWS Lambda or AWS CloudWatch? As an outsider, I would guess huge swaths of developers with a massive hierarchy. Buildings full of folks working on AWS services. I have no idea and extremely curious.
Earlier quoted context omitted.
Forking OSS isn't bad faith. If you want to make people pay you, make your software proprietary. In that case, however, you wouldn't get the free ride into the market that being OSS gives you.
Yes. This is how you discourage people from doing OSS. "You can't stop me" argument leads to a slippery slope and if you care about the open-source you see it differently. Not because you can, but because of the consequences of your doing.
I get that this is inconvenient for Elastic, but it’s good for users.