68 karma · joined November 2, 2014
http://www.math.ias.edu/~vladimir/Site3/Univalent_Foundation...
https://realworldocaml.org/v1/en/html/first-class-modules.ht...
this would be a plausible argument if the us treasury weren't the biggest buyer of long-term government debt.
are there any plans to make use of cohttp and/or lwt as the underlying network abstraction ? my concern with hand-rolled http is it may not handle the edge cases correctly and cohttp is more battle tested. also i believe it's more idiomatic ocaml to include interface files to hide the implementation details.
https://www.gov.uk/hmrc-internal-manuals/vat-government-and-...
vs old
http://www.hmrc.gov.uk/manuals/vatgpbmanual/index.htm
It's identical, except for a modified stylesheet. This may be 'unapologetically unifying and simplifying the experience of interacting with government', but this is not very much to show for all the time that has been spent on GDS.
The same comments apply to a lesser extent to the C++14 requirement- does your framework really benefit from using C++14 features over say C++11 ? Again I would make this clear at the top of the README.
Poly1305 isn't a walk in the park, but doesn't need special hardware support for fast constant-time implementation. Though I will agree something like HMAC is much simpler.
1) userland and kernel owned by the same group. this lends consistency to the experience, that is absent in linux, where it's clear that it's an amalgamation of many different tools.
2) (largely) one way of doing things
3) package management system (pkg-ng) that is a cross between gentoo portage and debian apt-get
4) extremely good documentation for an open source project (https://www.freebsd.org/doc/handbook/)
5) configuration is very simple (mostly driven from rc.conf)
6) excellent full-disk encryption support (geli)
driver support always lags a bit behind linux, on the other hand the drivers that do exist i'm confident are stable. i make sure to buy hardware which i know is supported.