I don't remember the details, but in one of the recent updates they increased the performance at top speed and initial start (below 3 mph). Prior to that, 85D and 90D (all-wheel drive configuration) got a significant boost to its 0-60 performance via a software update.

Since all the hardware is controlled via a software firmware, they are able to tweak the voltage supply of each motor to decrease or increase output performance.

Congrats Travis, Peter and everyone from Continuum Analytics!

Thanks, Sahat! Hope all is well with you!

If you own a Tesla Model S and live near a supercharger network, charging is not an issue. Over 8,000 miles in my Model S, all powered exclusively by the superchargers, free of charge.

Note: I live in an apartment less than 2 miles from the nearest supercharger in Los Angeles and only 8 miles from work. So, the range is never a problem.

Tesla Superchargers are not the solution for this, as they are simply not designed for such use. They were built to help with long range destinations.

There are cases where users, (ab)using them as you do, got a request to reduce their usage. I guess you didn't trigger any flags.

That was my initial reaction as well. Pretty interesting concept. Front page Hacker News web traffic to your website in real-time.

I totally dig it too, but I wish it counted without highlighting yellow. Neat feature, but a bit distracting.

This is an implementation of socket.io, right?

Seems to hold up pretty well.

Meh, mixins are anti-pattern and I am glad they are finally gone. In my experience mixins just make your code hard to read.

I never understood this line of reasoning. Isn't composition over inheritance a valid principle, especially in JS land?

Speaking more to the anti-pattern part of your comment, obviously whether or not you think they are hard to read is subjective.

Agreed 100%.

I find inheritance much harder to reason about or even read. Mixins don't always lead to the clearest code, but they're better than all the alternatives.

I don't think that avoiding mixins implies inheritance. The more common pattern, at least in React, is "higher-order" or "wrapper" components where the responsibility for managing the mixin's behavior is moved into a separate, composable component.

The main issue with mixins is that the origin of behavior becomes opaque. If I call this.mixinFunction(), it's not defined in my file or imported directly, so I have to know exactly which functions come from which mixins. With higher-order components, you can just look at the props and know where things originated.

I'm not a staunch defender of any particular approach, but I think that's the main argument against mixins. (And it applies to other languages as well, such as Ruby.)

Mmm, not sure I see a huge difference between:

    import Foo from './foo';
    let Bar == React.createClass({});
    Bar = Foo(Bar);
    Bar.mixinFunction();

and:

    import Foo from './foo';
    let Bar == React.crateClass({mixins: Foo});
    Bar.mixinFunction();

In both cases I'm adding functions to my Bar component; in neither case is it defined in my file or added directly.

It is true that in the general case the mixin approach would mutate the internal state of Bar, whereas the higher-order component approach would re-render Bar with updated props, which is a solid win for the latter style. (Conversely, a mixin can check the state of the underlying component, while a higher-order component cannot, which means that you can't really implement shouldComponentUpdate as a higher-order component.)

But it's really a fairly subtle difference, and I wouldn't say that either is particularly more transparent. :)

I actually commute every day via 405 and 10. You are right, it's awful during the rush hour, but during non-rush hours it is still faster than taking local streets. A few weeks ago I left work via 405 at 4:45pm and arrived home at 7:10pm, the commute that would take no more than 12-15 minutes without traffic.

You've never been tempted to bicycle that short a distance? Sure it wouldn't be 15 minutes but it also wouldn't be 2.5 hours.

I ditched my car for a bicycle, and I've never been happier. Except when I almost get hit by a car. But that's mostly rare. Mostly.

I'm not sure I'd want to do that as it gets quite hot in LA.

Not true. LA has some of the best weather in the world.

I agree with you but temp varies greatly. It often is 30 degrees warmer in the valley than in Malibu which you notice immediately driving over Topanga.

True. But it's sunny. You cruise down the road on your bike, feel the breeze from moving in the air, and we have a lot of bike paths too.

I commute most days, usually several miles. The only time I prefer car or train is when its raining, which is rare.

It's nice to see Google using Polymer.js on their pages.

Are they going to take it down like Microsoft did with Monster Truck Madness 2 website?

That's an excellent question. Doing this did not, at any point in time, feel like I was sacrificing my time for other fun activities. I enjoy coding the point of addiction sometimes.

On contrary, I felt the opposite most of the time - "I should be writing code right now instead of playing video games or socializing on weekends." But that will differ from person to person. Certainly not everyone will enjoy programming 24/7.

Satellizer gives you an illusion that you're doing an implicit grant flow by opening a popup and then magically you are signed-in. But authorization process is handled on the server: https://github.com/sahat/satellizer/blob/master/examples/ser...

I just implemented a GitHub sign-in and it took me only 8 minutes because on the server it was mostly copy-&-paste of the Facebook sign-in and on the client it's just:

  $authProvider.oauth2({
    name: 'github',
    clientId: 'xxxxxx',
    url: '/auth/github',
    authorizationEndpoint: 'https://github.com/login/oauth/authorize',
    redirectUri: window.location.origin
  });

Thank you. I like React too so perhaps someone could implement something like Satellizer that integrates with React.

Thanks for the explanation.

>I like React too so perhaps someone could implement something like Satellizer that integrates with React.

Indeed. And such a project could still make use of the server code of Satellizer, I'd imagine.