this post was submitted on 01 Nov 2023
139 points (96.0% liked)
Programming
17362 readers
174 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Rust. I've been using it for a while, and I've been using more software written in it lately. Stuff you make with it is just better in most ways. In other languages, you have to go above and beyond to make your code fully correct, safe, user friendly, and every trait I value in software. Rust makes those things easy, and so people are more willing to do them, and so things that get made in it are better. Oftentimes it's just a matter of pulling in a crate and adding a few lines of code.
I just wish Rust's syntax (and devs attitude) wasn't so unpalatably shite
I seriously can't stand that shit but I really like it's ideas
I'm learning Rust at the moment and I too think I have some reservations with its syntax. Most of these reservations come from my strong preference for functional programming over OOP.
I am unsure if I like method-syntax period, even if it isn't inherently OO. Chaining just makes me feel uncomfortable in a way piping doesn't.
Also it seems idiomatic for values of enumerated types to be written
Type::Enum, which seems ugly and unnecessary.What'd you make of this article?: https://matklad.github.io/2023/01/26/rusts-ugly-syntax.html
About the article you linked:
Author is removing every part of the initial function, admitting there are reasons those things are there in the first place, only to be left with a slightly more verbose version of an equivalent python implementation. Well then just use python?
Author also doesn't seem to understand what static polymorphism is/why this specific function is generic. It's not strictly about "bytes", it's about avoiding virtual calls/have nicer API. Author conveniently omits mentioning the clone() calls their version requires from the client call. Or they would make everything automatically cloned, and I already addressed that in the first paragraph I
Finally, standard libraries are notoriously bad examples of "normal" code. They mention it, but still declare that that their example is relevant. If the functions I wrote were compiled and used thousands of times per day I would probably worry more about splitting generic and concrete implementations. I'll take this over anything in the C++ standard library (which is a much more relevant language to compare rust with than e.g. python)