Is Go's crypto/tls ready for production environments? [closed] - ssl

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
There was previously a comment regarding the crypto/tls library in Go not being ready for production which has been quoted in many places but I have not seen any real updates on this issue.
http://grokbase.com/p/gg/golang-nuts/139sqq5hw5/go-nuts-re-go-is-production-ready-but-the-crypto-tls-package-isnt
What is the status today?
Since the comment was made both v1.2 and v1.3 of the language has been released. Has the library matured? Is it considered production ready?

Related

Does Machine learning models often needed to be compressed to run on MCUs.? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 days ago.
Improve this question
Does Machine learning models often needed to be compressed to run on MCUs.?
You are welcome to answer with (Yes, or No) with a good explanation.

Is the sylius ready for production? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
At Sylius "Sylius is still in development" is shown at the top. Does it mean that I can not use Sylius for my future shop? Or there could be bugs in the current version?
It depends on your release date.
V1.0.0-beta will be released by the end of November (see Roadmap update)
There are a lot refactoring and a big focus on documentation.
Some companies are already using it, you can see them in the showcase of official website, and personnaly, i use it for my future shop.

Emailing about Code freeze [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I need to notify my team about the approaching code freeze, So what all details should be mentioned in the mail? I want to prepare a standard template.
Thanks in advance
I usually mention the following items:
Code freeze date (date/time of last commit).
Name of the branch that'll be used for the freeze.
Grace period length for critical in-progress issue.
What release/build is this for.
Feature set of such release.

Is it currently possible to cross compile SWIFT for another platform [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Because of LLVM will it be possible to actually compile SWIFT code for use on another platform.
Of course you couldn't use the Apple only libraries, but just for generic code, does LLVM enable this, even if Apple wouldn't support it?

Why would you choose Squeak over Pharo today? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am trying to understand the uses of both. Already I have seen stuff on the SmalltalkHub doesn't often build on Squeak but always seems to work with Pharo. What are the advantages now in 2014 to choose Squeak and not Pharo?