Live data from Hacker News

Atria: A toolkit for modern C++ development from Ableton

abletonag.github.io

1–10 of 39 posts

Re: Atria: A toolkit for modern C++ development from Ableton

#5
post #2

First reaction: "Header only - This is great!" Then I read: "Dependencies boost". OK, moving on...

Interesting...

There are not many parts depending on boost and we could make it entirely optional [1] (it would be still be nice for people wanting to use atria::variant::match in combo with boost::variant, optionally).

Could you elaborate on why boost is a total no-go for you?

https://github.com/AbletonAG/atria/search?utf8=%E2%9C%93&q=b...

Re: Atria: A toolkit for modern C++ development from Ableton

#6
post #2

First reaction: "Header only - This is great!" Then I read: "Dependencies boost". OK, moving on...

Interesting... There are not many parts depending on boost and we could make it entirely optional [1] (it would be still be nice for people wanting to use atria::variant::match in combo with boost::variant, optionally). Could you elaborate on why boost is a total no-go for you? https://github.com/AbletonAG/atria/search?utf8=%E2%9C%93&q=b...

As another data point, I don't find the Boost dependency an issue at all. Boost libs are just so useful...

Re: Atria: A toolkit for modern C++ development from Ableton

#9
post #2

First reaction: "Header only - This is great!" Then I read: "Dependencies boost". OK, moving on...

Honest question from someone who hasn't done C++ in a very long time: why is "header only" a good thing?

From the popular (in game development circles, at least) stb libraries:

>Why single-file headers?

>Windows doesn't have standard directories where libraries live. That makes deploying libraries in Windows a lot more painful than open source developers on Unix-derivates generally realize. (It also makes library dependencies a lot worse in Windows.)

>There's also a common problem in Windows where a library was built against a different version of the runtime library, which causes link conflicts and confusion. Shipping the libs as headers means you normally just compile them straight into your project without making libraries, thus sidestepping that problem.

>Making them a single file makes it very easy to just drop them into a project that needs them. (Of course you can still put them in a proper shared library tree if you want.)

>Why not two files, one a header and one an implementation? The difference between 10 files and 9 files is not a big deal, but the difference between 2 files and 1 file is a big deal. You don't need to zip or tar the files up, you don't have to remember to attach two files, etc.

https://github.com/nothings/stb/

Re: Atria: A toolkit for modern C++ development from Ableton

#10
post #2

First reaction: "Header only - This is great!" Then I read: "Dependencies boost". OK, moving on...

Interesting... There are not many parts depending on boost and we could make it entirely optional [1] (it would be still be nice for people wanting to use atria::variant::match in combo with boost::variant, optionally). Could you elaborate on why boost is a total no-go for you? https://github.com/AbletonAG/atria/search?utf8=%E2%9C%93&q=b...

Your library looks pretty neat, but I have an aversion to boost too. I love that c++ is slowly absorbing the best bits so I can detach myself from it -- it's a great library but is just so monolithic. And whenever I need a non-header-only library from it I always seem to struggle through the windows b2/bjam/whatever process to build them.

Minor: there are a few mistakes on the landing page: 'welcome', 'implementation', etc.

Post reply on HN