1) Most software gets its timestamps from the system clock
2) If you have a mismatch between the system time and the application time, then you just have log timestamps that don't match up; it's a nightmare - even more so around DST/ST transitions
Deaths are currently at around 2,000 PER DAY in the United States. That is not in any way, shape, or form "extremely lower" than earlier waves. The Omicron wave was equal to the initial wave in severity, and we're still not out of it.
2016 IS very recently. Three years ago does not count as "many years ago". Richard Stallman is 66 years old. To have only realized that pedophilia is bad at age 63, only when other people had to convince him..welp.
> There's a big difference between standard styling and optional styling.
THIS.
This is not stated enough in the value of gofmt - it's the standard formatting style for everything. I've worked in Java and C++ for a couple of decades, and while every team has had its own style guidelines, and occasionally tools to enforce them, even different teams in the same organization would have difficulty understanding each other's code.
The value of gofmt is that it's the only formatting standard, thus I never have to learn a new formatting style when reading the code for an open-source library, or coming in to a new job. It's exactly the same as what I've been reading for the last 3 1/2 years of working in Go.
Go code compiles to compact, statically linked binaries with relatively compact memory usage and reasonably good concurrency support, and an excellent standard library for handling networking - it's a natural fit for monitoring stacks. Even some monitoring systems that aren't Go on the back-end have Go-based collectors.
Datadog will cost you $165,600 a year for 600 hosts. That is objectively equal to a very well paid engineer. So no, the statement is not untrue.
(I picked 600 because that was the approximate number of machines we had at my last job, where we used Graphite maintained by one guy, part time).
You included a LOT of redundancy in your OSS list. Multiple timeseries databases. Multiple collection daemons. Multiple dashboards. Multiple alerting systems (Who in their right mind would use Nagios AND Icinga?). You're effectively arguing about maintaining multiple monitoring stacks, some of which are quited aged.
Yes, however some features in TypeScript are only supported when targeting ES6 (such as "const"), so there's still some value in double-transpiling from TypeScript -> ES6 -> ES5 (I'm doing that on a couple of projects).
That may have changed somewhat in the TS 1.5 alpha - they're supporting more features on the ES5 target than they did in 1.4.
But yes, you still can't use ES6 features that TS doesn't know about.