4 ms·

> So that only really leaves ATS and Rust, and rules out Nim, D, Zig, Jai I don't have a problem with GC so Nim/D are on the table. ATS is a pain in the ass bu

• oconnor0 8y ago
  I don't think I'd call Rust user friendly.
  • vmchale 8y ago
    If the problem is the type system/borrow checker, it's simply a question of experience.
    • pjmlp 8y ago
      Not when writing GUI like code, to the point that the Rust team acknowledges that additional work needs to be done after NLL lands on stable. http://smallcultfollowing.com/babysteps/blog/2018/11/01/after-nll-interprocedural-conflicts/ http://smallcultfollowing.com/babysteps/blog/2018/11/01/afte... http://smallcultfollowing.com/babysteps/blog/2018/11/10/after-nll-moving-from-borrowed-data-and-the-sentinel-pattern/ http://smallcultfollowing.com/babysteps/blog/2018/11/10/afte... So while Rust is much more productive than ATS or Cyclone, there is still room of improvement for that experience.
      • floatboth 8y ago
        There's always room for improvement, but speaking of GUI, gtk-rs is pretty usable already.
        • pjmlp 8y ago
          It is, if you don't mind sprinkling your code with Rc<RefCell<item>> everywhere, as means to access widget struct members in callbacks.
• eggy 8y ago
  I find Zig much more user friendly than Rust. I have been able to do much more with Zig than Rust in one-tenth the time. I am not writing any code that requires the guarantees Rust may provide, and Zig seems to make it easier to write safer C-type code to boot.
  • vmchale 8y ago
    Zig doesn't force you to free all your memory (which occasionally good), so there are whole classes of errors that Rust/ATS avoid that are possible in Zig.