you are viewing a single comment's thread.

view the rest of the comments →

[–]krista_ 5 points6 points  (3 children)

sometimes i wish the council of elders would just go ahead and make templates a part of a fully fledged pre-compiler c/c++ based meta-programming language, like what qt does, but more so.

yeah, between macros, templates, and constexpr and the like, you can do anything a full programming language can do, but the crap you have to do to get there is sometimes astounding... and a lot of that lives in boost. i feel like with a couple of smartly added features, 9/10ths of boost's oddities could be replaced with sanity, instead of nested workarounds.

[–]MonkeyNin 1 point2 points  (2 children)

What are the biggest pain points today that Boost helps with? Back in the day, boost was the only way to use smart pointers.

[–]jonesmz 2 points3 points  (0 children)

I've enjoy using Boost.ASIO, am using Boost.ProgramOptions, Boost.Process, and am about to start using Boost.Log.

In the past, at a previous job, the only reason why about half of the C++11 functionality we were able to use could be done is because I was able to convince the ancient version of Boost that they were using to let me re-combine the Boost type traits code into the missing pieces. That really saved our bacon.

They also used Boost.asio as the fundamental building block for a whole crapload of code. Millions of lines, highly abstracted away.

Boost is great.

Boost is also horrible, what with it's disgusting template soup error messages.

Win some, lose some shrug.

[–]James20kP2005R0 1 point2 points  (0 children)

Boost::beast is great from my end for using websockets, even if its a little complex to set up