I wasn't unhappy about new keyboard feel but rather quality of keyboard itself. Eventually I'll bring it for repair, I think that should be covered indeed.
Apple mentioned something on a special "extreme" iMac model during their Mac Pro apologizing meeting last month. I'd assume i9 would be the right fit: something like 22-core Xeon would've been too expensive but single i9 would likely be just right.
It's probably the wrong thread to share my hopes for the next-gen but still.
My family owns four 2016 models (maxxed out both 13 inch and 15 inch, a pair used at a day job and a pair is personal) and we all experience similar issues:
a) Touch Bar reacting to fingers that are accidentally touch it while resting. Causes a lot of volume and Esc triggers. Latter is particularly annoying at it usually cleans Slack/Skype/other active text input.
b) Keyboard quality is terrible. My work machine does not respond to Option and Control presses anymore. My wife's machine has similar issues with up/down arrows.
c) I don't get why Apple changed default/native resolution to be non-retina trading extra screen real estate for image quality.
b) Last but certainly not least as mentioned on all previous MacBook threads starting October 2016: running Docker/minikube/Chrome/Slack and et voila: you have 4GB of RAM left.
I'm not even talking about ML/Data Science work: AMD GPUs are way behind even 1050 at the moment and I doubt that their new offering that is meant to compete with nVidia P100 will ever make it into a laptop.
Personally I think this news isn't real. Intel "promises" to release Cannonlake this year (thanks, AMD!) and I don't see much sense in either updating MacBooks with Kaby Lake nor releasing them just after 8 months after last refresh. That's the CPU that you get when company stops trying.
If they are going to mention MacBook Pro, I'd probably expect them to do a small price drop but not a refresh.
Yes and no: yes you can get a Quad-Core 64GB RAM + SSD server for $55/month (source: https://www.hetzner.de/de/hosting/produkte_rootserver/ex51ss...).
But there's one more spec that matters: networking. It takes completely different amount of effort to provide 1Gbps connectivity versus 40Gbps per server.
Most of the providers like Hetzner/OVH provide former, while GCE provides the latter. I'm not saying it's bad, in fact for most of the people 1Gbps would be more than enough. But it's not something that is fair to omit.
Disclaimer: I don't work for Google, just from my experience.
Incidents are inevitable and it's important to have a proper RCA/Service-Disruption process in place to handle those.
As mentioned on the other thread, maybe Gitlab doesn't have enough operational/SRE expertise in-house yet, but that was the case in every fast-growing company I've worked for last decade.
I wonder what are hardware specs on Google Cloud. I didn't manage to find anything similar for GCE.
E.g. what's the max speed of internode network connectivity within a region zone? What's the spec of local-ssd? Could be interesting to know underlying hardware.
I've been playing with it recently and you could implement peer-to-peer file transfers encrypted client-side with something like Stanford JS Crypto library.
It seems like you have a bunch of console errors: missing CORS headers, `clientXHRSignalingChannel.js:3 Uncaught TypeError: failureCB is not a function` and a bunch more. It does generate a key but the receiving party cannot download the file (probably because i cannot upload because of these errors).