> There are a lot of JS tools, but none of them do what we want. We’re trying to coordinate them. We want to provide a good default experience out of the box, so we’re building a CLI to: scaffold, skeleton files, set up build, set up testing environment, possibly even deployment Was there something wrong with the yeoman & grunt/gulp combo? The yeoman tool is great for the scaffolding and skeleton story, and even for…
The problem is that a lot of these js tools that are being built are being built on top of other hobbyist js libraries that are built on top of others that creates this weird chain of dependency that appears to arise from nothing other than the author's coding style preference. Take a look at just one of gulp's dependencies (and arguably one of the most important) vinyl-fs which it uses for file watching. This is the…
React and Angular Meeting
41–50 of 60 posts
Re: React and Angular Meeting
#42Fascinating comment from Christopher Chedeau of React: "The end game isn’t ReactNative. We want the web to win. Would be great for Angular to try to implement on top of our same primitives to see if we could share the work." It's as if ReactNative is being treated (strategically) as a more powerful version of PhoneGap.
If they want the web to win, then why didn't they design ReactNative to have an API that is a subset of HTML (where possible)? With their current API, we can't use the code written for RN on the web.
We actually designed React Native to work on the web. The layout and styles are a strict subset of CSS, the base component such as , and can be easily implemented on-top of , and . The gesture system is written in pure JavaScript as a React event plugin and should work as well.
It's just that it hasn't been a priority so far to exercise this possibility. But, every once in a while we make some example runs on the web. For example, two days ago during a hackathon we made 2048 example run (and work) in the browser by modifying less that 10 files.
> The end game isn’t ReactNative. We want the web to win.
Even though I was one of the few people that started React Native, I --really-- did not want it to exist in the first place. But, the sad truth is that you cannot build high quality, gesture heavy, apps on mobile web today :(
Re: React and Angular Meeting
#43Fascinating comment from Christopher Chedeau of React: "The end game isn’t ReactNative. We want the web to win. Would be great for Angular to try to implement on top of our same primitives to see if we could share the work." It's as if ReactNative is being treated (strategically) as a more powerful version of PhoneGap.
Needless to say I got the message. Don't step on their toes! During the React Native launch video they said, basically, "the web doesn't work for native".
Anyway, I'll continue to port the cool stuff from Native back to Reapp. I don't hold anything against them, in fact it's nice to hear they are actively pursuing bringing stuff from Native back to the web. I look forward to seeing what comes of this.
Re: React and Angular Meeting
#44Earlier quoted context omitted.
The problem is that a lot of these js tools that are being built are being built on top of other hobbyist js libraries that are built on top of others that creates this weird chain of dependency that appears to arise from nothing other than the author's coding style preference. Take a look at just one of gulp's dependencies (and arguably one of the most important) vinyl-fs which it uses for file watching. This is the…
fs.watch actually doesn't work just fine, not sure what gave you that impression. We went with the best file watcher that was around at the time because we didn't feel the need to write our own. The layers of abstraction are there so other people can make use of them as modules. We are (and have been) evaluating other solutions for file watching but gaze is still the best option for us to use under the hood.
I actually had a really interesting conversation with Bert Belder about some of the lower level problem with file watching. It came up that perhaps there could be a working group around fixing this issue.
Re: React and Angular Meeting
#45Earlier quoted context omitted.
If they want the web to win, then why didn't they design ReactNative to have an API that is a subset of HTML (where possible)? With their current API, we can't use the code written for RN on the web.
> With their current API, we can't use the code written for RN on the web. We actually designed React Native to work on the web. The layout and styles are a strict subset of CSS, the base component such as , and can be easily implemented on-top of , and . The gesture system is written in pure JavaScript as a React event plugin and should work as well. It's just that it hasn't been a priority so far to exercise this p…
We really do care about the web, and before very long we will be able to build great apps for web and on native, with a lot of code re-use. (And if you're willing to hack it, then you can do that today!)
Re: React and Angular Meeting
#46Fascinating comment from Christopher Chedeau of React: "The end game isn’t ReactNative. We want the web to win. Would be great for Angular to try to implement on top of our same primitives to see if we could share the work." It's as if ReactNative is being treated (strategically) as a more powerful version of PhoneGap.
That's interesting. I made and launched Reapp a couple months ago and one thing I noticed was the absence of any support from the React team. Not a single retweet from the React account (who are very active at supporting community projects), not a single React team dev commented on it. I had to ask them for some love, so in response they favorited a tweet of mine.. Meanwhile the same day react-canvas launched and nea…
I don't think this was intentional, and I'm sorry if it came off that way. We've certainly pointed people interested in building mobile apps at TouchstoneJS and I'll point people at Reapp too now that I know about it – obviously React Native isn't appropriate in all situations. Will try to keep an eye out and retweet some stuff of yours in the future.
Re: React and Angular Meeting
#47Re: React and Angular Meeting
#48Fascinating comment from Christopher Chedeau of React: "The end game isn’t ReactNative. We want the web to win. Would be great for Angular to try to implement on top of our same primitives to see if we could share the work." It's as if ReactNative is being treated (strategically) as a more powerful version of PhoneGap.
That's interesting. I made and launched Reapp a couple months ago and one thing I noticed was the absence of any support from the React team. Not a single retweet from the React account (who are very active at supporting community projects), not a single React team dev commented on it. I had to ask them for some love, so in response they favorited a tweet of mine.. Meanwhile the same day react-canvas launched and nea…
Not trying to just back them for no reason, but I'm happy with what they are giving the community.
Re: React and Angular Meeting
#49If Facebook would agree on using standard Typescript, instead of their own thing, that would be amazing.
Re: React and Angular Meeting
#50Earlier quoted context omitted.
That's interesting. I made and launched Reapp a couple months ago and one thing I noticed was the absence of any support from the React team. Not a single retweet from the React account (who are very active at supporting community projects), not a single React team dev commented on it. I had to ask them for some love, so in response they favorited a tweet of mine.. Meanwhile the same day react-canvas launched and nea…
I think this is more of a product of staying focused on what they need to work on. I would have been surprised if they did actively help you guys enhance Reapp. I mean just by open sourcing react native they are making huge contributions. Not trying to just back them for no reason, but I'm happy with what they are giving the community.
I love React and their team, and am incredibly positive on the future of what FB is doing.