▲ | kincl 21 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||
The Asciinema clients have now gone from Python to Golang back to Python now to Rust https://docs.asciinema.org/history/ https://blog.asciinema.org/post/and-now-for-something-comple... | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | creatonez 12 hours ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||
It's one of those projects where it really doesn't matter what language it's in, all of them will accomplish the job roughly the same. I'm happy for the dev to rewrite in whatever language motivates them to work on it, because with such a small codebase the chance it will affect functionality is low enough for it to not matter. | |||||||||||||||||||||||||||||||||||||||||||||||
▲ | imiric 21 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||||||||
That's... interesting. Most of the gripes about Go could've been apparent before a single line was written, with just some preliminary research. The packaging issues are valid for 2016, even though they are now resolved with Go modules. Then the rewrites in ClojureScript, Elixir, and now Rust... Sheesh. All this tells me is that the authors are trend chasers rather than solid engineers, which erodes any trust I had in this project. | |||||||||||||||||||||||||||||||||||||||||||||||
|