4 ms·

I'm impressed that the reasoning was more than just "Rust is super cool."

by OccamsMirror 3y ago

booi 3y ago
Rust is wicked fast?
- rizky05 3y ago
  [dead]
- chambored 3y ago
  blazingly fast
- queuebert 3y ago
  Like any low-level language it can easily saturate a single core, and it has pretty easy concurrency syntax.
notRobot 3y ago
My understanding is that there are lots of functional reasons to use rust in such situations, which are why it's considered "super cool".
djha-skin 3y ago
Not really though. He keeps pointing out that he wants to integrate with Rust libraries, but it's actually pretty easy to write integrations between Rust and Python[1][2]. If that were the actual reason, there is a much better path of least resistance available. The only other type of given argument for moving to Rust was that the author enjoyed it, so it appears to be another "Rust is super cool" rewrite. It really speaks to the power of developer experience. People are willing to rewrite their entire application to be more comfortable. I know I am, only my language of choice is Common Lisp. 1: https://saidvandeklundert.net/learn/2021-11-18-calling-rust-from-python-using-pyo3/ https://saidvandeklundert.net/learn/2021-11-18-calling-rust-... 2: https://www.infoworld.com/article/3664124/how-to-use-rust-with-python-and-python-with-rust.html https://www.infoworld.com/article/3664124/how-to-use-rust-wi...
- moyix 3y ago
  The startup time mentioned is actually a big deal for me – I do record all of my terminal sessions (I even wrote a tool that uses his avt library to grep through the terminal logs, although I never got around to making it fast enough to be really useful: https://github.com/moyix/termgrep https://github.com/moyix/termgrep), and with the Python version I often lose the first few characters of my first command in a new terminal because asciinema is still starting up...
  - infogulch 3y ago
    You record all of your terminal sessions?! Sessions that are open for days? Commands that accidentally spew huge amounts of garbled nonsense to stdout multiple times because you're figuring a command out?
  - ku1ik 3y ago
    Maybe the new `asciinema convert demo.cast demo.txt` command (in 3.0, develop branch) would be useful to you? It converts the session to plain text using avt (which is now embedded in the CLI). You could grep like this: asciinema convert demo.cast /dev/stdout -f txt | grep foo
kelnos 3y ago
I'd usually agree, but the list of reasons involve integrating with Rust libraries, all of which it appears were written by the same author of asciinema. I think it just boils down to the author feeling a lot more productive and less frustrated in Rust than Python. Which is a perfectly fine reason to switch!

I'm impressed that the reasoning was more than just "Rust is super cool."

booi 3y ago

Rust is wicked fast?

rizky05 3y ago
[dead]
chambored 3y ago
blazingly fast
queuebert 3y ago
Like any low-level language it can easily saturate a single core, and it has pretty easy concurrency syntax.

notRobot 3y ago

My understanding is that there are lots of functional reasons to use rust in such situations, which are why it's considered "super cool".

djha-skin 3y ago

Not really though. He keeps pointing out that he wants to integrate with Rust libraries, but it's actually pretty easy to write integrations between Rust and Python[1][2]. If that were the actual reason, there is a much better path of least resistance available. The only other type of given argument for moving to Rust was that the author enjoyed it, so it appears to be another "Rust is super cool" rewrite. It really speaks to the power of developer experience. People are willing to rewrite their entire application to be more comfortable. I know I am, only my language of choice is Common Lisp. 1: https://saidvandeklundert.net/learn/2021-11-18-calling-rust-from-python-using-pyo3/ https://saidvandeklundert.net/learn/2021-11-18-calling-rust-... 2: https://www.infoworld.com/article/3664124/how-to-use-rust-with-python-and-python-with-rust.html https://www.infoworld.com/article/3664124/how-to-use-rust-wi...

moyix 3y ago
The startup time mentioned is actually a big deal for me – I do record all of my terminal sessions (I even wrote a tool that uses his avt library to grep through the terminal logs, although I never got around to making it fast enough to be really useful: https://github.com/moyix/termgrep https://github.com/moyix/termgrep), and with the Python version I often lose the first few characters of my first command in a new terminal because asciinema is still starting up...
- infogulch 3y ago
  You record all of your terminal sessions?! Sessions that are open for days? Commands that accidentally spew huge amounts of garbled nonsense to stdout multiple times because you're figuring a command out?
- ku1ik 3y ago
  Maybe the new `asciinema convert demo.cast demo.txt` command (in 3.0, develop branch) would be useful to you? It converts the session to plain text using avt (which is now embedded in the CLI). You could grep like this: asciinema convert demo.cast /dev/stdout -f txt | grep foo

kelnos 3y ago

I'd usually agree, but the list of reasons involve integrating with Rust libraries, all of which it appears were written by the same author of asciinema. I think it just boils down to the author feeling a lot more productive and less frustrated in Rust than Python. Which is a perfectly fine reason to switch!