86 karma · joined August 9, 2016
> You can then use tox (or nox) to define your component and framework versions as variant virtual environments. As components evolve, you update the versions and rerun your test suite. You can publish internal update trackers for project teams to make sure they're testing with the latest-and-greatest environments.
So I am curious about the specific tool recommendation, thus the question.
Remember that just because you love to hear what your application is doing, it's not always be helpful or useful to your user. Give consideration to the Rule of Silence (http://www.linfo.org/rule_of_silence.html) and even if you do not agree with it remember that some of your users might.
Johnson, you’re fired! I just saved myself 10 grand a month!
Narrator: where do I sign up to work for that guy...........
In fact, the Microsoft version of CSV is a textbook example of how not to design a textual file format. Its problems begin with the case in which the separator character (in this case, a comma) is found inside a field. The Unix way would be to simply escape the separator with a backslash, and have a double escape represent a literal backslash. This design gives us a single special case (the escape character) to check for when parsing the file, and only a single action when the escape is found (treat the following character as a literal). The latter conveniently not only handles the separator character, but gives us a way to handle the escape character and newlines for free. CSV, on the other hand, encloses the entire field in double quotes if it contains the separator. If the field contains double quotes, it must also be enclosed in double quotes, and the individual double quotes in the field must themselves be repeated twice to indicate that they don't end the field.
The bad results of proliferating special cases are twofold. First, the complexity of the parser (and its vulnerability to bugs) is increased. Second, because the format rules are complex and underspecified, different implementations diverge in their handling of edge cases. Sometimes continuation lines are supported, by starting the last field of the line with an unterminated double quote — but only in some products! Microsoft has incompatible versions of CSV files between its own applications, and in some cases between different versions of the same application (Excel being the obvious example here).
The first thing I thought when I read this news was - good maybe they’ll take their 360,000 employees, make them all use Linux, and as a consequence standardise a developer laptop to compete with MacBook.
The second thing I thought was - if there is 360,000 people with Linux laptops in your enterprise, what sort of creative uses could you come up with for container orchestration.
The third thing I thought was - I wonder how much they pay in Microsoft licensing per year.
Here's an example - AWS VPC connections only supports IKEv1. (https://forums.aws.amazon.com/thread.jspa?threadID=252723) (https://docs.aws.amazon.com/vpc/latest/adminguide/Introducti...)
IKEv1 vs. IKEv2: https://en.wikipedia.org/wiki/Internet_Key_Exchange#Improvem...
Sounds like my kinda guy!