[–] 2 points 3 months ago (2 children)

Yes they do. I don't think it's totally unreasonable. Slow compile time is a big productivity drain. But it's not as bad as people often make out for Rust - in large part because compilation speed has at least doubled since Rust 1.0, but its reputation is still based on the 1.0 compile times.

And some specific projects do have substantially bad compile times. When your incremental compilation time is 20 seconds where in other languages it's instant... That's notably worse.

But I don't think it should be a deal breaker. C++ has dealt with similarly bad compile times for decades and people don't like it but it's never been enough for most of them to switch to another language.

  • source
  • parent
  • context
  • [–] 12 points 3 months ago (6 children)

    I am now pursuing opportunities to return to paid work on the Rust compiler. Wish me luck!

    Someone (Rust Foundation?) pay this man! Compilation speed is one of the few weaknesses of Rust and even though I think that in 95% of cases it's actually not that bad and people are just looking for an excuse to not use Rust, it would be great to remove that excuse. (And faster compilation is always nicer anyway!)

  • source
  • [–] 1 point 3 months ago

    Ah I see. That definitely depends on what it is and who your target audience is. I would say you can be quite technically proficient in Windows without being very familiar with the command line because a) the Windows command line sucks (even Powershell is kind of awful), and b) there are so many great GUI tools available, you almost never need to resort to the command line.

    So yeah, just depends where you want to draw the line and what it is that you're making.

  • source
  • parent
  • context
  • [–] 4 points 3 months ago (2 children)

    Depends on the windows user. But I dunno why you wouldn't offer it for Windows. You kind of have to go out of your way these days to make supporting Windows difficult, e.g. using OCaml or Perl or Bash or something.

  • source
  • [–] 1 point 3 months ago

    I've never seen a good answer to this question. Snapshot testing sucks. A 0.3% threshold can totally be too low for benign changes and too high to detect real bugs.

    Manual testing is probably the best option if you can afford it, but it's time consuming and tedious.

    I'm sure there are people working on AI for this. I wouldn't be too surprised if that's the best option but I haven't looked into any of that. Also you really want it to be deterministic and I'm not sure how you do that with AI easily.

  • source
  • view more: ‹ prev next ›