It's more about where the decision power comes from. Can you imagine a Rust RFC that added PATENTS to rust?
-
-
Replying to @wycats @dan_abramov
True also for Vue. From what I understand though React's is LESS dangerous than anything else from a major corp like Google or MS.
1 reply 0 retweets 0 likes -
I'd be fine if framed as big corps vs independent devs ie Vue or Ember. But you were using React's uniqueness as de facto evidence of guilt
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @dan_abramov
PATENTS is a uniquely bad patent license.
1 reply 0 retweets 0 likes -
Replying to @wycats @dan_abramov
What license does Google and MS attach to their frameworks, to protect us from *their* patent arsenals?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @dan_abramov
Seriously casting this as a benevolent act by Facebook is silly and I wish you'd stop doing it.
2 replies 0 retweets 0 likes -
Replying to @wycats @dan_abramov
Not benevolent, just less bad compared to what exists with the other big co's; I wish all software patents would die.
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @dan_abramov
Being overt with PATENTS is in many ways worse. Unilateral licensing terms in OSS is bad news.
2 replies 0 retweets 0 likes -
Replying to @wycats @dan_abramov
I wish the specific, object effects of this, vs what exists with other big co's (G, MS, etc) was explored and better articulated.
1 reply 0 retweets 0 likes -
I'm much less interested in surmising who thought about what & what's "better for OSS" than how this affects us *compared to alternatives*
1 reply 0 retweets 0 likes
One alternative is being less blase about becoming dependent on BigCo software, especially projects that double down on unilateral decisions
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.