wernerb

While I appreciate the record, the GPS fast forward video shows frequent texting while driving. Is this legal in the US? Here in the Netherlands we have statistics showing car accidents up after a downward trends with texting while driving as the leading cause. It makes me wish people were back to using cellphones without carkits, at least people had more chance of eyes on the road.

mode switching is very important. The upscaling is always worse than if my TV is trying to handle it.

I have a "niche" device called the Nvidia shield, and it does not support per-app switching either. It is slated for Android Oreo though, but until then I am running the shield on 1080p and just watch 4k netflix on lg smarttv.

Tbh, I would feel better if mode switching wasn't required at all, and Android and apple would invest in truly great upscaling techniques that can rival the native TV capabilities. The problem is, that I can't really as a consumer quantify if the upscaling is up to par, and rather assume that the TV is always better.

You can use variables in the FROM statement (recent docker versions).

Curious he does not mention the hosted elasticsearch+kibana on Amazon. Even integrates with cloudwatch and lambda to pull in the data.

The program goes into the why: in nature fat and sugar can not be found in combination so there is no natural inhibition.

They tested this with mice, one set would have unlimited fat, another unlimited sugar, and the third set the combination of sugar and fat. Surprisingly, the first two sets of mice would stop eating when they were full. Only the third set of mice would go on eating and eating..

I can't argue with the logic of the talk show guest, (who seems very good at her job!)

They are dealing with economy of scale. If facebook+google have 90% ad penetration then snap must displace facebook.

Having the car drive itself away is in my mind one of the most important features to get increase 100% electric market. You can have the car drive to a charger and automatically drive back once full, mitigating a shortage of charging stations as people leave their cars there long after they are charged 100%.

Proceeding to feed this Paul Bettany's "Jarvis" from some movies...

As a paying gitlab ee customer, we love to use gitlab. I just have one gripe with review apps. We would really like you to open it up with an API.

Allowing us to create the infrastructure outside of gitlab-ci and setting the reviewapp url/domain etc using the API would be extremely valueable for us, as we are stepping off of the gitlab-ci, but would very much like the UI interface upgrades review apps provides.

We are stepping off of Gitlab CI because of: * Only a single pipeline allowed per repository. We have a monorepo as we have a lot of small artifacts that make no sense to split out to multiple repo's and have to manage using gitsubmodules or having a separate code review process (we use merge requests a lot!) * Gitlab-ci's "stages" and not allowing dependencies on cross-stage is not helpful * No "skipped" status that can be supplied during the pipeline. E.g., we want to ignore changes to our documentation .

I feel this short (but worthwhile) video explains the problem best. https://m.youtube.com/watch?v=7Pq-S557XQU

You could rotate the key (make available the new secret) before expiring the old. During that time (which can be even a few hours) you typically reload your application to use the new credential.

If you are able to change your application's code, you could integrate with vault's API directly which is the most clean solution. If you are unable, you can use [consul-template](https://github.com/hashicorp/consul-template) or [envconsul](https://github.com/hashicorp/envconsul) to securely introduce your secret which would entail reloading/restarting your application.

"We found every submission to be of high quality. We will now explain why your talks are actually garden-variety by using landscaping metaphores"

Jokes aside. The issues raised are very good, but I can't help but think biased to a certain intended crowd. How does the panel(?) stay objective? Are the different views on topics and how to formulate the synopsis (exaggeration) perhaps relevant to a certain type of conference attendee and so deserving of a separate conference track?

I guess this is where KrebsOnSecurity went to when moving to google cloud? [0]

[0] https://news.ycombinator.com/item?id=12574428

Until we know exactly what websites/videos etc are loaded (also on the Opera benchmark!); you, me and all consumers do not know if this is true :)

The way I read the blog is that the adblocking is enabled to show that even _with_ an expensive extension enabled it still beats Edge, but that was in my opinion not the gist of the post.

The post was about that microsoft is not transparent about the methodology/setup/scripts/target websites used. A third party should be able to support Microsoft's claims.

Is it possible for the setup to be published to your github.com/microsoft so that it may be executed automatically? Heck, go the extra mile put it in a CI and publish the data on regular basis :)

Oh yeah its accessable from China. But I meant that there is no cloudfront edge region in China so chinese customers must cross the firewall and it is really really slow for them.

Cloudfront is not available in China. We had to implement a small CDN for a large ecommerce website. What we did was use geo-ip route 53 and route chinese ips to load balanced nginx instances caching the cloudfront cdn.

What compounds the problem with China is that the chinese are very much used to requesting an english language variant of the webstore as its often cheaper. This circumvents the CDN however as all stateful requests are routed to foreign servers making their experience really slow.

Also there's the chinese web license process that you have to go through to even host a website in china.

The video was created by Weta Workshop who specializes in special effects. "Providing design and manufacturing for film, television and creative industries for over 20 years."

I would not put much stock (no pun intended) into this unless there are more videos like the first one in the article mentioned.

'Nothing was your own except the few cubic centimetres inside your skull. ' (1984 George Orwell)

Interesting, do you have a source for more information? (not meant to be snarky, genuinely interested)

There is an active pull request here: https://github.com/docker/libcontainer/pull/479#issuecomment...

Yes, full freeze of process with CRIU could be an option though not limited to that. Tcp network pausing/throttling as well.

Regarding backpressure I am talking about reactive streams, of which I am a fan of late, this would be better suited perhaps at the application level [0].

Regarding infra/pod level migrations, I am wondering if this would be something to implement at the kubernetes level , perhaps a new type of controller/service ? You could then perhaps use labels to identify throttling/freezing/thawing of pods during migration.

[0]: http://www.reactive-streams.org/

Great to see development in storage with docker!

I like how this migration works. What about live migrations? Maybe I misunderstood, but I think in the tutorial the service is offline for some time. What about maybe applying backpressure (tcp level) to timeout the request while migration is underway?

Edit: If we are doing tarball migrations, then maybe i'd rather have an rsync backend :)

Oh and if we are doing large amounts of data migration (gigabytes), maybe even use something akin to something like what bittorrent sync is doing? The scenario would be that you use bittorrent sync (this is a theoretical example..) to one-way migrate continuously (to maybe multiple hosts..??), then pause/hold traffic when satisfied, complete final sync and you are migrated.

You can use an ambassador such as listed here [0].

[0] https://docs.docker.com/articles/ambassador_pattern_linking/

I was missing a docker container that hosts the Xserver and produces the X socket for the other GUI containers. This would be great for non-gui docker management platforms such as CoreOS.

Be careful, I think you get alotted free machine hours. This means that if you use multiple micro instances you will spend those free hours more quickly.

Drone [0] seems what you would like to use. Define all your containers as service containers and create/define steps to test how those service containers co-operate. Of course, you must test each service container individually in separate drone builds.

[0]: https://github.com/drone/drone

This looks really cool. I wonder though if my bed would not then be dependent on your servers at some point as I consider such a product as a long-term investment. For example, can it live without the server-side aggregation? Would you consider opensourcing parts of the server to enable people to use their own servers in the long run? Would you consider adding a respectable API that follows the ideas of for example, the philips hue? http://www.developers.meethue.com/philips-hue-api

C# and F# are different languages..

Last I checked you could not mix the two easily [0]

[0]: http://stackoverflow.com/questions/14280001/why-cant-we-use-...

The OP points out that immutable code is the standard in Scala. You have picked an example where Odersky gets 'lost' in mutable code. If anything, this video (and your comment) makes the case for immutable and side-effect free code using Actors and FP, as apparently it can be confusing.