boris

16 ms·

151.
by boris 6y ago
This is essentially embedding bits and pieces of a makefile into source code as ad hoc comments. Which is what happens when you don't have a proper, general-purpose build system.
152.
by boris 6y ago
Actually, rustc produce a crate metadata (those .rmeta files) which is all that's needed to start compiling dependent crates. Producing this metadata is pretty quick compared to producing the finished crate.
153.
by boris 6y ago
> There'd been a number of spectacular C++ project failures... And the most successful company of that era (Google) went ahead and implemented their product (the search engine) in C++...
154.
by boris 6y ago
You may want to check build2[1] then. As a bonus you also get a Cargo-like package/project manager (but with a real build system underneath). Full disclosure: I am involved with the project. [1] https://build2.org
155.
by boris 6y ago
We did start with C++ thinking (correctly, IMO) that if we can build C++, we can build pretty much anything. But build2 is a general-purpose build system, for example: https://build2.org/build2/doc/build2-build-sy
156.
by boris 6y ago
https://build2.org/build2/doc/build2-build-system-manual.xht...
157.
by boris 6y ago
I found it to be an "atmospheric" (for the lack of a better word) book -- you understand by feeling as much as by, well, direct understanding. Kind of like Master and Margarita (which some people also find pedestrian).
158.
by boris 6y ago
The need for speed is the direct result of worse is better.
159.
by boris 6y ago
Yes, just tried it the other day and it's great. Not a hint of acidity. Now need to decide which one I like best.
160.
by boris 6y ago
Second that. As much as I want to believe a $10k La Marzocco is absolutely essential to good espresso, a $100 Nespresso machine and Kazaar roast is the best espresso I've ever had.
161.
by boris 6y ago
FWIW, for the build2 project we host our own CI servers on premesis and the power supply is supplemented by a solar array. We have configured our daily package rebuild window to coincide with the maximum solar output so that on a sunny day
162.
by boris 6y ago
If you are interested, Peter Thiel's 0 to 1 has more on this and with more depth. As he says, we are the "indefinite optimists", expecting the future to become better somehow, rather than "definite optimists" that e
163.
by boris 6y ago
And the rest of the book deals with why it is more often than not painful. In summary, it's complexity. Brooks argues that software, being a pure thought-stuff, is also the most complex thing we attempt to build. And it's even wor
164.
by boris 7y ago
> ... maintained by people that believe they and their work are utterly infallible. Hence why to this date they have not made it possible to detect musl ... Yes, and they are every bit as fallible as anyone. Here is an example of a prett
165.
by boris 7y ago
Yes, this struck me as a crazy idea for C/C++ development, embedded or not. What if you save something intermediate not meant to be compilable/testable? I for example have a deeply ingrained habit of saving my changes all the time
166.
by boris 7y ago
> This is the bleeding edge; these devices have only been available for 13 weeks [...] Shouldn't these devices have been tested by AMD and motherboard manufacturers for months before they were released? Including on workloads like P
167.
by boris 7y ago
Good example of how we develop software these days: instead of fixing GNU make by ripping out that antiquated pipe-based jobserver and replacing it with proper multi-threaded parallelism[1], we rather optimize the operating system to make t
168.
by boris 7y ago
Interesting how compilation benchmarks do not scale at all from 24 to 32 to 64 core Threadrippers. Neither Linux kernel nor LLVM compilation. I wonder why it's so bad.
169.
by boris 7y ago
We (the build2 project) use it in our CI infrastructure for VM storage. For every build we make a snapshot of a VM, boot it, build, drop the snapshot, repeat. So we are talking about making/dropping snapshots every couple of minutes 24
170.
by boris 7y ago
Oh, there is plenty of drama on /r/cpp/.
171.
by boris 7y ago
> being in an exhausting fight against terrible odds by yourself [...] eat the shit necessary to do it I think (from experience) that's a pretty accurate way to describe a software startup. And so as you find yourself on the floor (
172.
by boris 7y ago
Thanks. Seeing that we are sharing ECC overclocking information, this post has some useful information for Kingston RAM: https://old.reddit.com/r/ASUS/comments/cw74rl/asus_pro_ws_x5...
173.
by boris 7y ago
Thanks for the info. Is this the same motherboard as OP?
174.
by boris 7y ago
Could you share the specs for your build, specifically the motherboard and RAM models. Also have you verified that ECC actually works? I am tempted to build something similar but AMD's wishy-washy ECC guarantees as well as Linux-specif
175.
by boris 7y ago
In build2 we do something similar for snapshot versioning between releases by incorporating the date and commit id into the pre-release component of semver. The result is a unique, properly ordered version for every commit in a project (we
176.
by boris 7y ago
> I often wonder how many of them could actually speak at depth, extemporaneously, about the subect of their talk or if their actual knowledge collides with the end of their slides. Was not my experience at CppCon at least. In fact, the
177.
by boris 7y ago
There is build2. It has "high-fidelity" (instead of hermetic) builds meaning that besides sources it keeps track of changes to options, compilers, etc. This gives you similar benefits at a fraction of the cost. There is no distrib
178.
by boris 7y ago
Here you go: https://www.infoq.com/presentations/os-rust/
179.
by boris 7y ago
You can go a step further and factor the build system core into a library and provide dynamically buildable/loadable modules. This way you can reuse the same core in several drivers (different frontends, build-by-convention like Cargo,
180.
by boris 7y ago
We did in build2[1]. Specifically, we have a notion of target type which may not be path or mtime-based. For example, one such target type is alias (something that is achieved in make with PHONY targets). So you could define, say, a url tar

More ›