News for hackers. Stuff that matters.
Re:My experience rewriting Enjarify in Rust by kbenson on Monday September 19, 2016 @01:02PM (#12532875)
I'm not sure what you're arguing. The article didn't advise people to switch from Python to Rust. It simply gave information that people that are considering it. The last paragraph even echoes some of your sentiment.

> And the performance it brings is not enough to make the decision to switch language in most cases.

That's assuming a lot. Nearly 10x the speed is extremely useful for some people. Presumably if you are rewriting your Python code in Rust or Go, you've already identified performance as a big reason to do so, and that gain would be extremely useful.

Re:My experience rewriting Enjarify in Rust by Thaxll on Monday September 19, 2016 @01:15PM (#12532983)
"Rewriting anything takes a lot of time and causes lots of bugs, going from Python to less expressive language means an increased maintenance burden. But if for some reason, you still want to rewrite it, please don’t pick Go. Rust is better in pretty much every way."

I mean it's pretty much 'never use Go'

Re:My experience rewriting Enjarify in Rust by kbenson on Monday September 19, 2016 @01:27PM (#12533062)
Yeah, the article boils down to "If you feel the need to rewrite your python in a statically typed language, and it's between Rust and Go, don't use Go, because the cost of implementing in Rust is roughly equivalent, but the performance gains are much higher."

I think with all the evidence presented, that's an eminently defensible position. Get twice the performance of Go (in this case, obviously it will be very dependent on project) for not much more effort, when you've already made the choice to rewrite for performance.