3 ms·

What’s being ‘sold’ is the speed of Rust not the novelty of the language choice

rwmj 5y ago
Why would speed matter for something that runs a few regexps over some commit messages once a month? I would have chosen Perl for this task: good enough speed for the task, excellent built-in support for regexps, templating libraries like the Template Toolkit, and flexibility around things like loading custom modules at runtime and parsing configuration.
- jstummbillig 5y ago
  Got to admire how smoothly we went from "Props for not selling language x for this" to "I am selling language y for this" in just 3 consecutive posts.
  - ExtraE 5y ago
    Language choice is a legitimate decision, debating which one to use is a legitimate topic. Selling an-already existing product based on its language is questionable, as the parent pointed out.
- judge2020 5y ago
  It could matter in edge cases, perhaps someone runs this on google3 or the linux kernel and it takes 10 seconds versus a minute+ on something like Perl (not sure if that's the case).
  - rwmj 5y ago
    I agree. If that's really one of the requirements then Rust or C++ or OCaml or something like that would make a lot of sense. Also I'd like to add to my original comment above: I don't care at all that this is implemented in Rust. Good on you. Open source software goes where the developers go, and isn't dictated by anything except what the developers want to do.
- handrous 5y ago
  We don't need more of the "git-[whatever]" commands to be in scripting languages. It's hard enough to bundle, distribute, and support as it is (especially on Windows). Though, yes, parts of it are already Perl so that probably would have been fine, but still a move in the wrong direction.
lhorie 5y ago
Saying "written in Rust" as a proxy for performance is a bit like saying "X in Y kb" in JS-land for the same reason. It says nothing about actual performance. One needs to show benchmarks if they want to have a convincing performance argument.

rwmj 5y ago

Why would speed matter for something that runs a few regexps over some commit messages once a month? I would have chosen Perl for this task: good enough speed for the task, excellent built-in support for regexps, templating libraries like the Template Toolkit, and flexibility around things like loading custom modules at runtime and parsing configuration.

jstummbillig 5y ago
Got to admire how smoothly we went from "Props for not selling language x for this" to "I am selling language y for this" in just 3 consecutive posts.
- ExtraE 5y ago
  Language choice is a legitimate decision, debating which one to use is a legitimate topic. Selling an-already existing product based on its language is questionable, as the parent pointed out.
judge2020 5y ago
It could matter in edge cases, perhaps someone runs this on google3 or the linux kernel and it takes 10 seconds versus a minute+ on something like Perl (not sure if that's the case).
- rwmj 5y ago
  I agree. If that's really one of the requirements then Rust or C++ or OCaml or something like that would make a lot of sense. Also I'd like to add to my original comment above: I don't care at all that this is implemented in Rust. Good on you. Open source software goes where the developers go, and isn't dictated by anything except what the developers want to do.
handrous 5y ago
We don't need more of the "git-[whatever]" commands to be in scripting languages. It's hard enough to bundle, distribute, and support as it is (especially on Windows). Though, yes, parts of it are already Perl so that probably would have been fine, but still a move in the wrong direction.

lhorie 5y ago

Saying "written in Rust" as a proxy for performance is a bit like saying "X in Y kb" in JS-land for the same reason. It says nothing about actual performance. One needs to show benchmarks if they want to have a convincing performance argument.