News for hackers. Stuff that matters.
Re:What should go into the C++ standard library (2018) by quotemstr on Wednesday February 27, 2019 @10:33PM (#19268788)
There are plenty of ways to organize C++ code, including several package managers. Why should a language -- a specification for a grammar and an abstract machine to run programs using it --- specify things so concrete as the way you download code? It might as well dictate what editor you use.

We need less, not more, conflation between languages, runtime environments, build systems, and package repositories. It's senseless to couple these concepts.

Re:What should go into the C++ standard library (2018) by vlovich123 on Wednesday February 27, 2019 @10:36PM (#19268799)
And yet having coded in Rust, Cargo solves all this bikeshedding. You can of course use your own build system but Cargo is pretty consistently used across the board which finally makes developing in a systems language as easy as Python (like virtualenv & pip but better).
Re:What should go into the C++ standard library (2018) by pjmlp on Thursday February 28, 2019 @02:47AM (#19269714)
Not really, cargo still doesn't provide an answer for binary libraries, and depending on how the workspace is configured and the projects one is compiling, it may end up compiling the same crates multiple times.
Re:What should go into the C++ standard library (2018) by blt on Friday March 01, 2019 @04:56AM (#19279178)
I feel ok about making binary libraries difficult. I want open source to be the easy path. I think the idea of abi compatibility forces a lot of unnecessary overhead on designs. Consider the radical design of TempleOS where everything is c source, jit compiled when run.
Re:What should go into the C++ standard library (2018) by pjmlp on Friday March 01, 2019 @05:09AM (#19279233)
Which is ok, assuming the Rust community doesn't want to be represented in such markets and doesn't have an issue waiting for cargo building always from source.

Just don't complain about adoption then.

Re:What should go into the C++ standard library (2018) by steveklabnik on Friday March 01, 2019 @11:12AM (#19282005)
I think you will be happy sooner rather than later, but I heard about it second hand, so I don’t want to say too much.
Re:What should go into the C++ standard library (2018) by pjmlp on Friday March 01, 2019 @11:36AM (#19282374)
Thanks, looking forward to it. :)