News for hackers. Stuff that matters.
Re:Apache Flink by rakoo on Wednesday January 30, 2019 @02:45AM (#19033390)
> As does any competition.

Those are open-source frameworks, which is antithetical to competition. The whole point of open-source is that the contributions of one entity can benefit everyone, while in this situation, having so many frameworks "dilutes" the efforts because the same problems need to be solved in each framework. Smartphone makers aren't here to share their technical advances with everyone, they're here to make money.

I'm not saying we should purposefully agree on killing all but one framework, but the ideal situation is if one or two come out at the top as being just the best in their category so that everyone just use them, and all efforts converge towards those.

Re:Apache Flink by virgilp on Wednesday January 30, 2019 @03:04AM (#19033467)
I don't think that's how it works; "best" is sooo hard to define. Humans are very diverse, and have different needs/preferences. Also what is best today may not be best tomorrow (not because of the system itself, but because of changes in the environment), so it pays off to have "sub-par" systems evolve in parallel with different slightly different goals or implementations.

I don't see "open-source" as being antithetical to competition, at all. In fact, e.g. Databricks only exists because of Spark. There is competition in the open-source world too, and IMO that's a good thing.

Re:Apache Flink by PurpleRamen on Wednesday January 30, 2019 @04:48AM (#19033827)
Since when is there no competition and diversity in open source? Isn't too much choice usually a major complain with linux, programming languages, frameworks, etc?
Re:Apache Flink by manigandham on Wednesday January 30, 2019 @10:25AM (#19035757)
Nobody said that. But having too many competing overlapping products does mean more fractured effort spread amongst all of them.
Re:Apache Flink by marcinzm on Wednesday January 30, 2019 @08:05AM (#19034681)
>I'm not saying we should purposefully agree on killing all but one framework, but the ideal situation is if one or two come out at the top as being just the best in their category so that everyone just use them, and all efforts converge towards those.

That assumes you can have a single framework with all the features people want without causing issues (conflicting basic designs, high cost to maintain, deployment costs, configuration costs, etc.).