In the past (C/C++ days) we used a lot of third-party binary-only packages
like SmartHeap for memory management and LeadTools for imaging. (I like to
think of that as the "Programmer's Paradise" era.) I haven't used
binary-only packages in many years, but I do wonder how a company like
LeadTool
The purpose of a standard, in my opinion, is to allow multiple
implementations to be compatible. This seems counter to the open-source
model, where there is a reference implementation completely in the open
that encourages community participation and improvement.
JavaScript needs a standard - t
I haven't done it, but these two might be a starting point.
https://github.com/Azure/go-ntlmssp
https://github.com/ThomsonReutersEikon/go-ntlm
Mike
On Saturday, December 9, 2017 at 5:59:41 PM UTC-5, snmed wrote:
>
> Hi all
>
> We are primarly working in a windows environment and developing web
Hi, we’re needing to use FIPS-validated crypto in a particular deployment.
It looks like the dev.boringcrypto branch would meet our needs well. But
I’m struggling to verify which BoringCrypto version is actually meant when
the Go version is 1.14.1b4. Looking at BoringSSL I’m trying map b4 to a
Thanks so much for the quick reply. I see where that comes from now.
On Tuesday, April 7, 2020 at 12:40:52 PM UTC-4, Filippo Valsorda wrote:
>
> On Mon, Apr 6, 2020 at 5:45 PM Ian Lance Taylor > wrote:
>
>> [ + filippo ]
>>
>> On Mon, Apr 6, 2020 at 2:00 PM ancie
+1. I found the new draft readable and in practice it feels quite natural.
My hope was always that generics would "feel like Go".
On Tuesday, June 23, 2020 at 12:34:30 PM UTC-4 Haddock wrote:
> Also big +1 from my side and kudos to Ian for always answering to this
> storm of objections and sugg
said, I'm sure my design could be improved a lot, and I'll do that when
generics are released.)
If anyone wants to do a comparison, you can look at:
https://github.com/ancientlore/go-avltree (original version)
https://github.com/ancientlore/go-avltree/tree/v2 (generics version)
Regards,
In my experience, they lag maybe a week for a minor release like 1.16.6 to
1.16.7. I imagine it takes longer for a major release, especially if it's
time to upgrade BoringCrypto (like b5 to b7).
Mike
On Friday, August 27, 2021 at 7:09:21 PM UTC-4 jonath...@gmail.com wrote:
> Hey there,
>
> Go
I agree this is very good news. I don't have any visibility into the
timing, but from watching other modules, I'd say it can be hard to predict
how long it takes a module to proceed through the process. Up to a year
maybe?
Have you looked at GOEXPERIMENT=boringcrypto and importing
"crypto/tls/
