The article claims nobody’s tried a language natively compatible with C++, but that’s the approach that Google’s Carbon is taking: https://github.com/carbon-language/carbon-lang
Carbon is on my list of things to experiment with.
Cooperative C++ Evolution – Toward a TypeScript for C++
11–20 of 209 posts
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#12I'm confused doesn't C# fill this role?
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#13The article claims nobody’s tried a language natively compatible with C++, but that’s the approach that Google’s Carbon is taking: https://github.com/carbon-language/carbon-lang
Carbon is disappointing and feels like a missed opportunity. It feels more like a syntax refresh. C/C++ desperately need a safety overhaul. I work in the embedded functional safety space. Rust has shown it can be done. Not having lifetime/borrowing support or something that achieves the same thing from the start gives the impression nothing has been learned in the last decade.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#14The article claims nobody’s tried a language natively compatible with C++, but that’s the approach that Google’s Carbon is taking: https://github.com/carbon-language/carbon-lang
And Circle and cppfront. Edit: of course this is about cppfront :)
Indeed, I think the article is about cppfront.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#15I'm confused doesn't C# fill this role?
C# does not transpile to C++, so no. You are still left with the .net runtime, garbage collection, etc.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#16Neither TypeScript nor Dart are relevant technologies to people interested in C++.
It's weird to refer to these arguably bad web technologies to market an unrelated initiative.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#17Cppfront: https://github.com/hsutter/cppfront
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#18I'm confused doesn't C# fill this role?
No, C++ developers generally use it to avoid garbage collection.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#19I’m not a frontend guy but heard that typescript is already falling off and contentious at this point. Is it truly something that’s going to stay?
IMO the only way TyoeScript is going away is if all the useful components end up getting merged into JS. It’s simply too useful.
Re: Cooperative C++ Evolution – Toward a TypeScript for C++
#20I’m not a frontend guy but heard that typescript is already falling off and contentious at this point. Is it truly something that’s going to stay?
Typescript has a lot of momentum on all fronts and is almost certainly the future of Javascript. The big problem is that it still requires transpilation, which can set up all sorts of shitty traps. Not to mention that the Javascript ecosystem in general is a horrendous mess, which Typescript on its own can’t fix.
The future of JavaScript is in the past. Get rid of all the stupid transpilers and frameworks and just use plain JavaScript in the browser.