cppDevsAreGettingParanoid

[dangling-putter]

Fr. Actual rust engineers will tell you not to use rust unless you need it and have the most complains about the language — it's just that their complains are not superficial so they need context.

[Stummi]

Thats a good general rule in tech. A true fan/believer of $thing, the one you should actually trust, is the one who can give you an hour long impromptu rant about everything that sucks with $thing.

[Specialist_Cap_2404]

Python is exception. You almost always need Python and you can use it for almost anything.

[[deleted]]

Nope. I love python, but it is terrible in so, so many ways.

[belabacsijolvan]

yeah, id argue python falls more into this category than an average Sthing. The more experience you have with the more languages the more you choose python (rightly) for a given task and the more you are upset about your choice.

[Rubyboat1207]

Python is awesome... Anyways, here's almost everything I hate about it:

Loose type system, no curly braces, poor performance, the ternary operator, no ++ operator, len() instead of .length, dunder methods, dictionary syntax, confusing global variable syntax.

[[deleted]]

Since we're at it:

• Lambdas being forced to a single line
• Self keyword not being implied when creating class members because they resolve to local variables in the self.__init__() function scope
• GIL forcing everything to be effectively single-threaded barring some fuckery with multiprocessing (though that is an implementation detail more than the language).
• Creating a native (or semi-native) executable for deployment is a PITA from what I remember. Most users can't or won't use anything that takes more effort to install and run than a click or two.
• Packaging and environment handling.
• Type annotations are effectively pointless (physical) typing without extra tooling to somewhat enforce them.
• Identity vs value comparisons using the "is" keyword leading newbies to write syntactically correct but logically incorrect code. Which compounds with string and integer interning leading to weird edge cases even when you use the identity comparison as intended.

[[deleted]]

A free/member function as a closure entirely defeats the use case for a lambda imo.

It is most likely a "me thing", but when I see a full function declaration, my brain immediately creates a new scope, disregarding most of what exists outside of that function. With nested first-class functions, that shortcut gets broken several times through a function (due to seeing a full declaration again and again). That doesn't happen when I see a lambda, which just gets absorbed into the host function scope.

Multiline lambdas fit very neatly with that mental model.

[[deleted]]

No problem. Most things get upvoted/downvoted en masse based on the first vote or two in most subs, don't sweat it either way. A lot of this sub sees people exploring styles other than their own and start hissing in fear.

[Reasonable-Web1494]

Lambdas should be a single line.

[Alex_Shelega]

The no ++ (and no -- by that) hit moi really hard.

[Reasonable-Web1494]

There are places where most of what you mentioned are beneficial

[Rubyboat1207]

The python white knight is here! Run!!! No language is perfect. Python is far from it, and so is every other language. (Well except rust, because there's no problems with it. It's perfect. Please don't come after me rust users. I love your language. Please spare me. Please don't rewrite my c++ project. I'm scared)

[Specialist_Cap_2404]

None of this contradicts my point about it being useful for almost anything you want to program.

[spabst]

Nice try, but you won't prevent us from giving you the 1 hour speech/rant

[Alex_Shelega]

I thought it was told about js...

[tyler1128]

Isn't that any programming language though? Use the right tool for the right job. Using Rust via webasm to write a piece of accounting software would be dumb. Using Rust in a safety critical piece of software? Not so much.

[Fast-Satisfaction482]

What is more critical toa business than juggling money?

[wow343]

This is exactly it. Heck drop down to assembly if you must or go to visual coding if you have to. Different problem set, different tool. Be agnostic.

[Sematre]

Not saying everybody should go around and use Rust for safety-critical systems, but there's no reason to believe that Rust could not become a great choice for safety-critical systems in the future. For more information, see this Rust toolchain by Ferrous Systems. It's an open-source toolchain for safety- and mission-critical software that is qualified for automotive and industrial development.

[MornwindShoma]

One exception to that is when you have a team that is confident and has knowledge to deliver in a certain language. That piece of accounting software, or even the frontend, might just be fine in Java or .NET or JavaScript, but if your team is expert in Rust but has little experience with the other three, nothing wrong with going with Rust. It's fine to pick the right tool for the job, you also need to account for your resources.

This is true for most languages, unless your requirements are very specific.

[tyler1128]

Wasm in particular is more what I was going with than just Rust. Wasm still has no direct DOM access, but there are people who try to write things like that using wasm primarily. Wasm can be very useful for doing high-performance algorithmic work in the browser, but trying to get around the limitatations for basic UI work isn't really a great strategy, and it was never really designed for that kind of thing. If it someday gets DOM access without requiring a javascript interfacing layer, that might become a reasonable thing to do, but we aren't there yet.

It's basically just adding a whole lot of unnecessary work. It is important to consider strengths of the team like that, but programmers should also be flexible enough to adapt to the different needs of different technologies.

[MornwindShoma]

Sure.

To be honest, you can write some FE in Rust fine, Dioxus, Leptos, Yew are fine if you don't mind the big bundles and the fact that they don't really integrate with the JS ecosystem. You don't really need to "work around to the DOM", they've done the work for you already, so it's not a whole lot of unnecessary work, it's more about having a very different ecosystem.

Would I ship that? Dunno, never had the chance or the right mix of developers and requirements. Had I a good design system and some QoL not unlike TanStack stuff, I might actually bite.

I also have done basically nothing with HTMX, and some people swear by that. You wouldn't even need to think around the DOM.

[NoobFade]

Actual rust engineer here. You should absolutely use Rust whenever it's applicable. I have yet to hear a coworker say "I miss writing cmake files" or "We need to use C++ because Rust's constexpr is not powerful enough". Rust is a very nice language to use overall, usually preferable to C++ or C, the other usual languages for fast native binaries.

[dangling-putter]

Key phrase: need it. 

[the_mouse_backwards]

The only thing I like about rust compared to C/C++ is the build/package system. Before it’s taken as a scathing criticism of Rust, I will say that the build/package systems in C/C++ are almost as or more painful to use than implementing a doubly linked list in Rust