top | item 45603232

(no title)

12345ieee | 4 months ago

Not to mention their pro features keep breaking syntax of the community version, obviously with 0 transparency.

Now, of course they should get paid for the work they do, but these sort of "we were FOSS and surprise we're not anymore" are becoming commonplace and are always done hoping no one notices.

discuss

order

saddist0|4 months ago

Honestly, FSL doesn't break any flow for day to day developers. What's the harm? I am curious to know. On the contrary I like competitive vs non-competitive distinction.

DetroitThrow|4 months ago

Most of us don't want to let a court decide if we compete with a very general distinction you describe, and can't afford lawyers to evaluate a 2 year old license without much case law.

Most of us prefer not to bring on a dependency in our project that is primarily designed to extract commercial value from users and is less friendly to contributors than similar open source projects.

sarchertech|4 months ago

It’s because big tech companies have spent millions to foster goodwill towards the OSI Open Source definition. And there’s a general feeling that software that fits that definition is pure and any that doesn’t is unclean.