61–70 of 124 posts
Earlier quoted context omitted.
What's the next JavaScript framework for non-web mobile apps though?
Oh, it's 2018, nobody uses React Native anymore. We're using Weex [1] or NativeScript [2] now. [1] https://weex.incubator.apache.org/ [2] https://www.nativescript.org/
Neat! Yoga is a great library, I wrote Rust bindings for it: https://github.com/bschwind/yoga-rs?files=1 I eventually want a React Native esque framework but written in Rust instead of JS. Still a ways away though, I don't have much time to work on it.
Earlier quoted context omitted.
Of course it hurt their software adoption rate. You have very public spats by wordpress and apache over this. Think of people who couldn't convince their boss to use react / react-native because the legal department saw that PATENTS file and said NO WAY. I think they are making these moves because they see that they are going to be in a weaker position in the future and need to open their grip on these projects to ma…
The irony being that the Apache license has an identical clause.
I thought it was a good thing personally because patent lawsuits are a waste of everyone's time but apparently enough people disagree.
Not that I know anything. Sorry for rambling. Point is I want to ask the question: are they (practically) identical?
Earlier quoted context omitted.
> Its probably too late though and people are moving off of it to the next javascript framework. But is there a viable alternative with the same level of features and ecosystem momentum? GraphQL and React Native, in particular, seem well positioned to dominate their respective niches. That gives React a big advantage, which might counteract the licensing issues, no?
If that were true then why are they changing the licence at all? They have tooling and are well positioned but what they need is big players to also back them so that people are more incentive to buy in. That is where moving the licence to MIT makes sense.
Earlier quoted context omitted.
If that were true then why are they changing the licence at all? They have tooling and are well positioned but what they need is big players to also back them so that people are more incentive to buy in. That is where moving the licence to MIT makes sense.
To buy in for what? If literally everybody apart Facebook stops using React, the project will still go on because it powers a shitload of FB properties.
Prediction - there will be a Harvard Business Review about Facebook's adventure with licensing. My unproven hypothesis is that they hurt their software's adoption rate because of their licensing. Personally, I believe MIT is correct. I had moved my company away from React when they had the licensing problems. To me, it feels like they are coming back to the community now.
Of course it hurt their software adoption rate. You have very public spats by wordpress and apache over this. Think of people who couldn't convince their boss to use react / react-native because the legal department saw that PATENTS file and said NO WAY. I think they are making these moves because they see that they are going to be in a weaker position in the future and need to open their grip on these projects to ma…
It's ironic how one can hold utmost respect for Facebook's libraries, but be vehemently against the actual Facebook web application and their business practices.
It's not at all different from loving music written by drug addicts whom you wouldn't want as friends. Software developers are people too.
Earlier quoted context omitted.
Of course it hurt their software adoption rate. You have very public spats by wordpress and apache over this. Think of people who couldn't convince their boss to use react / react-native because the legal department saw that PATENTS file and said NO WAY. I think they are making these moves because they see that they are going to be in a weaker position in the future and need to open their grip on these projects to ma…
Actually we just thought it was a shame that people wouldn’t use it because of the license. Not much more complicated than that.
Earlier quoted context omitted.
Of course it hurt their software adoption rate. You have very public spats by wordpress and apache over this. Think of people who couldn't convince their boss to use react / react-native because the legal department saw that PATENTS file and said NO WAY. I think they are making these moves because they see that they are going to be in a weaker position in the future and need to open their grip on these projects to ma…
And what is this next JavaScript framework?
I'm not surprised, React Native doesn't work nearly as well as you'd think. This is basically a piece of software you'd have to give away (IMHO).
Exact opposite experience. After being a mobile dev for 8+ years and making all of my most recent apps in RN, including a rewrite of one that was many years old, you're wasting your time if you still write native code instead of RN. It's just better in every single way and is an incredibly impressive, stable piece of technology.