> Then you should be in favor of increasing biking infrastructure so that you're much less likely to make a mistake involving a bicyclist.
Of course i am. Not sure what made anyone think i'm not in favor of it.
Guess opinions are bad-form around this place :P
> As a driver, it is your responsibility to manage a two-thousand-pound weapon responsibly. As you have the most power to cause harm, you also have the most responsibility to prevent it. The biggest problem with vehicles in the US is that you're "entitled" to drive without learning how dangerous you are to everyone around you, and how to navigate that danger safely.
You seem to think my post was entitled, it's not. It's my opinion that i don't like them. I also do not like pedestrians jaywalking, but that doesn't mean i'm entitled. I would prefer to reduce risk by means that this article lays out.
I don't like things that increase risk. Bikers in my lane, infront of my "two-thousand-pound weapon" simply increase risk. It's like gun safety. I don't put my finger on the trigger until i'm ready to fire.
You (and i assume the downvoters?) seem to think that just because i express my opinion, that i would attempt to ban bikers from the roads completely. Far from it.
> I see more people driving break the law every day while driving then I've ever seen bikers do in my entire life. People are jerks regardless of what they use to commute with.
I don't think he (or many) would claim otherwise. The issue isn't the people who ride bikes, but rather the mode they choose to travel with and the impact it has on your drive. Bikers cause all sorts of added danger to both themselves, and you as a driver.
If you have a moment of human error in car-v-car, you're very likely to have both parties walk away from the incident. You call your insurance(s), your rates go up a bit, and your life moves on. Accidents are very, very common.
Repeat this same scenario in car-v-biker, and the odds quickly swing towards it being a life endangering accident. It's just a step away from hitting a pedestrian.
I don't dislike bikers because they slow me down or anything like that. I dislike them because of the likely increase in severity for almost all car-v-biker accidents.
edit: Interesting, seems i am getting downvotes for my opinion. Care to explain your thoughts? I can't imagine you (downvoters) feel that car-v-biker is an equal risk compared to car-v-car, do you?
Yea, i really thought that this stuff should be out of dockerland. Not that i dislike the feature, just that it seems to overlap with established tools that excel at doing one thing well.
Well, as unhelpful as this.. I love everything about Polymer, except the possible HTTP request spam and lack of serverside rendering.
Polymer is sort of React Components "To the extreme" (to me). They represent everything i love about React Components, with encapsulated JS, CSS, and HTML. Meaning that i can pull in someone elses Polymer component, or use one from another project, and it "just works".
Granted, the HTTP spam scares the hell out of me. Vulcanize may help with that, but i have yet to really figure out the whole process for my workflows.
Having to load an html wrapper, do clientside routing, load the data into the clientside templates and render templates all for the first page load just scares me with Polymer. React solves this by letting me do it all serverside, and it is wonderful at that.
I really do love React. I'll likely stick with React for another project or two, unless i conceptually have an "ah hah" moment with Polymer.. but until i can render Polymer serverside, i'll always be longing for React.
edit: Come to think of it.. If someone could bake html imports and shadow dom into React, i may be in heaven.
It's something i've been struggling with quite a bit. Conceptually i love Polymer, and really want to switch, but React's serverside rendering is just hard to beat. I'm scared of showing users page load spinners while my 20 Polymer components all load their data heh
Fwiw, i use serverside React rendering with a Golang API server. My JS code has an interface layer which interfaces to browser/node, and on first load a balancer throws the request to Node, which makes local API calls to the api server, and renders it all in node.
Technically i use Node, but only to implement a small interface layer for things like http requests. So i don't really consider it a Node app. The real code is all React and Golang.
I would want to rotate simply to get more resolution.. but then i'd wonder why i wasn't using the highest resolution from the start.. and then bam, i'm back to using the a normal camera app and holding it sidebars haha.
Though, i think i'd prefer this style app if it just picked portrait or landscape, and adjusted between just those two states dynamically. That would be nice if you accidentally shoot in one, and decided you wanted the other. Which happens quite frequently for me.
I'm quite happy to see this, from a Google Music user perspective.
I was getting quite antsy with the lack of music related features. Google Music was feeling so.. lacking. I was close to switching back to Spotify, or trying something new.
Glad to see something is still being worked on heh
Possibly. At any rate, the loss/gain of Soylent is all about the type of person you are. I don't expect someone who doesn't see the appeal/desire of Soylent, to enjoy drinking it.. Rob didn't intend for that.. it's supposed to be cheap, neutral, and healthy. Nothing more, nothing less.
With that said, i'm super excited for it, and i've been drinking DIY "Soylent" for a few days now, since i'm getting impatient waiting for official soylent, and i couldn't be happier. It's everything i wanted. Once the official stuff gets here, i'll spend even less time preparing, and in theory it will taste better too (mainly less grit).
Not to mention i've been dying for this type of product for a long time, and have not been aware of a meal replacement shake that is intended for this level of consumption.
People can argue the health implications all they want, but to argue that this isn't anything new.. well, maybe i'm missing something, but it's quite new to me.
Considering that i've been wanting this product for the last 15 years - I'd say at the very least the others (whatever they may be) were a marketing failure.
I feel like applications and tooling to pre-render your HTML (eg: Reactjs) are more interesting. It's definitely more work currently (when done right), but it seems like the most natural flow. Always render html, let clientside link it up, everybody wins.