12,138 karma · joined February 8, 2013
Cargo is great if you're starting from nothing, but it's not very pragmatic to ignore all your existing code and experience and form another ecosystem within your organization. There's probably a limit to how many code ecosystems you want in your org, even in large and well-funded ones.
You can't code taste into every tool that might want to help you edit your source code.
That being said, almost all formatters have ways to tell them to go away in especially important stretches of code, with the tradeoff being ugly generated code fixups for that need hand massaging every time.
And Rust has the same issues, at least when shipping or consuming libraries with C APIs is in the picture.
Or, in other words, do we need hundreds of thousands of curricula? Doesn't that leave a lot of by definition below average curricula. Would selecting among even dozens of well-designed options make sense instead?
This is where public schooling is hypocritical. There are various forms of education about race, gender, etc., but almost no mandatory education on religion?
I'm not saying indoctrination, but education. Shouldn't everyone have a basic understanding of the history and tenets of Buddhism? Atheism? Hinduism? And so on? I think so. Even if the prism of importance is postmodern and focuses on respect fo others' self-identification, religion is clearly a major aspect in self-identification or we wouldn't treat the subject as controversial.
It's also kind of a boring question because there's no experiment we could run to explain how creation miracles worked. It's definitely a fountain of controversy, though.
Point being, the Unix philosophy has its own issues, especially around the foundations of how it all glues together.
So I guess both Stewart and Apple get some credit there. But Apple isn't making it clear who is deciding Stewart crossed a line and how that happened. Maybe it's a government? Maybe it's an exec? I can fault them for that.
Viable designs to support header units was still up in the air until six months ago or so. I don't see significant investment for that happening in GCC or Clang still, especially with respect to how build systems are supposed to understand how to invalidate BMIs and such. Current trajectory is that we'll consider header units a niche technology or even an unfinished idea.
Well, the daemon-based approach won't really work with certain kinds of distributed build and caching systems. I suspect it will work for a lot of use cases though. It's also problematic if you want to parse code without a build system as such. Does every analysis tool and IDE need to add support for that GCC specific API?
But the p1689 approach is implemented the same way for all three major compilers. And it should be reasonably adoptable by anything else that might want to work with CMake and other build systems that choose to support p1689.
The lib is still the lib. The header files are replaced with module interfaces. It's just that those are probably going to be shipped with some parsing instructions, like required preprocessor flags, the C++ version used, and that sort of thing.
Only Microsoft implements that so far. I gather EDG (which powers IntelliSense) has been at least researching support for consuming IFC files.
I'm not aware of anyone sponsoring work in Clang or GCC to add IFC support.
How does build2 understand module dependencies without that?
But integration and tooling is required for any major amount of adoption. IntelliSense has to work. Existing LSPs have to work.