LibreSSL, and the new libtls API

Re:LibreSSL, and the new libtls API by angersock on Friday October 02, 2015 @04:12PM (#10320991)

So, forking is pretty much the only way to do proper code cleanup in a timely fashion, right?

If you don't, people still clamor for legacy support and bug-for-bug compatibility. A fork is the only way of truly signalling "We aren't going to support our old mistakes anymore."

New features don't need forks, but cleaning up raging stupid and cruft does.

[ Parent | on HN ]

Re:LibreSSL, and the new libtls API by neoCrimeLabs on Friday October 02, 2015 @04:33PM (#10321130)

IMHO, there is a time an place for everything. Sometimes forking is a good idea sometimes not.

When you want to make idealogcal changes to an existing codebase that does not mesh with the idealologies of the maintainer(s), forking is a great way to make your changes happen. Time will tell if your ideas were good ones. That and how well your maintain and promote your fork. :-)

In the case of OpenSSL vs LibreSSL, it appears the OpenBSD team made a great call and they are making it work really well. As for if anyone else agrees and adopts it, only time will tell.

[ Parent | on HN ]