Genuinely serious since this is so much of a meme.

  • bluerabbit@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    4 years ago

    I really like Rust but there are lots of situations I wouldn’t use it. Some examples:

    • If I want very strict control over dependencies, a very small number of dependencies, or dependencies with specific/trusted origin.
    • If I was building software that won’t be actively maintained for years but might need adjustments later. The Rust ecosystem is a fast-moving target and upgrading a library could cause a huge cascade of other changes.
    • For the most hassle-free integration with an important library like Qt, particularly if a Qt GUI is the main point of my application.
    • Most web front-end. Using WASM to control the DOM with glue code is using a sledgehammer to crack a nut.
    • (?) Probably most event-driven apps like GUIs. Rust’s lifetimes mostly stay out of your way but they only work on the stack. Synchronisation between potentially multiple threads is very in-your-face and explicit, compared with say Java’s “synchronized” methods. It’s only early days for Rust GUI frameworks so I will wait and see. Maybe they’ll come up with something great.
    • AgreeableLandscape@lemmy.mlOPM
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 years ago

      I’m most curious about your thoughts on GUI apps: For Qt, is the main problem right now the fact that no complete bindings exist or is Rust fundamentally problematic for Qt integration? If Rust had a complete binding of Qt or GTK libraries, would you use Rust as opposed to the framework’s native language (C++ and C respectively)? What’s currently your favourite language for GUI development and what makes it suitable for GUI?

      www.areweguiyet.com says that “Rust’s expressiveness and high level abstractions make it ideal for building intricate and complex user interfaces.” What do you think of this?