devrelm

Uh, yes? Clearly?

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'} />

They released inward-facing video of the safety driver shortly after the incident.

The driver was staring at her phone in her lap with only occasional glances at the road every 5 seconds or so. I would call that pretty negligent.

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.

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.

To be fair, the primary reason that my wife and I don't use Allo is because it was never available on the web.

EDIT: And now after signing in, I realized that what I /really/ need is a desktop app...

Looking at "paths", shouldn't those @types (history, redux & react) be picked up automatically, at least as of TypeScript 2.0?

Also:

  "*": [ "./ClientApp/types/*", "*" ]

I like that. I may have to add it to my app and get rid of our typings.d.ts (currently included through "files") once and for all.

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?

This one isn't actually /too/ complicated. It certainly uses some advanced techniques -- transitions, clip-paths, nth-child -- and I'm not sure (haven't checked) if or how it works in browsers other than Chrome, but the fact that you _know_ you'll have 30 shards greatly simplifies everything.

If you can have a designer draw up the basic design, then you can one-by-one take the shards & put them into place with CSS. From there you can set up some animations on specific shards to make it seem like everything's moving together. From there, you basically have one animal. It'd be time-consuming, but would work.

The css selector for a particular animal's shards start with a `.<animal>` class selector, so that you change the animal class in a parent and all the shards move into place.

It looks like they're still using some javascript to set "states", which seem to trigger animations. I'm honestly not sure why they decided to do that rather than just using keyframes with animations, though I imagine that it may have been that animations were firing before the transition between animals finished, which would have caused a little bit of weirdness.

I love woodworking as well, and have completed a few little projects since buying a house and finally having a garage/workshop.

But, if that's not something you have the space/money for yet, I think that cooking is a nice substitute hobby. There's a lot to learn with tools and technique, and you get the immediate satisfaction of seeing (and tasting!) your finished product.

Just be careful though -- I've injured myself many more times in the kitchen than in the garage.

Right. I actually wonder how self-driving Semis will handle such a situation.

Given that it's all math at that point, I wouldn't doubt if regulations surrounding minimum yellow-light timing are updated to more accurately represent the stop time of heavy loads. Otherwise it should be easy to prove in court that stopping in time would be impossible given the speed limit & weight restrictions (or lack thereof) in place at a given intersection.

Yeah, I work every day in New York. I have no idea what this guy is talking about.