montyedwards

4 ms·

1.
by montyedwards 10y ago
Not disagreeing with you or the postmortem, but: 1. that post is from Feb 8, 2016 2. nanomsg 1.0 was released on June 10, 2016 After nanomsg 1.0 release, recent activity on github includes: 8 days ago -- fixes #828 Add logical connections
2.
by montyedwards 10y ago
No idea when LibreSSL will add X25519 or X448, as defined in RFC 7748 - Elliptic Curves for Security. Here's RFC 7748 https://tools.ietf.org/html/rfc7748 Here's the errata for RFC 7748 https://ww
3.
by montyedwards 10y ago
I'm currently evaluating LibreSSL for use in data protection software I licensed to a large company. The optional libtls API bundled with LibreSSL is a really simple wrapper API that is secure by default. And it was a breeze to build o
4.
by montyedwards 10y ago
Swift is good for enterprises that standardized on Macs and ios devices, but there aren't many of those (yet). I'm pretty sure Swift isn't ready on Windows, which is a shame because most "enterprises" standardized o
5.
by montyedwards 10y ago
Nobody is suggesting OpenBSD not being RedHat should be embarrassing. However, it is not ideal to have a security-focused OS not directly provide binpatches for the base system and core libraries like libressl. Trusting OpenBSD.org is one t
6.
by montyedwards 10y ago
Anyone interested in using ECC should take a glance at SafeCurves: choosing safe curves for elliptic-curve cryptography http://safecurves.cr.yp.to/ There's a nice table showing which curves are safe and which curves ar
7.
by montyedwards 10y ago
Rust has: - Static typing - Type inference (and pattern matching) - No dependency on JVM, .NET, or BEAM But the number of web frameworks, etc. for Rust sucks compared to that of older languages like Go. Go 1.0 was released in early 2012 an
8.
by montyedwards 10y ago
Servo would be more compelling for use with commercial software if had MIT or Apache license. The MPL isn't as bad as GPL but still isn't as generous to the developer as MIT or Apache. With the right license, Servo would be a sla
9.
by montyedwards 10y ago
I understand, but none of those links are the .NET Core 1.0 release announcements. And the download page for .NET Core 1.0 doesn't mention FreeBSD at https://www.microsoft.com/net/download#core
10.
by montyedwards 10y ago
I don't see mention of FreeBSD anywhere in the .NET Core 1.0 announcements -- has official support for FreeBSD dropped or been postponed?
11.
by montyedwards 10y ago
I don't see downloads for FreeBSD. CoreCLR (.NET Core) mentions FreeBSD at github, but nothing from Microsoft's announement of RC2.
12.
by montyedwards 10y ago
The Go programming language doesn't compile to C. Compiling Go is faster than compiling C. If Go transpiled into C code first, and then had to compile resulting C code, then that entire process would be slower. The Nim programming lan
13.
by montyedwards 10y ago
I'd use OpenBSD if it provided: 1. significantly faster vioscsi(4) driver for VirtIO SCSI adapters -- I can live with vioscsi being up to 2x slower than Ubuntu or FreeBSD, but 5x - 10x slower is probably a deal breaker for some other f
14.
by montyedwards 11y ago
I tried TDM-GCC. In my experience, certain aspects increase risks when using go: 1. go is buggier for Windows than Linux and FreeBSD, even though they are all "first class" platforms in go. 2. cgo is also buggier for Windows tha
15.
by montyedwards 11y ago
The only thing preventing me from using Go on Windows is lack of production quality cgo on Windows x86 and x64. For example, using external linking should "just work" with recent versions of sqlite3 but it fails on Windows.