3 ms·
The issue is not that each one in isolation is particularly problematic, the issue IMO is when they get assembled by an end-user into a pile of mixed metaphors.
by arcticbull 8y ago
The issue is not that each one in isolation is particularly problematic, the issue IMO is when they get assembled by an end-user into a pile of mixed metaphors.
fmt::memory_buffer out1;
std::ostream out2 = std::cout;
auto out3 = printer(stream);
auto out4 = my_printer();
format_to(out1, ...)
out2 << "Hi..."
out3.print(5);
out3 += 6;
These all do the same but it's a total mess.
- 0db532a0 8y agoAnyone who writes like that needs to have a chat with Uncle Bob.
- arcticbull 8y agoHaha, that's fair :) I'm trying to convey that sometimes as an end developer, you pick a number of third party libraries based on what they do -- not what their API definition looks like. Then you end up in an awkward mix-n-match of DSLs that are hard to reason about without a deep knowledge of each because the operators you normally key off of are redefined. Maybe thats why I'm not a C++ developer haha.