News for hackers. Stuff that matters.
Re:Async Rust Is A Bad Language by pshc on Friday September 08, 2023 @05:22PM (#37439605)
Debugging rare crashes and heisenbugs is more frustrating, and in non-safe languages, a chronic problem.

Whereas after you prove the safety of a design once, it stays with you.

Re:Async Rust Is A Bad Language by jstx1 on Friday September 08, 2023 @05:35PM (#37439731)
It stays with you until you need to change something and find yourself unable to make incremental changes.

And in many use cases people are throwing Rust (and especially async Rust) on problems solved just fine with GC languages so the safety argument doesn’t apply there.

Re:Async Rust Is A Bad Language by brigadier132 on Friday September 08, 2023 @05:52PM (#37439848)
> change something and find yourself unable to make incremental changes

why do you believe this becomes the case with rust code?

Re:Async Rust Is A Bad Language by imtringued on Saturday September 09, 2023 @04:26AM (#37443320)
The safety argument is actually the reason why you can use Rust in those cases to begin with. If it was C or C++ you simply couldn't use it for things like webservers due to the safety problems inherent to these languages. So Rust creeps into the part of the market that used to be exclusive to GC languages.
Re:Async Rust Is A Bad Language by maccard on Saturday September 09, 2023 @04:44AM (#37443402)
What do you think nginx and Apache are written in?
Re:Async Rust Is A Bad Language by ttfkam on Saturday September 09, 2023 @10:13AM (#37445692)
How few severe vulnerabilities and other major defects (memory corruption or crashes) do you think Nginx and Apache have had over the years?
Re:Async Rust Is A Bad Language by sliken on Saturday September 09, 2023 @06:38PM (#37451008)
Sort of. Do you want someone that doesn't understand the constraints that likely is creating a bug that will cause crashes? Or do you want to block them until they understand the constraints?
Re:Async Rust Is A Bad Language by throw10920 on Friday September 08, 2023 @08:54PM (#37441123)
So you use a safe, garbage-collected language like Python, and iterate 5x as fast as Rust. Problem solved. It's 2023 - there are at least a dozen production-quality safe languages.
Re:Async Rust Is A Bad Language by buildartefact on Friday September 08, 2023 @09:10PM (#37441206)
You’re seriously suggesting writing a game engine in Python?
Re:Async Rust Is A Bad Language by throw10920 on Friday September 08, 2023 @09:35PM (#37441320)
You accidentally responded to the wrong comment. I never mentioned a game engine.
Re:Async Rust Is A Bad Language by Turskarama on Friday September 08, 2023 @10:30PM (#37441634)
It doesn't really matter, there doesn't exist a problem space where both Rust and Python are reasonable choices.

Case in point, I once wrote a program to take a 360 degree image and rotate it so that the horizon followed the horizontal line along the middle, and it faced north. I wrote it in python first and running it on a 2k image took on the order of 5 minutes. I rewrote it in rust and it took on the order of 200ms.

Could I iterate in Python faster? Yes, but the end result was useless.

Re:Async Rust Is A Bad Language by throw10920 on Friday September 08, 2023 @10:35PM (#37441667)
> there doesn't exist a problem space where both Rust and Python are reasonable choices

This thread, and many other threads about Rust, are filled with people arguing the exact opposite - that Rust is a good, productive language for high-level application development. I agree with you, there's relatively little overlap - that's what I'm arguing for!

Re:Async Rust Is A Bad Language by kprotty on Saturday September 09, 2023 @12:32PM (#37447197)
Both qualify for writing tiny web servers, cli/byte-manipulation scripts, server automation jobs, in-house GUI applications, and other small stuff. Could technically argue that these are a "relatively little overlap" depending on what you do though..
Re:Async Rust Is A Bad Language by SantalBlush on Saturday September 09, 2023 @12:00AM (#37442172)
This thread is about writing a game engine, so GP didn't "accidentally" respond to the wrong comment. Their question is on-topic.

If your comments aren't relevant to writing a game engine, then they're not relevant to this thread.

Re:Async Rust Is A Bad Language by throw10920 on Saturday September 09, 2023 @01:40AM (#37442585)
> This thread is about writing a game engine

This is false. This "thread" is not "about" anything. The top-level comment was about writing a game engine, and various replies to that thread deviated from that topic to a greater or lesser extent. Nobody has the authority to decide what a thread is "about".

Additionally, the actual article under consideration is about Rust's design in general. That makes my comments more on topic than one about game engines in particular, and so viewed through that lens it's pretty obvious that if you're going to assume anything about my comments, then it would not be that they're about game engines.

Re:Async Rust Is A Bad Language by pkolaczk on Saturday September 09, 2023 @03:19AM (#37443013)
> and iterate 5x as fast as Rust.

I've been involved in Java, Python, PHP, Scala, C++, Rust, JS projects in my career. I think I'd notice a 5x speed difference in favor of Python if it existed. But I haven't.

Re:Async Rust Is A Bad Language by throw10920 on Saturday September 09, 2023 @02:39PM (#37448786)
You're probably just using Python wrong, then. You can use a Jupyter notebook to incrementally develop and run pieces of code in seconds, and this scales to larger programs. With Rust, you have to re-compile and re-run your entire application every time you want to test your changes. That's a 5x productivity benefit by itself.