[wayneftw]

Facebook is a steward not a dependency. React has been free and open source and largely driven by the needs of the community. Right down to that time when the community cried out about Facebook's odd license clause regarding patents. And they changed it.

But I can't imagine modern technology being where it is without big shifts. Perhaps that is not good for very long term projects. We'll see how Vue fairs in the long run if they never make any big shifts, I suppose.

Then again, none of the big shifts in React broke anything permanently, did they? I could be wrong about this, I haven't been paying attention since the very beginning…

[rk06]

> Right down to that time when the community cried out about Facebook's odd license clause regarding patents. And they changed it.

Looks like you are remembering things differently. Facebook doubled down on public outcry and even react maintainers gave up on it.

Then wordpress chose to stop its adoption of react in its new editor. And that caused Facebook to change the licence.

The fact a big org was needed for this change, is a major factor for Facebook's distrust.

[wayneftw]

The WordPress group isn't part of the community? That it's a big org is a distinction you're making, not me. Open source communities are full of big organizations.

And now that the genie is out of the bottle anyone can do as they please with this fairly small rendering library and Facebook can't stop them. So I'm still not sure what the concern about Facebook is?

[rk06]

The problem was that:

1. They chose to insert the clause and refused to use standard MIT license despite complaints from community and their own developers

2. They are the kind of company who chose to do shady stuff despite complaints from community and their own developers

#1 was fixed. #2 is still the case and may come to bite back in future. That is the concern

[wayneftw]

So, nothing more than ambiguous conjecture? Got it.

Well, I'm pretty happy using it and I certainly don't lose any sleep over Facebook having built it. Quite the opposite - I thank them for it! Nobody can take away my rights to freely available MIT licensed code.

[porker]

> We'll see how Vue fairs in the long run if they never make any big shifts, I suppose.

Vue 2 to Vue 3 has felt like a big shift. Big enough to leave most libraries incompatible with Vue3 and a lot of community forks spread around while library authors work out how (and if) to support both versions.

Vue 3 is an improvement to work with IMO but it's a rewrite your code kind of upgrade.

[midrus]

The Vue 2 to 3 sounds very familiar to me to what happened with python 2 to 3 transition.

[gentleman11]

Angularjs didn’t really stick around after google moved on to angular 2, despite being open source. People who still wanted a similar workflow switched to vue. I think that’s the concern

[cout]

There's plenty of angularjs still around, for projects that can't or don't want to move to angular 2. The official end-of-life keeps getting pushed back, and I won't be surprised if someone r eventually forks it.

[ducharmdev]

Wow, had no idea AngularJS hadn't hit it's EOL yet

[worker767424]

Compare this to HHVM which evolved into a PHP fork no one other than Slack uses.