111–120 of 120 posts
Earlier quoted context omitted.
You don't need all of that from scratch. You can just build React components, and when it comes time to add a store or a router the only thing you need to change are the glue components that bind things together. I think it works out nicely -- the dev process is as composable as the app itself.
Yea I've noticed that. The react community likes to focus on examples involving a sign up form with 3 fields where you "really don't need all of that". Except that is not what most of us SPA devs are building. We need most of that.
Or you don't need all of that.
It's very, very rarely a different situation.
Earlier quoted context omitted.
having the option to precompile your framework to 20kb file size which is smaller than some libraries feels like a great feature
20kb? Really? On last week I built NG2 application(rc.4) with one component and size was over 500kb, with all dependencies which needed to run it. Maybe @angular/core weight 20kb, but in order to run real world application need add many dependencies. rxjs, zoom.js, shims, and so on..
Earlier quoted context omitted.
If it's an internal app or if it otherwise doesn't need to be single-page-app, save yourself some brain cells and do something simple like Rails or Django. If JavaScript is absolutely required, stick with Sails/Mongo and skip the Ember/Angular SPA.
How does that help with a rich front-end? We're not looking to use JavaScript simply for the sake of using JavaScript. We want it in particular for a richer front-end. As far as I can tell, Sails isn't going to help with that any more than Rails does. That's why we're looking into Ember or Angular.
Earlier quoted context omitted.
How does that help with a rich front-end? We're not looking to use JavaScript simply for the sake of using JavaScript. We want it in particular for a richer front-end. As far as I can tell, Sails isn't going to help with that any more than Rails does. That's why we're looking into Ember or Angular.
What is reach front end? The one where you wait your js to arrive only for it to issue own API calls, then wait data to arrive, then it to be parsed and finaly shown? It would not surprise my if some dumb turbolinks staff would beat a lot of fancy frameworks performance an UX wise.
No, that's your own straw man definition.
> It would not surprise my if some dumb turbolinks staff would beat a lot of fancy frameworks performance an UX wise.
Turbolinks absolutely does not beat a well written SPA UX-wise.
Earlier quoted context omitted.
I wonder where the happy medium is. Setting up React/Redux/React-redux/react-router/react-redux-router/react-redux-router-thunk/webpack-hot-module-oh-my-god-what-am-i-doing takes forever.
Honestly, the fact that people put up with this in Js ecosystem amazes me to no end. I've been working with ClojureScript on the front-end for the past year, and it's just night and day. There's a single build tool ( http://leiningen.org/ ), and it manages dependencies, tests, builds, etc. Things just work. Setting up a new project is as simple as: lein new reagent-frontend myapp I can go and start developing it by r…
Earlier quoted context omitted.
Angular for job opportunities, react for more pleasant and forward looking web development practices.
Er.. https://github.com/angular/angular-cli 1. Open terminal 2. > npm install -g angular-cli > ng new app > ng serve 4. Use the cli tool to generate components/pipes/services/etc., build, test, develop 5. Profit. Find a more blissful and joyful experience than this in react land?
Earlier quoted context omitted.
I wonder where the happy medium is. Setting up React/Redux/React-redux/react-router/react-redux-router/react-redux-router-thunk/webpack-hot-module-oh-my-god-what-am-i-doing takes forever.
Honestly, the fact that people put up with this in Js ecosystem amazes me to no end. I've been working with ClojureScript on the front-end for the past year, and it's just night and day. There's a single build tool ( http://leiningen.org/ ), and it manages dependencies, tests, builds, etc. Things just work. Setting up a new project is as simple as: lein new reagent-frontend myapp I can go and start developing it by r…
npm i -g create-react-app
create-react-app my-app
cd my-app
npm start # start devserver
npm run build # build for productionEarlier quoted context omitted.
Honestly, the fact that people put up with this in Js ecosystem amazes me to no end. I've been working with ClojureScript on the front-end for the past year, and it's just night and day. There's a single build tool ( http://leiningen.org/ ), and it manages dependencies, tests, builds, etc. Things just work. Setting up a new project is as simple as: lein new reagent-frontend myapp I can go and start developing it by r…
CLJS is just a language.
Earlier quoted context omitted.
Honestly, the fact that people put up with this in Js ecosystem amazes me to no end. I've been working with ClojureScript on the front-end for the past year, and it's just night and day. There's a single build tool ( http://leiningen.org/ ), and it manages dependencies, tests, builds, etc. Things just work. Setting up a new project is as simple as: lein new reagent-frontend myapp I can go and start developing it by r…
This is pretty much what we’re doing with Create React App. npm i -g create-react-app create-react-app my-app cd my-app npm start # start devserver npm run build # build for production