3 ms·

The truth is that rust is in its infancy its all guesses at this point. Go didn't attract c++ people as people first guessed.

bsder 11y ago
I saw them talking about that, but it's completely obvious. Nobody today is running C/C++ unless they need either A) complete speed or B) bare metal. Go can't do either, so there was going to be very little transfer from C/C++ to Go.
- prewett 11y ago
  C++ is still mostly what I use, but I need neither speed nor bare metal. Maybe add C) people doing UI and applications? There aren't many other good options: Java: UI looks terrible; it's annoying living in Noun-land when CPUs are, if anything, more about verbs than nouns; and running properly on Windows is not trivial. C#: Up until recently, not cross-platform unless you're ok with Mono. (But, might be worth looking in to now) Python: great for scripts and experiments. The lack of static typing is a real problem when working with code other people wrote. Also, UI is not a strong point. Go: what UI libraries? (I'm sure they exist) Objective-C: even on iOS/Mac-only projects, I still prefer C++, because it's so much easier to use STL objects than NS data structures. C++: you can pretty much get it done, and often you can use Qt to get it done quickly and cross-platformy. I'm hoping Rust will be the C++ I always wanted.
  - kibwen 11y ago
    Most GUI toolkits for Rust are in their infancy, but I hear that Gnome will be working on integrating Rust with GObject this year, which should allow Rust to leverage Gtk: https://wiki.gnome.org/GUADEC/2015/BOFs/Rust https://wiki.gnome.org/GUADEC/2015/BOFs/Rust Some preliminary work towards this: https://github.com/gi-rust/glib-sys https://github.com/gi-rust/glib-sys
    - bsder 11y ago
      > I hear that Gnome will be working on integrating Rust with GObject this year, which should allow Rust to leverage Gtk: This disappoints me greatly. The idea of an object hierarchical GUI is not a guaranteed given. It causes things like "primary UI thread" which doesn't need to exist anymore. It is a reflection of a time when memory and CPU was more scarce. In the face of massively parallel CPU's and huge memory, a tile-based, constraint GUI with publish-subscribe is probably a much better choice. This is especially true with a language that promotes concurrent programming. I suspect, sadly, that we're simply going to continue down the same broken, single-threaded UI path because of the installed codebases.
  - rhodysurf 11y ago
    I am a Qt/C++ programmer by day and i have been looking at rust and there some bindings to GTK and such, but to me, nothing really comes close to the cross platform-ness of Qt. There seem to be simple QML bindings for Rust too, but thats not really the same.
  - pjmlp 11y ago
    > Java: UI looks terrible Java GUIs can be made to look quite nice, just many developers never spend the time to go beyond the default settings. If anything, the old Filthy Rich Clients blog from Chet Haase , Romain Guy was full of examples how to achieve great UIs in Java. However most 9to5ers don't read such sources of information.
- deleted 11y ago
  [deleted]

bsder 11y ago

I saw them talking about that, but it's completely obvious. Nobody today is running C/C++ unless they need either A) complete speed or B) bare metal. Go can't do either, so there was going to be very little transfer from C/C++ to Go.

prewett 11y ago
C++ is still mostly what I use, but I need neither speed nor bare metal. Maybe add C) people doing UI and applications? There aren't many other good options: Java: UI looks terrible; it's annoying living in Noun-land when CPUs are, if anything, more about verbs than nouns; and running properly on Windows is not trivial. C#: Up until recently, not cross-platform unless you're ok with Mono. (But, might be worth looking in to now) Python: great for scripts and experiments. The lack of static typing is a real problem when working with code other people wrote. Also, UI is not a strong point. Go: what UI libraries? (I'm sure they exist) Objective-C: even on iOS/Mac-only projects, I still prefer C++, because it's so much easier to use STL objects than NS data structures. C++: you can pretty much get it done, and often you can use Qt to get it done quickly and cross-platformy. I'm hoping Rust will be the C++ I always wanted.
- kibwen 11y ago
  Most GUI toolkits for Rust are in their infancy, but I hear that Gnome will be working on integrating Rust with GObject this year, which should allow Rust to leverage Gtk: https://wiki.gnome.org/GUADEC/2015/BOFs/Rust https://wiki.gnome.org/GUADEC/2015/BOFs/Rust Some preliminary work towards this: https://github.com/gi-rust/glib-sys https://github.com/gi-rust/glib-sys
  - bsder 11y ago
    > I hear that Gnome will be working on integrating Rust with GObject this year, which should allow Rust to leverage Gtk: This disappoints me greatly. The idea of an object hierarchical GUI is not a guaranteed given. It causes things like "primary UI thread" which doesn't need to exist anymore. It is a reflection of a time when memory and CPU was more scarce. In the face of massively parallel CPU's and huge memory, a tile-based, constraint GUI with publish-subscribe is probably a much better choice. This is especially true with a language that promotes concurrent programming. I suspect, sadly, that we're simply going to continue down the same broken, single-threaded UI path because of the installed codebases.
- rhodysurf 11y ago
  I am a Qt/C++ programmer by day and i have been looking at rust and there some bindings to GTK and such, but to me, nothing really comes close to the cross platform-ness of Qt. There seem to be simple QML bindings for Rust too, but thats not really the same.
- pjmlp 11y ago
  > Java: UI looks terrible Java GUIs can be made to look quite nice, just many developers never spend the time to go beyond the default settings. If anything, the old Filthy Rich Clients blog from Chet Haase , Romain Guy was full of examples how to achieve great UIs in Java. However most 9to5ers don't read such sources of information.
deleted 11y ago
[deleted]