What happens if a rollback somehow makes things worse? Even emergency rollbacks need a gradual rollout so you’ve got a chance to catch any new issues you didn’t expect.
I guess knowing that people will criticise your messy code is one of the reasons why people don’t open source more things. It’s nice to have the code open-source even though it’s not perfect.
To mount a camera on my desk, I'm about to purchase this "Neewer Tabletop Light Stand", and a mini ball head with standard 1/4 inch screw for angle adjustment.
I can't vouch for it yet, but hope it arrives and does the job. There's other similar products in other sizes by other brands.
I've been using InfluxDB, but not satisifed with limited InfluxQL, or over-complicated Flux query languages. I love Postgres so TimescaleDB looks awesome.
The main issue I've got is how to actually get data into TimescaleDB. We use telegraf right now, but the telegraf Postgres output pull request still hasn't been merged:
https://github.com/influxdata/telegraf/pull/3428
> Your control. Your network. Your infrastructure. Your responsibility
These are all the reasons why I don't want to self-host my own git. I can live with it being down every now and then. And when it is down, I don't want it to be my job to fix it. I've got more important stuff to worry about.
> Total privacy - we do not have access to your email account, Ivelope only sends your email data and password between your computer and your email server.
I wish this was the default assumption these days.
If that’s the user interface, I can hardly imagine what’s underneath. Is this thing actually secure with properly designed two-factor authentication, etc. Or a weak password and a PHP script and some rubbish like that?…
Google Apps isn’t Google’s primary business – they could neglect it and have unhappy customers, but their bottom line would hardly notice the difference.
Picking files out of homebrew for distribution is generally a bad idea. You’ve fixed the linking issues, but not -mmacosx-version-min.
If you run
$ otool -l libpython3.5.dylib
and look for LC_VERSION_MIN_MACOSX – you’ll see it’s compiled only for your current OS.
So, if you do this on OS X 10.11, your users will have to have OS X 10.11. It may appear to work on older versions of OS X, until you hit something that doesn’t. For example, when I tried using a homebrew library, it was compiled using newer SSE instructions that weren’t supported on older processors still supported by older OS X versions. So when testing on an old Mac, it crashed with bad instruction at a somewhat random point in execution.
I didn’t even realise it wasn’t free until reading your blog listing 'sales' separately to 'downloads'. Price needs to be way more obvious up the top. Only now just seeing it’ll cost $50, is a disappointment after thinking it was free.