4 ms·

My biggest issue with both perl and python (apart from no static checking) is third-party libraries: 1. I definitely want to use third-party libraries, so I do

by gwd 3y ago

My biggest issue with both perl and python (apart from no static checking) is third-party libraries: 1. I definitely want to use third-party libraries, so I don't have to re-invent the wheel 2. I hate having to install and manage third-party libraries on all systems where I might want to run something. After using golang and rust, it's really painful to go back.

superkuh 3y ago
>2. I hate having to install and manage third-party libraries on all systems where I might want to run something. I feel the same way. Rust is pretty bad in this sense because you have to install an entire third party compiler and toolchain from outside of your repositories. Usually recommend in the form of, >curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs https://sh.rustup.rs | sh And if you don't install the third party rustc from out of repos your rustc is only able to compile code written $now till about $now + 3 months. After using perl it was really painful to try to compile random rust code I found. It's not that it's impossible to write forwards compatible rust, it's just that rust devs are mostly hostile towards it. Reactions to this comment will be, "3 months is too old to expect things to compile. You're holding back progress." And that's a legit POV. But one I'm glad Perl doesn't share.
- inferiorhuman 3y ago
  Typically I dislike having to be forced into a package manager's version of a given language. For example I recently upgraded ansible on my old MacBook and brew decided that it had to install its own version of rust which meant compiling it from scratch. 12GB later and I got ansible installed. Yuck. Likewise I've found CPAN to usually get out of my way… but at least in FreeBSD land I've not had to fight perl packages too much. And I've definitely been missing having Perl in the FreeBSD base system recently. And if you don't install the third party rustc from out of repos your rustc is only able to compile code written $now till about $now + 3 months. If you're not doing things that rely on nightly you generally get a lot more than three months. The catch is, of course, that a lot of things depend on nightly.
  - superkuh 3y ago
    I'm not a Rust programmer. I am a person who compiles and uses programs other people write. I do not ever plan on updating my rustc compiler every day. But yeah, the Rust ecosystem is uniquely geared towards that kind of behavior and it makes using to code written for those assumptions useful for a very limited, ~3 month, time span.
philote 3y ago
You could always use a tool that compiles your Python or Perl program into a standalone executable.
donaldihunter 3y ago
Golang and Rust are not any better at scale. Just try resolving go dependencies in a Kubernetes ecosystem project.

by gwd 3y ago

superkuh 3y ago

>2. I hate having to install and manage third-party libraries on all systems where I might want to run something. I feel the same way. Rust is pretty bad in this sense because you have to install an entire third party compiler and toolchain from outside of your repositories. Usually recommend in the form of, >curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs https://sh.rustup.rs | sh And if you don't install the third party rustc from out of repos your rustc is only able to compile code written $now till about $now + 3 months. After using perl it was really painful to try to compile random rust code I found. It's not that it's impossible to write forwards compatible rust, it's just that rust devs are mostly hostile towards it. Reactions to this comment will be, "3 months is too old to expect things to compile. You're holding back progress." And that's a legit POV. But one I'm glad Perl doesn't share.

inferiorhuman 3y ago
Typically I dislike having to be forced into a package manager's version of a given language. For example I recently upgraded ansible on my old MacBook and brew decided that it had to install its own version of rust which meant compiling it from scratch. 12GB later and I got ansible installed. Yuck. Likewise I've found CPAN to usually get out of my way… but at least in FreeBSD land I've not had to fight perl packages too much. And I've definitely been missing having Perl in the FreeBSD base system recently. And if you don't install the third party rustc from out of repos your rustc is only able to compile code written $now till about $now + 3 months. If you're not doing things that rely on nightly you generally get a lot more than three months. The catch is, of course, that a lot of things depend on nightly.
- superkuh 3y ago
  I'm not a Rust programmer. I am a person who compiles and uses programs other people write. I do not ever plan on updating my rustc compiler every day. But yeah, the Rust ecosystem is uniquely geared towards that kind of behavior and it makes using to code written for those assumptions useful for a very limited, ~3 month, time span.

philote 3y ago

You could always use a tool that compiles your Python or Perl program into a standalone executable.

donaldihunter 3y ago

Golang and Rust are not any better at scale. Just try resolving go dependencies in a Kubernetes ecosystem project.