> ...but i dont really think it has a large cultural impact. aside from trump this election cycle i feel most 'famous' tweets are about as significant as here come dat boi.
That's absurd. I've seen numerous articles in online entertainment media sites (e.g. People, US Mag, TMZ, Buzzfeed) that are solely made up of embedded tweets. CNN and MSNBC (and even Fox News) reference tweets all the time. Maybe Twitter as a company has failed to monetize the platform properly and shareholders have taken a loss but to downplay Twitter's cultural impact seems largely misguided.
Not trying to defend anyone here but I think you're making the wrong comparison. React (the library) isn't changing. Just like Elixir, JavaScript (the language) is changing for the better and almost everything is backward compatible. What folks are upset with here is react-router, an optional, third party routing library dependent on React. Authors should be allowed to improve their own projects otherwise they become stagnant as the libraries and languages they depend on evolve. It's why semver exists.
Much of React-Routers problems can be traced to the fact that it uses React components as its API. Yes, there's an alternative API in v3, but it doesn't seem to be very well thought through and is hardly ever used in examples.
Another issue with React-Router is that fundamentally in a web-based system, the router is the core of your framework (middleware, hand-offs to controllers/views, etc. are all built around the abstraction that the router sets up). With React-Router embracign React Components as their API, it means that your entire application must be built to the same abstraction---entirely within the React system, with components nesting other components.
I feel the problem of making a large javascript application client-side is best dealt with by keeping React as the view only, and putting everything else (router, dispatcher, models, etc.) in the form of another abstraction and not defaulting to component based architecture because that's simply what React does.
I agree. I don't necessarily want my routes to be declared in react. I'm currently looking into using router5 (https://github.com/router5/router5). The library also has integration plugins for react and redux.
Also, check out https://medium.com/@mweststrate/how-to-decouple-state-and-ui.... Michael Westrate talks about using your state container to control routing, instead of letting the components do it then syncing current route to state container. He is the author of mobx and uses it in his example, but I imagine it would work for redux scenarios too.
It came at a great time, in that it really crystallised some ideas I had been having about the friction of using React-Router. So I buckled down and wrote my own router component with HistoryJS & Crossroads.
Why would you actively avoid every political discussion? The reality is politics affects many aspects of our lives especially with more and more legislation affecting the very technology we work with on a daily basis. Having a rational conversation and listening to other views can help move discussion forward and broaden awareness.
Thanks for that, at least it's something. John Clay is listed here[1] as a contributor to "Website maintenance and troubleshooting, Mac OS X help documentation". I wish they would post a similar update on their website and explicitly confirm that the current source and binaries have been audited and are safe.
After working on a few large JS applications (using Backbone or Angular or React), I decided to try out Ember for a relatively smaller application.
Ember feels very Rails-y (likely on purpose) and the documentation wasn't great. It took me a few hours to get a surface level understanding of how things worked with each other, especially Ember Data. I ultimately ended up dropping it because of my frustration. It was only a couple months ago (early December 2015).
Obviously I'm just one data point but I know I've talked to other devs who feel the same way. I'm sure Ember will only get better but I don't think it's the antidote at all.
Fast and beautiful flowers at affordable prices. We're growing and need a highly skilled JavaScript (Node) developer to come help us build stuff quicker. Our backend is almost fully powered by Node. The position requires someone who can adapt and thrive under pressure. Some of the backend is being moved to micro-services but we're not planning to go overboard with it. You'll be the third engineer (joining me and another person) and employee #15 so you'll have a huge impact on not only the tech but the company itself. We're passionate about making our customers happy and know that our tech plays a big part of that process. Come join us!
Most of the work requires backend knowledge:
* JavaScript (NodeJS) application development
* Postgres, Redis
* API development
* nginx/AWS/DevOps (some base knowledge, at the very least)
This is not a front-end position. Please email me at chetan@urbanstems.com. I definitely value seeing your past work over a standard resume but feel free to send it along.
We're growing and need a highly skilled JavaScript (Node) developer to come help us build stuff quicker. Our backend is almost fully powered by Node. The position requires someone who can adapt and thrive under pressure. Some of the backend is being moved to micro-services but we're not planning to go overboard with it. You'll be the third engineer (joining me and another person) and employee #15 so you'll have a huge impact on not only the tech but the company itself. We're passionate about making our customers happy and know that our tech plays a big part of that process. Come join us!
Most of the work requires backend knowledge:
* JavaScript (we're slowly moving the codebase over to ES6), Node/io
* Postgres, Redis
* API development
* nginx/AWS/DevOps (some base knowledge, at the very least)
* Would be awesome if you know front-end dev (Backbone, React, moving to Flux-like arch soon). Not necessary though so don't fret.
Please email me at chetan@urbanstems.com. I definitely value seeing your past work over a standard resume but feel free to send it along.
