Unity wont bake lights on Ryzen Hackintosh too using Progressive GPU/CPU. Also VMWare won't run because of lack of Intel specific VT-x support, same with Docker for mac, Virtualbox runs fine though (it finds amd-v).

It feels like GCP figured out a way to charge for ingress. I can get behind using NAT instead of our instances having external IP's but a 4.5¢/GB hit on egress AND ingress traffic is hard to swallow.

If you like this you might like Glances. I use it on my home cluster to monitor Docker quickly. You can pull it up in a browser for extra laziness.

https://nicolargo.github.io/glances/

Safari seems lacking in the browser extensions department.

This is probably the only reason I don't use Safari on macOS. Especially since their new extension API came out, most of the (few) extensions I was even able to find are now manual-install pains.

I would use it for browser testing websites if it's renders identically to the Windows version.

Seems unlikely to ever render identically. At the very least I believe chrome uses the platform specific font shapers (coretext on mac, cleartype on win).

So in the end, a mac version of edgeium just adds yet another browser to the test matrix columns....

Seems like a good idea to check for and try any export tools before adding content to a system. Furthermore if the site provides the export tool there's no guarantee they wont take it away or modify it.

The best approach is to keep your source of truth out of the Medium platform from the start. You can use the "import post" functionality to tag your original off-Medium post as the canonical one, which gives you the best of both worlds: Medium discoverability plus full control over your content. https://help.medium.com/hc/en-us/articles/214550207-Import-a...

I think we can be sure they won't do it because of GDPR.

I commented on a thread a couple weeks ago about Cloud Functions on GCP here: https://news.ycombinator.com/item?id=17796893

Eager to test it out we ran thousands of tests attempts with different RAM sizes and I can corroborate this persons findings in regards to the reduction of cold start time from functions with larger RAM allocations and seeming unpredictability of cold start on GCP. I hope with time they will improve cold start times or increase the minimum time for making a function "cold".

From the parts I can see in Knative-land, it's being given a lot of thought. My view is that the biggest improvement to be made is in smarter handling of raw bits. Kubernetes doesn't quite understand disk locality yet and most docker images are less-than-ideally constructed in any case.

What do you find suboptimal about most Docker images? Just the size, or something else?

I wrote several thousand words on the topic a few months (email me for the link).

The gist is: you can make an image easy for developers, or you can make it performant in production, but you cannot have both.

Ease of development typically leads to kitchen-sink images or squashed images, but production performance requires careful attention to the ordering and content of layers.

Among other things with puppeteer we do screenshot generation using GKE on Google Cloud @ https://screenshots.cloud/ scaling up and down running instances depending on demand. We keep browser instances running constantly as the startup time is significant. I will be interested to see what the startup time is for puppeteer on this, will definitely be giving it a try.

Nice reference immediately above "used by us" :)

One completely unrelated thing. On Chrome 68.0.3440.84, I noticed the large icons (particularly the Kubernetes one) looked "weird", with jagged edges that didn't make any sense. Some poking with the devtools revealed that 'backface-visibility: hidden' seems to be disabling antialiasing.

Suggest opening the following in new tabs so you can flip back and forth between them:

- As is right now: https://i.imgur.com/nYzsukI.jpg

- Nicer-looking: https://i.imgur.com/GNlvx7Z.jpg

I noticed disabling this has an effect on the animation at the top (the edges of the moving webpage slides don't have constantly-moving jaggies).

There may well be a valid reason you have this enabled, perhaps for added performance. Or perhaps React added it in for you? :P

Thanks for spending time to let me know because I don't think I would have noticed it otherwise! I can't see it on retina but I can on my non retina display. We'll have to make the CSS rule more specific. As to why it's there I believe Firefox 57 or around that version had an issue with the sliding animation on the top of the page causing images to tear or not render at all when they scrolled in. This bug must have been solved recently because disabling backface-visibility on the image doesn't cause the same tearing.

I was very curious what was causing the non-antialiasing, it was fun.

And you can repro :) cool. Makes a lot of sense you can't see it on retina.

Interesting FF bug you hit. CSS3 GPU-accelerated animations are incredibly complex... heh, adding the rule fixed Firefox ~57, but now Chrome 68 is glitching out because the rule is there. I wonder if Google realizes yet. Ponders complexity of creating minimal testcase, versus waiting for someone else to notice :P

Looks amazing guys, public metrics looks like a really killer feature. Hope to be able to afford to spend $80/month on this in the future!

Thanks! Let us know if you sign up in the future and we can be helpful at all. Will have some more features coming down the pipe built around Public Metrics as well.

You can run your daily/hourly backups on the mirror and not impact performance on your main database.

Right. But the grandparent comment was suggestive of the possibility that he or she wanted the mirror to fulfil multiple roles, including being the backup.