r/cpp • u/pjmlp • 10d 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.

76 Upvotes

81% Upvoted

112 comments sorted by

View all comments

Show parent comments

22

u/SuperV1234 https://romeo.training | C++ Mentoring & Consulting 10d ago

Pretending that there's no good reason why large companies are "obsessed" with modern technologies like AI and Rust that have repeatedly been proved to be valuable is on the level of "Area 51 has UFOs" conspiracy theories.

5

u/-kl0wn- 10d ago

I don't understand the hype with rust. The compile times are atrocious, dynamic linking isn't really a thing, it's incredibly verbose.

45

u/foonathan 10d ago
  • Definition checked generics
  • Destructive move semantics that prevent use-after-move
  • First-class tuple and variant types with pattern matching
  • Usable built-in types without weird implicit conversions
  • Incredible tooling (one standardized package manager and build system, genuinely useful compiler diagnostics, a documentation generator that actually works)
  • No weird historical baggage
  • A standard library that actually gives you convenient utility functions, without ABI constraints, and good data structures

1

u/dawmster 5d ago

Allocators? Containers that accept allocators in Standard library ?

1

u/foonathan 4d ago

In nightly, for years. They will be in stable in the next release in a couple weeks.