If I'm on vacation, I'm not looking to save every single dime because I know that it's a one-off expense.
If I'm looking for an apartment, I'll actively research to find the best deal because it's a long term commitment that could have huge ramifications on my finances years in the future.
Case in point:
I'd gladly pay $250 a night in a Manhattan hotel, because fuck it, I'm going on vacation, will only be there a few days, and don't want to spend an hour each day on the train getting to/from Newark just to save a couple hundred bucks.
But I would have to be crazy to pay $250 a night for an equivalent (i.e. studio) apartment in Manhattan, regardless of how much time it cuts off of my commute.
It looks like Subscribe's `to` prop expects an array. So, `[CounterContainer]` is just an array with a CounterContainer in it.
The `{ }` that wrap it are just part of the syntax of passing props. If you wanted to pass an object literal to a prop, you'd have to double-up the curly braces:
<div style={{ color: 'white' }} />
And strings can be passed with or without curly braces:
// both of these are fine:
<div id='foo' />
<div id={'foo'} />
Also keep track of every time that you see references to each topic both before and after bringing them up.
And have a control group that you simply don't bring up at all. Make sure to have more than one, so that you still have more remaining if someone around you brings up one of your control topics.
As my driving instructor used to say, "Stop signs and red lights do not actually reach out and stop the other driver."
The lesson: just because it's your turn to go does not mean that others will not enter the intersection when it's not their turn. I agree that rolling stops at a 4-way stop are generally safe when you can clearly see that no other cars are at or approaching the intersection. But in my experience, the fact that the other person is at fault has been little consolation for having to deal with a totaled car and a permanent backache.
Right, so the reward/risk isn't enough for you. It's also prudent to stop at a green and look both ways but nobody does this either.
At the end of the day you either trust other drivers or you don't. You're not exposing yourself to any significant addional risk by making these 'safe violations' than you do driving in general.
But in some sense you do, because you don't come to a dead stop at every intersection, even when it's green. And it's a bitter pill to swallow, but no amount of defensive driving can make you totally safe. Getting rear-ended sucks.
Sure, but you can take some relatively easy actions to significantly reduce your chance of injury by a crazy driver. I don't come to a stop at green lights, but I do glance both ways to see if there's oncoming traffic. Occasionally there is: I've seen people blatantly run red lights.
OK, obviously that's true. But if it's empty, you have good visibility, and you plainly have the right of way, well, I'm just going to take it on faith that nobody is hurtling down the road at 80 mph. You can't possibly account for everything; that's the risk of driving.
My thought would be that it would be at the source level. "98% of people find this source reliable", though that's certainly subject to the same biases.
Better systems might require more work to mark a story as false (such as how reporting a story as false currently works in Facebook.) Over time, Facebook can see on their end which domains are pushing fake news and choose not to surface unreliable sources on people's news feeds.
That idea is also vulnerable. Conservatives will just flag off stories from MSNBC, liberals will just flag off stories from Brietbart, the truth of the actual article notwithstanding.
Is `xmlns` actually required? We've pulled it out of all of our React svg's and everything seems to work fine. Does anyone know of any quirks this could be causing?
If I'm on vacation, I'm not looking to save every single dime because I know that it's a one-off expense.
If I'm looking for an apartment, I'll actively research to find the best deal because it's a long term commitment that could have huge ramifications on my finances years in the future.
Case in point:
I'd gladly pay $250 a night in a Manhattan hotel, because fuck it, I'm going on vacation, will only be there a few days, and don't want to spend an hour each day on the train getting to/from Newark just to save a couple hundred bucks.
But I would have to be crazy to pay $250 a night for an equivalent (i.e. studio) apartment in Manhattan, regardless of how much time it cuts off of my commute.