Folly: An open-source C++ library developed and used at Facebook

Re:Folly: An open-source C++ library developed and used at F... by didip on Friday January 07, 2022 @05:21PM (#29845678)

If you start a green field C++ project, would you choose Folly, Boost only, or Abseil?

[ Parent | on HN ]

Re:Folly: An open-source C++ library developed and used at F... by dureuill on Saturday January 08, 2022 @03:43AM (#29849868)

I wouldn't start a green field C++ project if I can help it[1], but if I had to I would probably go with the standard library with maybe as little boost as possible.

[1]: http://cliffle.com/blog/prefer-rust/

[ Parent | on HN ]

Re:Folly: An open-source C++ library developed and used at F... by versatran01 on Friday January 07, 2022 @05:26PM (#29845729)

abseil and part of boost

[ Parent | on HN ]

Re:Folly: An open-source C++ library developed and used at F... by aaaaaaaaaaab on Friday January 07, 2022 @08:11PM (#29847452)

Unless you have a compelling reason: none of them. The modern (C++17<) stdlib should cover your needs.

[ Parent | on HN ]

Re:Folly: An open-source C++ library developed and used at F... by sgeisenh on Friday January 07, 2022 @08:24PM (#29847524)

The stdlib implementations of associative containers have serious drawbacks. At the very least, most projects should consider adopting absl::flat_hash_(set|map) and absl::btree_(set|map) (or similar replacements) over the stdlib containers.

I am also partial to explicit error handling over exceptions, and there is a lot to like about absl::Status (and absl::StatusOr).

Disclaimer: I work for Google but the views expressed are my own and don't necessarily reflect those of my employer.

[ Parent | on HN ]