3 ms·
There's too much friction for Rust to be the solution, unless there are drastic changes in the near future. None of Vulkan, Metal, GTK, Qt, Cocoa, Android, iOS,
by BaculumMeumEst 3y ago
There's too much friction for Rust to be the solution, unless there are drastic changes in the near future. None of Vulkan, Metal, GTK, Qt, Cocoa, Android, iOS, or Wayland have official Rust support, and maintaining the boundary is a non-trivial task.
My gut feeling is that a different language with less friction will gain more traction.
- IshKebab 3y ago"None of <list of enormous ancient systems> have official support for <new language>"
- BaculumMeumEst 3y agoI think that is a reductive dismissal of a real problem. Rust is intended as a C++ replacement, but interfacing to existing C and C++ code can be very messy, it’s not just simple language bindings. What I’m suggesting is that the work needs to be spread out or it’s not likely to happen.
- IshKebab 3y agoC is fairly effortless, but I agree C++ could be better. But hardly any languages integrate with C++ very well. Have you ever used SWIG? (Shudder...) I do agree it would be nice if it could. The cxx crate is ok but we could do a lot more. Maybe something like SWIG but based on LLVM so it actually works properly.