News for hackers. Stuff that matters.
Re:CIDLib: C++ Development Environment by gok on Saturday March 09, 2019 @08:07PM (#19349591)
It's funny you mention JSON parsers and Boost in particular. The Boost JSON parser is an abomination. It's written as a parser generator in template code, so any file which includes it gets about 10 seconds of compile time just for that. It also blatantly violates the JSON spec and gives little to nothing in terms of parse error messages. Oh and until recently it was neither thread safe nor reentrant (you could not parse two JSON files on two different threads in the same process because it used shared global state for all parsing).

I remain baffled that anyone uses boost for anything in production.

Re:CIDLib: C++ Development Environment by AboutTheWhisles on Saturday March 09, 2019 @08:33PM (#19349668)
I'm sure there are good parts to boost. I have no idea what they are, but just by sheer quantity, something must be worth using.
Re:CIDLib: C++ Development Environment by stochastic_monk on Monday March 11, 2019 @01:44AM (#19356935)
You’re right. For a few examples:

Smart pointers (unique, shared, auto), now part of the standard <random> The new Filesystem TR unordered_{map,set} enable_if/type_traits

Some is probably less important, but they’ve been instrumental in moving the C++ standard library forward.

Re:CIDLib: C++ Development Environment by AboutTheWhisles on Monday March 11, 2019 @11:03AM (#19359454)
Those were influential and have a had a very positive effect on modern C++ without a doubt. Now that they are part of the standard though there are fewer reasons to use anything from boost, largely because it is a double edged sword of compile times and dependencies.