[deleted]
Atria: A toolkit for modern C++ development from Ableton
31–39 of 39 posts
Re: Atria: A toolkit for modern C++ development from Ableton
#32Earlier quoted context omitted.
I'm not the same person, but I don't use boost, and I avoid projects that depend on it, because every time I've used boost in the past it's always done dreadful things to the build time. Anything that uses boost always seems to compile at a glacial pace and then takes aeons to link. It's also not much fun in the debugger, should you happen upon it in a call stack or see one of its types in the watch window - but buil…
You have to be careful with what you pull in. But with precompiled headers I'm building a suite of 25 command line apps, all dependent on boost, in 22 seconds on a 2012 MacBook Air. gcc on Windows is similar. Microsoft doesn't even let you share precompiled headers across projects, but it's still building in under 20 seconds. There's a LOT of really idiotic C++ build scripts out there. I really don't know what some p…
20 seconds is not particularly impressive..
Re: Atria: A toolkit for modern C++ development from Ableton
#33Earlier quoted context omitted.
You have to be careful with what you pull in. But with precompiled headers I'm building a suite of 25 command line apps, all dependent on boost, in 22 seconds on a 2012 MacBook Air. gcc on Windows is similar. Microsoft doesn't even let you share precompiled headers across projects, but it's still building in under 20 seconds. There's a LOT of really idiotic C++ build scripts out there. I really don't know what some p…
20 seconds is not particularly impressive..
Neither is the hardware. The point is that I'm doing a clean build of an entire app in under a second. Which means the "boost tax" is also under a second.
You can certainly make a mess of things if you're not careful. Most people seem to.
Re: Atria: A toolkit for modern C++ development from Ableton
#34Earlier quoted context omitted.
You have to be careful with what you pull in. But with precompiled headers I'm building a suite of 25 command line apps, all dependent on boost, in 22 seconds on a 2012 MacBook Air. gcc on Windows is similar. Microsoft doesn't even let you share precompiled headers across projects, but it's still building in under 20 seconds. There's a LOT of really idiotic C++ build scripts out there. I really don't know what some p…
How complicated are these command line apps?
400-600k with symbols stripped.
I'm using boost/any, boost/iostreams/stream & tee, and boost/property_tree/json_parser. So obviously I'm not going nuts with things. But wanted to provide the data point.
Re: Atria: A toolkit for modern C++ development from Ableton
#35The novel part here is transducers and the funken package built on top of them, right? What are they used for, in your applications? The documentation is really terse and could use a few examples.
Re: Atria: A toolkit for modern C++ development from Ableton
#36Earlier quoted context omitted.
Worth noting that only the first two points there are relevant here, since these are not single file libraries. Also, the STB libraries work massively differently from C++ header only libs (#define STB_FOO_IMPLEMENTATION, for example). Also, fwiw Sean Barrett also has gone on record as saying that he's not really a fan of C++ before. I'm struggling to find a specific link, but it's not really a secret. (As a side not…
STB libraries are C not C++. Sean Barrett prefers C, basically. The header-only approach from Sean Barrett is quite a bit different than the header-only approach from C++: In C++ it means you will be pulling all the code all the time when importing a header. In C you will get the prototypes for the library. And in only one of the file you will #define STB_ _IMPL Anyhow STB libraries are a joy to work with, I urge any…
Ha, did you mean to reply to the parent comment? You basically repeated everything I said :) (agreed on all points, though)
Re: Atria: A toolkit for modern C++ development from Ableton
#37The novel part here is transducers and the funken package built on top of them, right? What are they used for, in your applications? The documentation is really terse and could use a few examples.
Yep, sorry about the state of the docs... hopefully it will improve over time. As the `status` section highlights, a lot of the stuff here is very green, but we wanted to open-source early and polish it along the way instead of waiting until everything is "done" ("done" doesn't make sense for an OSS project anywayzzz :-)
There will be a tutorial on the transducers stuff coming up at some point. That is the part that is under more active development indeed. We will also talk about that at CppCon next September.
Re: Atria: A toolkit for modern C++ development from Ableton
#38Earlier quoted context omitted.
Worth noting that only the first two points there are relevant here, since these are not single file libraries. Also, the STB libraries work massively differently from C++ header only libs (#define STB_FOO_IMPLEMENTATION, for example). Also, fwiw Sean Barrett also has gone on record as saying that he's not really a fan of C++ before. I'm struggling to find a specific link, but it's not really a secret. (As a side not…
STB libraries are C not C++. Sean Barrett prefers C, basically. The header-only approach from Sean Barrett is quite a bit different than the header-only approach from C++: In C++ it means you will be pulling all the code all the time when importing a header. In C you will get the prototypes for the library. And in only one of the file you will #define STB_ _IMPL Anyhow STB libraries are a joy to work with, I urge any…
>The header-only approach from Sean Barrett is quite a bit different than the header-only approach from C++:
I'm aware, but the practical advantages of having a library in a single source file apply no matter what the programming language.