lukaszwojtow
Joined 5 years ago
Karma
76
Submissions
40
Member since
Sep 29
Recent submissions
Comment · 1 year ago
Comment · 2 years ago
Old lcamtuf is back!
Comment · 2 years ago
I feel the same. I think they realise it, but for the lack of better ideas, this is what shareholders want. It's like "we have to collect data, because everyone does it, and use it for anything"
Comment · 2 years ago
Using the code later in a non open-source project can happen also with MIT/Apache licensed code. Even without CLA. Does it mean that company that does it is immoral?
Comment · 2 years ago
I get it. If there are alternatives that overall would be better (including their technical merits and how easy it is to introduce them to a commercial company) then use them. No one is forced to buy dual-license.
Comment · 2 years ago
Good. So now Redis Inc is in trouble because they have to replace community work with their own. If community does most of the work, then what's the problem?
Comment · 2 years ago
Yes, they paid. And they can use the code they paid for. But it doesn't give them right to leech of any future code written by someone else IN THE FUTURE.
Comment · 2 years ago
All this outcry about license switch coming from "community" feels funny. After all, if there is the "community" then they can take the last open-source version and keep developing it themselves, right? But most "communities" are about "take, take, take", not "work, work, work". They often upset only because someone declared they aren't going to work for free any more.
Comment · 2 years ago
If AGPL blocks adoption then "large orgs" can buy commercial license (assuming software is dual-licensed).
Comment · 2 years ago
Problem: They want someone else to maintain this feature long-term.
Comment · 2 years ago
I guess they can fork that "open core", introduce that feature, then maintain it themselves forever. Pull changes from original open core and their "open" branch will be better than original.
Of course they don't want this work. They want the company to maintain it instead.
It's an MVP but perfectly usable. I needed features that I couldn't find anywhere else:
Parameter optimization with a genetic algorithm
Fuzzy optimization: randomly remove trades or whole markets and see what happens
Data mining: find rules how to exit trades sooner for better profit
Compare strategy results to random trading
Check current drawdown for statistical significance
Write trading systems in Java so I can test every idea under the sun and never be held back by some custom "scripting" language.
Of course, it's open-source. A GitHub star is much appreciated. Thanks!