@sjw @mikuphile Rust's error messages are usually pretty nice. There aren't many languages that come close to "hundreds of unimportant template spew" that C++ gives you.
@apropos @mikuphile Not in my experience and the syntax of the language is pretty much, "What if we combined the the worst parts of C++ with JavaScript because we're soy infused Biden supports? Vote blue no matter who amirite?!"
@sjw @mikuphile your Rust experience definitely doesn't include a tiny mis-use of a template, the equivalent of passing the wrong type to a function, that results in 800 lines of error messages.

It's still possible to have a bad time. Depending on how you learn Rust, you can be comfortably using libraries to get quite a lot done, and thinking "wow, this was a quick language to be productive in", and then you'll make the tiniest change that requires care with lifetimes and suddenly the difficulty curve that you thought was gliding down has risen up like a wall in front of you and broken your nose. If you've had this experience I can understand not appreciating the error messages that say "you need a lifetime annotation" only to result in more error messages when you do as told only result in more error messages when you again do as told, to no resolution.

But as you learn more of the language you get past this period and the error messages become reliably useful again. You never learn C++ well enough to not occasionally get template spew, you just use an IDE well enough to not see them.
@apropos @sjw @mikuphile Rust is awful. It's an entire language built around the idea of "What if you have to remove all of the upsides of this language in order to use it for the our current use case?"

C++ is much better. Also I dont want to have safety vs freedom arguments in my programming languages.
@rhyse @sjw @apropos @mikuphile

fuck C++. Its just C but worse


At least Rust is a language that prioritizes safety (Especially since C++ has none of it)

C++ as a language is essentially a collection of operations, all of which carry some of the pitfalls of C, but not all of the utilities carry the same pitfalls,

C++ is literally the language where the Rule is used less than the exception to the rule. Rust at least is incredibly consistent, even if it does have a higher barrier to entry than C++

C > Rust > Literally Anything > C++

Source: Professional C++ dev

@lunarised @sjw @apropos @mikuphile @rhyse When it's just C but some more stuff it's not that bad. Not really worth bothering with the extra headaches unless you really benefit from something though. Mainly I'd only pick it if there's a lib I really want, or would really benefit from class vtable lookups without having to do something fancy

When I do opengl shit I pick C++ purely so I can get glm, assimp without the wrapper and a few other things, then end up basically writing C code anyway, maybe with a bunch of stuff packed inside structs just so i can do

model.translate(...);

instead of

model_translate(&model, ...);

Follow

@lunarised @sjw @apropos @mikuphile @rhyse Though also, if you don't need more than C libs (and some basic C++ linkage) and want some more, you can pick D to get the benefits of C++ without as much of the garbage. It's supposed to be redesigned C++

dlang.org/comparison.html

· · Web · 1 · 0 · 2
@applejack @sjw @apropos @mikuphile @rhyse I want to like D, but it doesn't seem to add anything rust already isn't for me
Sign in to participate in the conversation
Game Liberty Mastodon

Mainly gaming/nerd instance for people who value free speech. Everyone is welcome.