xxyyzz3d

Yeah, I think the keyword there is ideally, because it's really hard to know how much of a difference it actually makes.

Say your luggage is misrouted or mishandled. Does knowing the GPS coordinates actually help? In the end you still need to get the airline / airport to properly process and return the luggage. I somehow don't imagine that there exists a process now to get that information to the right places. Knowing that your luggage is stuck in London when you're in Tokyo doesn't really un-ruin your vacation, so I'm not sure about how that aspect is being marketed.

  TypeScript now supports using ‘let’ and ‘const’ in addition
  to ‘var’. These currently require the ES6 output mode, but
  we’re are investigating relaxing this restriction in future
  versions.

Would be quite nice to be able to use 'let', and just use variable renaming to generate ES5 code with unique names in the case where scopes overlap. I guess it might be coming?

I think there is something to notice about having a hard fixed timeline for everyone. See from the bug:

https://code.google.com/p/google-security-research/issues/de...

  > Microsoft confirmed that they are on target to provide fixes for these issues
  in February 2015. They asked if this would cause a problem with the 90 day
  deadline.
  
  < Microsoft were informed that the 90 day deadline is fixed for all vendors and
  bug classes and so cannot be extended. Further they were informed that the 90 day
  deadline for this issue expires on the 11th Jan 2015.

  > Microsoft confirmed that they anticipate to provide fixes for these issues in
  January 2015.

So basically Microsoft asked for an extra month, and they said no, which forced them to move quicker, and fix it a month earlier. Without picking any side of the debate, you can still see what effect the non-negotiation of timeline has on getting patches out as soon as possible.