Earlier quoted context omitted.
Just learned that LLVM, GCC, CUDA, HPC, HFT and the whole games industry aren't serious new development.
.. is it new development?
I guess, unless you're into retro-gaming.
Carbon Language: An experimental successor to C++
171–180 of 521 posts
Re: Carbon Language: An experimental successor to C++
#172Earlier quoted context omitted.
As far as I'm concerned, C++ is there for legacy purposes only. There are some nice frameworks and tools using it, sure. Yes, you are required to learn it if you are studying CS. Any serious new development today is done using more modern languages such as Rust (i.e.: the linkerd service mesh proxy [1] for encrypted pod communication in a k8s cluster). As even the Linux kernel is slowly transitioning to using Rust [2…
Just learned that LLVM, GCC, CUDA, HPC, HFT and the whole games industry aren't serious new development.
> I guess, unless you're into retro-gaming.
So new (same-)old development then?
Re: Carbon Language: An experimental successor to C++
#173Earlier quoted context omitted.
> A key example of this is the committee's struggle to converge on a clear set of high-level and long-term goals and priorities aligned with ours [ https://wg21.link/p2137 ]. I was frankly shocked by that goals and priorities document. The non-goals section reads like an open declaration of war against anyone whose use cases for C++ differ from GOOG and NVDA. My interpretation of Carbon is that since GOOG failed to t…
> GOOG and NVDA Why use these stock index abbrevs (or whatever they are) in this context here? GEEZ! To the topic, it sounds a bit grumpy. If we look at languages and how many evolve... many suffer the phenomenon that they almost all are Turing complete, and try to gain concise (or simple understandable) expressiveness somehow, and then they try to not break compatibility too much to varying degrees - net result: the…
It's an implication that the driving force for the development is money. By the way, jump on the GEEZ train, that stock's gonna go through the roof!
Re: Carbon Language: An experimental successor to C++
#174Well, `returned var` is totally unnecessary - why didn't they borrow the syntax from Go?!
Re: Carbon Language: An experimental successor to C++
#175Earlier quoted context omitted.
Designing a language to interop well with a single language is short sighted in my opinion. I want a clean ffi that I know will be able to iterop with Swift, Typescript, C#, C++, C, python etc... In my current project I'm currently using Rust/protobuff to do all of this and it rarely gets in my way of how I want to do things.
The major usecase for Carbon is to advance Google's internal, multi-billion line, C++ codebase. As nice as a greenfield language with a clean ffi would be, "extremely close ties to C++" is Carbon's primary benefit.
sorry for nitpicking what is likely intentional exaggeration, but multi billion can’t be anywhere near accurate, right?
Re: Carbon Language: An experimental successor to C++
#176Earlier quoted context omitted.
Isn't this one of the most prominent features in D? Sounds like they're trying for something very much like D, while starting closer to current C++.
D is closer to this than this rust rip-off
Yeah, why not D? It's such a good, mature alternative to C++, albeit not widely adopted.
Re: Carbon Language: An experimental successor to C++
#177Re: Carbon Language: An experimental successor to C++
#178Why use Rust syntax (fn, x:Type, ...)? Syntax is one thing that is not so well-designed in Rust (in my opinion). Also, with the stated goals, it seems a bit unnecessary to overhaul C++ syntax, but then I found no explanation why syntax was changed. So what's wrong with C++ syntax if your goal is a successor of C++? This now looks to me like a Rust-- instead of a C++++, which is a picture they might not want to give r…
Indeed, syntax only a mother could love. (Swift, I am looking at you, too.)
Re: Carbon Language: An experimental successor to C++
#179Earlier quoted context omitted.
I still haven't seen a cross-platform production level GUI app written in Rust. All the time, it is C++ these companies use for these apps, especially having millions of users and generating multi-millions or hundreds of millions of dollars.
We may need more time. IIRC, Firefox is incorporating some code written in Rust, and there's also Servo.
Mozilla laid off Servo's developers and a lot of the core Firefox Team 2 years ago. Servo is dead
Re: Carbon Language: An experimental successor to C++
#180Earlier quoted context omitted.
The syntax looks a lot like Rust, though. I'm surprised they made such a break when there explicit goal is to make migration from C++ as easy as possible. Also, Rust (from my biased point of view) is currently on its way to become the standard low-level language, so I'm not too confident that Rust-but-with-OO is enough of a selling point.
Considering the seemingly endless list of things that deliberately don't break with the c++ legacy, new syntax is almost the only change left. And if you were about to give c++ a syntax reboot, why wouldn't you look at what successful other modern syntaxes are doing? "c++, but in a syntax for people accustomed to rust instead of in a syntax for people accustomed to C" sounds like a perfectly reasonable approach. Your…
> I suspect that the author (authors?) wouldn't disagree at all with "use Rust when possible, Carbon when you can't"
That is in fact explicitly stated on the Carbon introduction:
"Existing modern languages already provide an excellent developer experience: Go, Swift, Kotlin, Rust, and many more. Developers that can use one of these existing languages should."