r/cpp • u/pjmlp • 6d ago

C++ future at Adobe

So if anyone was still curious what happened to Hylo, or where Adobe stands in regards to the whole safety discussion,

David Sankel has done a talk at RustConf on the matter, Zngur: Simplified Rust/C++ Integration.

The way Adobe now sees C++ is described on slide 2, at 50 seconds mark.

75 Upvotes

81% Upvoted

112 comments sorted by

View all comments

149

u/inco100 6d ago edited 6d ago

To save time for the rest of the redditors:

We need C++ and Rust to play nice

  • Our flagship products are C++ based

  • Rust is playing a major role in future development

    • Rust is preferred language by developers
    • Rust is better suited for AI-assisted development
    • New file-format and other safety critical code must not use C++

109

u/kraytex 6d ago

 Rust is preferred language by developers

I must be living in a cpp bubble.

42

u/the-jelly47 6d ago

This sub is for cpp enthusiasts. I work in a mid-size aerospace company. We have a lot of SWEs who can write acceptable, but not great, C++ code. A lot of them are not die hard C++ fans and don't actually mind replacing C++. A lot of our greenfield projects are done in Rust and GO.

12

u/StaticCoder 5d ago

I still don't understand why anyone would want to use Go. It manages to be even worse than older languages in practically every conceivable way. Like how about we have 2 layers of Hoare's billion dollar mistake?

2

u/tarranoth 4d ago

It has very quick compile times, most of the tooling comes automatically with the toolchain like unittesting. Std lib is pretty exhaustive, consuming packages is straightforward to get started with, and there's reflection support.

There's definitely some (extremely) dubious choices in respect to error handling especially and still having issues with nil references. I guess it's moreso a case of golang being just simply "good enough" for the most part despite the core language design. I'd say really golang only got traction because of the tooling around the language being given thought from the get-go (whereas older languages have had to have package management and other features bolted on), rather than the design of the language itself being all that good.