Also make sure you call or visit the diggers hotline before you start to make sure you don't hit any buried cables. Not sure about outside the U.S. folks.
what are you talking about? how does that article have anything parodying this statement? i think you misunderstood the statement. what did you think my statement meant?
It's very annoying. To me a while of searching around to find the explore button also, which got grouped into that drop down. Hiding content in drop downs unnecessarily is very annoying.
This would be amazing if companies did this.
Maybe something like this should be encouraged for the monthly who's hiring posts.
I've noticed a few places starting to list salary range and it seems to be well perceived.
Motorcycle exhaust mufflers are commonly made of carbon fibre but it really depends on what you're putting this on and how far down stream from the exhaust it is. I've seen a lot of heat barriers made from carbon on cars and motorcycles. Also hoods are often replaced for carbon in racing and a lot of people have exhaust manifolds directly below them. What usually happens is the carbon gets discolored from the heat but not much worse unless it's directly touching, but that's another can of worms.
Are people always using React with another framework or can you build out full applications with just React? Im looking to start another project and want to try React but not sure if it has everything I'm looking for.
React + Flux in the form of Flummox (along with react-router for routing) is enough for a 10kloc application I recently wrote for Expedia. If you don't want to make architectural decisions or composing smaller libraries then I think Ember is a better choice, but for us React is perfect.
You don't need another framework to build apps with React. But you will need several libraries as React isn't "kitchen sink" type framework like Ember and Angular.
In my React-based apps, I typically include react-router for routing and request or superagent for ajax calls. You can also include a Flux-inspired library if you're into that sort of thing.
The only thing you need is Ajax and you have it right here in the browser without the need of a third party library. All the rest can be handled by React and its plugins.
That's how I do things, React + raw Xml Http requests. Since JSX is already a layer on its own no need to add yet another layer of complexity.
React is the "View", so you need something like Backbone to fuel it. Roll your own, use Backbone, Flux (made by FB especially for React) or Reflux (third party. Flux re-imagined).
I would advise against using Backbone with React/Flux. First, because you don't need it, and secondly, because Backbone is mutable by default, which can cause all sorts of data flow bugs.
Once you buy into the Flux methodology (not necessarily Flux as described by Facebook), a lot of the concerns that Backbone handles melt away. You don't need observable collections and models because all state changes are explicit and data moves in just one direction. Given that Backbone's core is just a thin layer on top of XMLHTTPRequest, you're better off just doing XHR yourself, with POD objects for data.
Just pure react is great for tiny things, but for large applications you should use React with Flux architecture with alt or flummox or reflux or whatever you like, it simplifies things in the long run.
Of course you would need to do things like ajax or routing, for which there are endless libraries, or you can just go pure XHR. React-Router is terrific for routing.
I owned a few before getting into tech. I was a half owner of a limo business. I owned an auto repair shop. I also had a side gig with that doing fabrication for race cars. Later I started making metal furniture in partnership with the cabinet shop next to me. I also invested money I'm a friends motorcycle repair business but cashed out on that and my other businesses to get into the world of software. It was a lot of fun.
I'm that person. For me it's all about cost.
I rent a room in a house in the suburbs for $400mo where if I wanted to live in the city where I work it would cost me around $1k. I don't make a lot of money so even though my time is valuable, it isn't helping my bank account. Until I get a better job it just isn't an option to move into the city.
That's what I meant when I said "despite having options within 5-10 minutes"; I very much meant "viable options within their price range". When you're constrained by cost, you may have to trade time for money.
