1,869 karma · joined September 1, 2011
NASA must have decided there was no real danger to the operators apart from some longer shifts and sleeping in the office. Otherwise, even without the backup ground control, ISS wouldn't be in any significant danger if disconnected for a few days.
Unless AI is constrained to pro player max pointer move delta, click rate, and vision latency, I don't really see much difference between AI and a team of kids running with aimbot shouting "cyka cyka".
For comparison, the fastest train is 2h 25m. I guess you need to travel to and from the train station too, but it's definitely more central (2x15 min) and you can easily hop on train even five minutes before the departure - although I usually plan at least another 15 min buffer. That is a total of a little over 3 hours.
I don't pretend to know enough about economy of future trains vs future electric flights, but it looks like short distances will always be a tough sell for airplanes. Personally I also find trains more comfortable and I was never given a free massage for carrying scissors in my pocket when boarding one.
My Nexus 5 (2013), fully under control of Google, didn't get even 7.0 (2016). Moto G4 (2016) I bought few months ago is on 6.0 (2015), might get 7.0 (2016) soon-ish. I basically stopped caring about new versions, buying new phones to get the latest, etc. They are not even as exciting as they used to be, feature-wise.
edited: Nexus 5 actually got 6.0
I've seen this technique somewhere exploited even further, by tricking yourself into working in "forced mode" on something completely secondary, while resting when working on the important stuff.
Privacy should be an added value, not something we put in front of everything else. It would be meaningless if web wouldn't enable us to do what we do. So in reality, isn't this poll just a list of things we already have thanks to the internet, plus one thing we don't have - privacy?
> You are correct that many valid issues/bugs have been closed without resolution.
> Our team simply does not have time to address all issues AND build Angular Material 2. (This is what we have consistently stated in our Forum posts).
> We welcome community leadership with Pull Requests. Often those PRs have side affects, their scope of changes is too large, and ultimately the risk is simply too great to merge.
> So we close/reject the PR... we do this to protect the existing user base. Pull Requests that have granular improvements and fixes are much easier to assess, test, and merge... and thus can be quickly merged.
> Pull Requests that are submitted referencing closed issues will then trigger us to reopen those issues; until the merge is complete.
> After Angular Material 2 has been released, we expect to continue to support and improve Angular Material 1 for many quarters.
> Both versions are important. Both are need to support the Angular 1 and Angular 2 developers
For me it's clear while the work on Material 1.x is not prioritized, it's not officially deprecated and PRs are still welcome if they are reasonable in size and impact.
Yet, the available toolchain for it is years behind others. If you wonder how you should have any live reload development with it, you can either rely on community plugins like grunt-closure-compiler [2] or hope plovr[3] is finally resurrected back to a state where it's usable. This all sounds fine until you think about any unit testing. The only karma runner[4] for closure is simply broken and unmaintained. Even worse, most of npm packages you might want to compile with your code will output thousands of errors because there is no clear way to whitelist code as "not my code leave it alone". I can just hope one day Google will publish a yeoman generator with all those things solved and get it back in the game.
[1] https://groups.google.com/forum/#!msg/closure-compiler-discu...
[2] https://github.com/gmarty/grunt-closure-compiler
Also, if you suggest only females are getting harassed at work, you are wrong :)