| ▲ | int_19h 3 days ago |
| The reason why WHATWG was able to take over HTML like that is because all the people & companies that were actually making the browsers were onboard. With C++, my impression is that most implementers simply aren't interested. And, conversely, most people who might be interested enough to roll a new implementation have already moved to Rust and make better use of their time improving that. |
|
| ▲ | favorited 2 days ago | parent | next [-] |
| The browser companies weren't just onboard with WHATWG – they literally are WHATWG. The WHATWG steering committee is Apple, Google, Microsoft, and Mozilla. |
|
| ▲ | pjmlp 2 days ago | parent | prev | next [-] |
| You right, because the main companies with OSes that contribute to the surviving compilers that still care about ISO, are now focused elsewhere. Apple with Swift, Google with Go, Java/Kotlin, Rust, Microsoft with C#, Go, Java and Rust. Most modules stuff on GCC was done by a single developer, if I am not mistaken. Notice how Visual C++ blog posts are mostly about game development related improvements, Visual Studio tooling. Everyone else their compilers are still stuck on C++14, or C++17 if lucky. |
|
| ▲ | quotemstr 2 days ago | parent | prev [-] |
| You're right, but dammit, I wish you weren't. A world in which we can evolve existing large C++ codebases gradually towards safety instead of having to RRiR is a better world. There are lots of cool innovations C++ made that will just disappear from the Earth, forever, if C++ can't be made memory safe in the same sense Rust is. I mean, Rust doesn't even support template specialization. I don't think it's too late for someone to fork both C++ and Clang and make something that's actually a good synthesis of the old and the new. But yeah, the most likely future is one on which C++ goes the way of Fortran (which still gets regular updates, however irrelevant) and the energy goes into Rust. But I like to rage, rage, against the dying of the type based metaprogramming. |
| |
| ▲ | BoxFour 2 days ago | parent | next [-] | | > I don't think it's too late for someone to fork both C++ and Clang and make something that's actually a good synthesis of the old and the new. People have tried variants of this already: Carbon, for example. I don’t think anyone outside of Google uses it, though, and even within Google I suspect it’s dwarfed by regular C++. I don’t think C++ will become irrelevant for a long time. Recent standards have added some cool new features (like std::expected), and personally I feel like the language is better than ever (a biased opinion obviously). Memory management is still a huge elephant in the room, but I don’t think it’s becoming irrelevant. | | |
| ▲ | pjmlp 2 days ago | parent [-] | | Carbon is still being designed, and their goal is to migrate existing code, for Google purposes. They are quite open everyone else should use a managed language or Rust. |
| |
| ▲ | Yoric 2 days ago | parent | prev | next [-] | | FWIW, Rust doesn't have specialization yet because they're really hard to get right without introducing new undefined behaviors. This doesn't mean that it's not possible to achieve a safe subset of C++ that supports template specialization, but it suggests that we aren't going to see it any time soon. | |
| ▲ | tialaramex 2 days ago | parent | prev | next [-] | | Well like you said, Fortran didn't actually go anywhere. Fortan 77 is a terrible programming language, but you can't seriously claim it "disappeared from the Earth". Not that long ago tsoding was like "I should learn Fortran" and wrote a bunch of Fortran. Obviously from his perspective some things about Fortran are awful because it's very old, but it wasn't somehow impossible to do. There are a few really amazing things which have been achieved in C++ like fmt, a compile time checked, userspace library for arbitrarily formatting variadic generic parameters. That's like man on the moon stuff, genuinely impressive. Mostly though C++ is a garbage fire and so while it's important to learn about it and from it we should not keep doing that. | | |
| ▲ | Yoric 2 days ago | parent | next [-] | | > There are a few really amazing things which have been achieved in C++ like fmt, a compile time checked, userspace library for arbitrarily formatting variadic generic parameters. Anecdotal, but that's hardly unique to C++. So even if C++ were to disappear overnight (which we all agree won't happen), this wouldn't be a burning-library-of-Alexandria moment. | | |
| ▲ | tialaramex 2 days ago | parent [-] | | Well. What other examples of this feat are you thinking of? To me the things which come to mind are either compiler magic (e.g. C printf) or they rely on RTTI (e.g. Odin and similar C-like languages) and neither of those is what fmt does, they're "cheating" in some sense that actually matters. | | |
| ▲ | Yoric 2 days ago | parent | next [-] | | I co-implemented this in OCaml ~20 years ago, using no compiler magic (it did use a macro). Pretty sure that I've seen the equivalent in Haskell, too, and in variants of Scheme. Zig has it, too. And while, as you mention, the Rust implementation does use compiler magic, I'm pretty sure that it could be implemented as a macro, just more slowly. etc. | | |
| ▲ | Yoric 2 days ago | parent [-] | | (sorry, it wasn't you who mentioned it, but it was a good remark nevertheless :) ) |
| |
| ▲ | int_19h 2 days ago | parent | prev [-] | | https://doc.rust-lang.org/std/macro.format.html https://zig.guide/standard-library/formatting/ | | |
|
| |
| ▲ | pklausler 2 days ago | parent | prev [-] | | Judging Fortran by looking at Fortran 77 is preposterously uninformative. | | |
| |
| ▲ | fooker 2 days ago | parent | prev [-] | | > fork both C++ and Clang Great! What are you waiting for? If you try to answer that question, you'll also find why other similar projects are not finding much traction yet. |
|
