Agreed. I recently stumbled upon the fact that even Hacker News is using Firebase for exposing an API for articles. Caution should be taken when writing server-side software in general.
It's also that not all services used together may work on the latest version of k8s. For example, one of the services can only support up to 1.11 and need updates to use 1.12, then you suddenly cannot deploy 1.12 to those clusters. I think in terms of LTS it's more about having stable APIs for developing.
For direct integrations there is already a tool called Sublimerge (https://www.sublimerge.com/) (I am not affiliated with this team), anyone compared the two?
If it's a merge tool is not integrated directly with the editor, it's not as useful.
On a side note, the competition for this sector of market, for sublime and such is much tougher, like atom and vscode being "free" to use. The one thing that hinders definitely, is the amount of third-party packages available.
What really trigger this is that their beta versions for mac and windows now have a changlog reading like this:
"Introduce Docker Community Edition"
It seems that they would be releasing the current tools as a separate but related product now. Just to clarify, Docker for Mac or Windows is not open-sourced (although it includes docker which is open-sourced).
I am always thinking, if the compression scheme is known, you would need some good noonce to avoid known plaintext (for example, compression format's header is always the same), and also by CRIME, which is to remover the dictionary of the compression.
I think it is best to use built-in compression scheme by the compression program to do the encryption first, as those often take these into account (and the header is not leaked, since only the content is encrypted).
