@taschenorakel@flutter@slint@qt#rust is not that hard for a C++ dev IMHO… the biggest change is that you need to learn to trust the compiler: It does have a point when it flags something, even when you go “that is wrong, I do that in C++ all the time and it never caused any problem”.
Compile times are not that much worse than C++ and are actually improving – slowly.
But #slint has great #cpp support, too, so just use that till your team is ready to adopt rust.
@taschenorakel @flutter @slint @qt I’ll always argue for #rust + #slint, but I am heavily biased.
@hunger I’d argue this team here lacks the required skill level to take advantage from Rust. (Well, and I lake the patience for Rust’s compile times).
I still like alot what you guys are doing.
@flutter @slint @qt
@taschenorakel @flutter @slint @qt #rust is not that hard for a C++ dev IMHO… the biggest change is that you need to learn to trust the compiler: It does have a point when it flags something, even when you go “that is wrong, I do that in C++ all the time and it never caused any problem”.
Compile times are not that much worse than C++ and are actually improving – slowly.
But #slint has great #cpp support, too, so just use that till your team is ready to adopt rust.