←back to thread

302 points Bogdanp | 3 comments | | HN request time: 0s | source
Show context
adastra22 ◴[] No.44390813[source]
As a former C++ developer, claims that rust compilation is slow leave me scratching my head.
replies(5): >>44390867 #>>44390918 #>>44391177 #>>44395299 #>>44403069 #
eikenberry ◴[] No.44390918[source]
Which is one of the reasons why Rust is considered to be targeting C++'s developers. C++ devs already have the Stockholm syndrome needed to tolerate the tooling.
replies(3): >>44391267 #>>44391775 #>>44392740 #
MyOutfitIsVague ◴[] No.44391267[source]
Rust's compilation is slow, but the tooling is just about the best that any programming language has.
replies(2): >>44392557 #>>44394703 #
GuB-42 ◴[] No.44392557{3}[source]
How good is the debugger? "edit and continue"? Hot reload? Full IDE?

I don't know enough Rust, but I find these aspects are seriously lacking in C++ on Linux, and it is one of the few things I think Windows has it better for developers. Is Rust better?

replies(3): >>44392771 #>>44393092 #>>44393361 #
1. adastra22 ◴[] No.44392771{4}[source]
No idea because I never do that. Nor does any rust programmer I know. Which may answer your question ;)
replies(2): >>44398467 #>>44401430 #
2. frollogaston ◴[] No.44398467[source]
"Rust devs don't use debuggers" isn't a good answer. The one time I used Rust for some project like 7 years ago, I did have to use a debugger, and it was fine.
3. GuB-42 ◴[] No.44401430[source]
If programmers don't use a debugger, that's because the debugger is bad.

For me, the ideal debugger is one you never leave. That is you are in a debugging session, maybe with your code running, or stopped on a breakpoint, and you write your code without leaving the session. You can see the values of your variables as you type them, the branches that will be taken, etc... When an error condition happen, you break on it, and still without leaving the session, you can fix the code, roll back before the error happened and see if it passes. IntelliJ is close to that, and it seems like some tools from the video game industry are even better.

Debugging should be natural, it shouldn't be something you pull out as a last resort. If it is not natural, it is a bad debugger, or a bad development environment, period. Maybe there are reasons for why it is bad, maybe the language designers have other priorities, which is acceptable, but it doesn't change the fact that it is bad. Same goes for slow compile times by the way.