3 ms·
You'd have to be nuts to depend on something backed by Expensify. They'll probably fire the maintainers. Edit: Turns out it's authored by the CEO! So you'd hav
by thesmallestcat 10y ago
You'd have to be nuts to depend on something backed by Expensify. They'll probably fire the maintainers.
Edit: Turns out it's authored by the CEO! So you'd have to be nuts to use it, period. But, um, poke the source if you're curious. This is a good intro https://github.com/Expensify/Bedrock/tree/master/libstuff#libstuff----all-the-stuff-you-need-to-build-a-c-application https://github.com/Expensify/Bedrock/tree/master/libstuff#li... I can't imagine a more ironic and hilarious backdrop for the "We Fire People" campaign. Must be tough finding people who can keep up with a brain that big.
- quinthar 10y agoOut of curiosity, what specifically do you find idiotic about the document you linked to?
- thesmallestcat 10y agoI didn't call anything idiotic. But let's just say that grappling with the STL may be slightly preferable to this... thing. And there is some special irony referring to STL as an "esoteric abstraction" while offering your own vastly more esoteric abstractions in the same swoop. And the following paragraph speaks for itself, particularly in the context of developing a fucking database: > Computers are super fast these days, and real world applications spend 99% of their CPU time doing some very specific item, with the rest of the time spent doing just boring stuff. Accordingly, libstuff is not intended to be hyper-efficient: it's intended to be hyper-usable. This means libstuff uses a lot of std::string objects for pretty much everything. Where a more complex object is required, some higher-level string-based object is used.
- quinthar 10y agoYes, I think it does speak for itself. Thanks!