Same. I like it for the funny memes, learning news, seeing what my friends are up to. I don't see it as particularly sinister or anything. I certainly don't think of it as an escape from a "mediocre" life.
Exception i encountered recently was needing ternary state boolean. a set of flags where true and false indicates outcome and undefined indicates "not yet processed". I suppose some sort of 0 timestamp could work but... No, I think I'll stick with boolean.
As a human being he wasn't perfect, but I come back to images from his film in my head time and time again and they help me look up from my work and consider bigger things on an ongoing basis. His films create space in my head which I go to for help when I need it most.
One of the hard things to get right when writing one of these "Tips for being a great X" is that they're usually written from the point of view of someone who is a clear leader in their field.
With some exceptions, the people who write this sort of article have the confidence (or presumption) to see themselves as ahead of the pack. It is rare to see articles like this written by teams of people who, in cooperation, balance tasks like product management, architecture, engineering, operations and customer success between them. And yet that is, imo, the best way to do it.
When I read and article like this advising the reader to do X to "their team" (in this case let your team get on with work), it falls into this category where the "how to be a great X" applies to a particular structure - where "X" is somehow in control of the rest of the team, rather than an equal participant.
Is there any indication that the numbering change reflects a significant technical shift (eg preparing to target ARM specifically)? Or is this just aesthetics?
Someone just got tired of writing "10." in the marketing team, also they'll be able to have a versioning more like iOS which macOS copies already much in 11.x
Main thing that would prevent me investing in this stack is that the runtime has been designed with typescript in mind. In a few years if the typescript thing blows over, you're left with a runtime and conventions skewed toward statically-typed programming patterns.
As someone who works with TypeScript extensively, TypeScript patterns are basically Javascript patterns - although perhaps with slightly fewer runtime type checks.
I used to dislike typescript, until I was hired to write it. It has warts, but the benefits outweigh them, and you aren't forced to use the parts you may not find beneficial. I think it's a good way to prototype a typed version of javascript, at the least.
