The bigger, of course also more distant and vague, announcement is that "by 2050 Microsoft will remove from the environment all the carbon the company has emitted either directly or by electrical consumption since it was founded in 1975."
I'm a German engineer in the US. The thing with these stories is that they won't happen to you. If you're employed by a tech company you have great health insurance.
Of course, it still sucks that it can happen to someone at all and you might not want to live in such a society. That's a separate issue.
Speaking of SV, I think the cost of living and the social problems there have made it increasingly unattractive. Seattle is nice.
The actual title on microsoft.com, "MariaDB, PostgreSQL, and MySQL: more choices on Microsoft Azure", has actually less marketing spin and more information.
What's the business model going to be? The ToU are quite far-reaching regarding user content: "By submitting User Content through the Services, you hereby do and shall grant us a worldwide, non-exclusive, perpetual, royalty-free, fully paid, sublicensable and transferable license to use, edit, modify, truncate, aggregate, reproduce, distribute, prepare derivative works of, display, perform, and otherwise fully exploit the User Content".
Also, are there other ways to browse, search, etc., the highlights in addition to the daily email?
Right. You could always define a new type with an existing underlying type, like Celsius with the underlying type int in your example. See the spec here: https://golang.org/ref/spec#Types
This would define a new, non-interchangeable type, even though it's just an int behind the scenes. The new type alias on the other hand define a new name for an existing type; you still have just one type. In the user ID example above that's not what you want, it would allow using an int where a UserID is required.
The Go standard library is very well written and depending on which parts you read you can learn about lots of things like file operations, HTTP, crypto, etc.
It's easy to read it all on the web, the docs are here: https://golang.org/pkg/ and clicking on a function name shows the source.
I've used both extensively and I think they are fairly different, with different strengths and weaknesses. Bash is more pragmatic and more concise on the command line. PS is more uniform in its design and nicer for scripting IMO. It allows passing objects through pipes, has built-in JSON reading and writing, built-in parameter handling with defaults, mandatory and optional params, switches etc., and such niceties.