3 ms·

I would've thought there's a better way of approaching software design in 2020 than "This 50,000 employee company decided to open source one big bang grab bag o

I would've thought there's a better way of approaching software design in 2020 than "This 50,000 employee company decided to open source one big bang grab bag of functions". Especially with a readme that doesn't include any explanation of what's in the library or why they're there. >Folly (acronymed loosely after Facebook Open Source Library) You literally broke your first promise. That literally translates ot FOSL. You could've used FOSL. That's a word. It makes sense. It's even a bit funny. >is a library of C++14 components designed with practicality and efficiency in mind. As opposed to all those components that are designed with impracticality and inefficiency in mind. I honestly don't think I can say I've ever designed anything without those two things in mind. >Folly contains a variety of core library components used extensively at Facebook. Which tells me literally nothing about what's in this library. How do I know what's used extensively at facbook? Last I saw it was mediocre PHP 4.

shafte 7y ago
Perhaps you missed the "What's in it" section while skimming the readme? :) >Because of folly's fairly flat structure, the best way to see what's in it is to look at the headers in top level folly/ directory. You can also check the docs folder for documentation, starting with the overview.
- Traster 7y ago
  Ah, the old "Read the code" version of documentation. Guess what? That's not documentation. That's douchebag for "I didn't write documentation"
  - shafte 7y ago
    That doesn't seem very fair. They link a docs folder and an overview document, neither of which require that the user read code to get a good idea of the library's contents. That said, the code is also reasonably well commented as well, for example: https://github.com/facebook/folly/blob/master/folly/Singleton.h https://github.com/facebook/folly/blob/master/folly/Singleto.... So "read the code" is not terrible advice in this case either.

shafte 7y ago

Perhaps you missed the "What's in it" section while skimming the readme? :) >Because of folly's fairly flat structure, the best way to see what's in it is to look at the headers in top level folly/ directory. You can also check the docs folder for documentation, starting with the overview.

Traster 7y ago
Ah, the old "Read the code" version of documentation. Guess what? That's not documentation. That's douchebag for "I didn't write documentation"
- shafte 7y ago
  That doesn't seem very fair. They link a docs folder and an overview document, neither of which require that the user read code to get a good idea of the library's contents. That said, the code is also reasonably well commented as well, for example: https://github.com/facebook/folly/blob/master/folly/Singleton.h https://github.com/facebook/folly/blob/master/folly/Singleto.... So "read the code" is not terrible advice in this case either.