Earlier quoted context omitted.
> In my opinion most of the Great Javascript Fatigue of 2015-16 was caused by users trying to fill in the blanks left by the React team and producing one solution after another (and quickly abandoning ship as something iteratively better was released). I agree wholeheartedly with this. And it's also why I love Ember, you get templates, routing, data access all working together with minimal configuration. I love Djang…
I found Ember was much harder to get started with than React. More concepts, it's own CLI and build system, outdated docs. (I used it 2 years ago)
Create React Apps with No Configuration
171–180 of 250 posts
Re: Create React Apps with No Configuration
#172My team has wasted so much time configuring webpack. This is a big win for React IMO.
This right here is why I actively suggest not using webpack. It's Grunt 2.0 all over again and not worth the mess. IMO it's the worst choice Facebook could have made for this toolkit, as it breeds some awful habits.
Re: Create React Apps with No Configuration
#173> Having just attended EmberCamp a week ago, I was excited about Ember CLI. Ember users have a great “getting started” experience thanks to a curated set of tools united under a single command-line interface. This is one of the best things about Ember. `ember new`, `ember serve`, ember generate component my-component`, `ember build`, `ember deploy`, `ember install`. It's opinionated but it lets you get productive rig…
Kind of interesting to think about the two projects and how they diverge based on the core developers. Ember is made by folks who work on / for small and medium companies[1]. They don't have the build infrastructure Facebook does and are able to create an anointed solution in Ember-CLI because they'll use it daily. React is stuck in a place where the environment it's developed in is unique from what any other user wi…
To clarify, I like old and boring because it generates less JavaScript fatigue.
Re: Create React Apps with No Configuration
#174Earlier quoted context omitted.
I found Ember was much harder to get started with than React. More concepts, it's own CLI and build system, outdated docs. (I used it 2 years ago)
2 years ago is decades in the front-end world. If we make decisions today based on the state of things years ago, we'd be screwed.
And if we CAN'T "make decisions today based on the state of things years ago", then we're really screwed.
Re: Create React Apps with No Configuration
#175Earlier quoted context omitted.
Lol. No, I still fully agree. We think React is a tool to create great UIs, and UIs definitely include concerns like data fetching, etc. So some of this might make it into React in some form in the future.
In the meantime, you can also try out the official Flux library from Facebook ( https://github.com/facebook/flux ), or Redux ( https://github.com/reactjs/redux ), which offer great solutions for data manipulation and storage
(The guy you're responding to is the creator of Redux) :-)
Re: Create React Apps with No Configuration
#176Re: Create React Apps with No Configuration
#177This is lacking tons of features that other boilerplates already have but I think this was a great move because we needed a source of truth for doing app structure in React. In a different note, I think if you write it yourself from scratch you'll have more control and knowledge down the road when it comes to nasty bugs but I won't blame you for choosing this over spending weeks setting up a React app.
If you work with React a lot, you can setup a React project to your taste in about 30 minutes. But the catch being if you leave React for a while then come back, all bets are off. I think most boilerplates add way too much and are overly opinionated. I like that this is simple, and "eject" gives power users an even better starting point.
React Starter Kit comes with GraphQL as its API layer. I love GraphQL, and have written tons of it when writing Relay code, but I wouldn't ever expect someone getting up to speed on React to use it.
You have to limit the number of things you throw at newcomers.
Re: Create React Apps with No Configuration
#178Earlier quoted context omitted.
Kind of interesting to think about the two projects and how they diverge based on the core developers. Ember is made by folks who work on / for small and medium companies[1]. They don't have the build infrastructure Facebook does and are able to create an anointed solution in Ember-CLI because they'll use it daily. React is stuck in a place where the environment it's developed in is unique from what any other user wi…
I suppose that's the price people will pay for needing the latest shiny (React) instead of the now old and boring Ember or AngularJs. And also thinking that the solution that works for Facebook is the one that is the best fit for a small startup, because someday they will reach Facebook's size. To clarify, I like old and boring because it generates less JavaScript fatigue.
I know the cool thing amongst us older folk are to say "Oh there goes them darn ole kids chasing their new toys again" but this is a case where very clearly one is much more suited for the job than the other. There's nothing wrong with a winner emerging. All of the "problems" people gripe about here about React can be avoided. I have posted this before, but I'll post it here again -- You wouldn't go to learn how to program Java by first learning how to configure maven, download dependencies, set up your project in an IDE, and then build and deploy your WAR through Jenkins into a J2EE container for "Hello World"
React has all the goodies provided by the community, but React IS just a library. If you want to learn React -- copy and paste the latest CDN, use the in-browser transformer, and freaking learn react. The tutorials are great, and so is the article "Thinking in react"
In any case, I haven't looked at this CLI, but if it's anything like the ember-cli I am sure it will help with the artificial gripes.
Re: Create React Apps with No Configuration
#179Earlier quoted context omitted.
In the meantime, you can also try out the official Flux library from Facebook ( https://github.com/facebook/flux ), or Redux ( https://github.com/reactjs/redux ), which offer great solutions for data manipulation and storage
I think he knows about those two options. (The guy you're responding to is the creator of Redux) :-)
Re: Create React Apps with No Configuration
#180Earlier quoted context omitted.
I suppose that's the price people will pay for needing the latest shiny (React) instead of the now old and boring Ember or AngularJs. And also thinking that the solution that works for Facebook is the one that is the best fit for a small startup, because someday they will reach Facebook's size. To clarify, I like old and boring because it generates less JavaScript fatigue.
You don't think a legacy AngularJS project is full of "fatigue"? I shudder at the thought. Angular 1 is so awful, even the creator himself, Misko said it really wasn't intended to be used in this way. I know the cool thing amongst us older folk are to say "Oh there goes them darn ole kids chasing their new toys again" but this is a case where very clearly one is much more suited for the job than the other. There's no…
That's not really fair, though. It will be a React + x + y + z project, because as you said, React is just a library, and it needs other pieces to fill the gaps provided by some of these other frameworks.
I could be wrong, but it will take a couple years to tell. By then, React will be old news also.