[–] 3 points 2 weeks ago (2 children)

I mean, just to offer you the counter perspective, IMHO programs written in X tend to have problem Y:

  • Python: Terrible error messages, buggy, sluggish, slow, but good documentation
  • Java: Gurgles RAM like there's no tomorrow (but tends to do something useful with it), sluggish
  • Node.js: Just gurgles RAM for the fun of it, buggy, over-engineered functionality, confusing documentation
  • Rust: Over-engineered functionality
  • Go: Bad error messages, quirky detail behavior
  • Haskell: Practically 0 bugs, but if you do run into a bug, good luck. Thin documentation.
  • C/C++: Basically no bells or whistles, and no compiled build available. Also stupidly difficult compile on anything, except the singular dev's PC.

Obviously, these are caricatures, i.e. I'm overdrawing the details and omitting nuance. And these are also influenced by the kind of people that are drawn to these languages. And these are influenced by what I know about the languages, I didn't conduct a double-blind study.

But yeah, there's a reason why Python ended up first on that list. I don't have that hard of an opinion about the others, but genuinely, when I know a non-trivial program is written in Python, I will think twice whether I want to use it. Because it always seems to cost me a non-trivial amount of nerves in the end.

  • source
  • parent
  • context
  • [–] [S] 32 points 2 weeks ago (3 children)

    Excellent, thanks for the tip! I'm thinking of writing a linked list and creating reference pointers to the list so I can copy it and change the copy. Unsafe fixed all the problems, but my PC keeps crashing. I think it's some non-rust util smh

  • source
  • parent
  • context
  • [–] [S] 7 points 2 weeks ago

    Dropping the /s for a moment, I actually already learned Rust about 7 years ago for my CS courses. There was a 7 week writing course where we had to pick a programming topic, centered on language design. I chose to generally discuss Rust because of lifetimes and found that there are a lot of cool things, but the syntax can get extremely dense

  • source
  • parent
  • context
  • [–] 12 points 2 weeks ago* (5 children)

    I am unwilling to make light of another's desire to learn so that they might help themselves, even if some of the phrasing feels a little silly and market-y.

    What does this post accomplish? Feels mean-spirited, really.

  • source
  • [–] 5 points 2 weeks ago* (2 children)

    Wow, I hate the thumbnails just from this screenshot.

    Good luck, Rust is easy if you have a background in C/C++. Lifetime specifiers are a wrinkle, but also doable. I recommend you do Advent of Code tasks and ask an LLM for stylistic feedback.

  • source
  • [–] 2 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

    I could understand caring a lot about the language if I were writing or maintaining something, but not usually if I'm just using a software package, unless it has performance implications. Maybe for software that has privilege escalation risk you maybe want a language that might help mitigate some security issues, but launchers shouldn't fall into that camp.

    But, hey, people have their own preferences and opinions. Maybe someone's super into Rust and wants to try to run as pure a Rust environment as possible or something.

  • source
  • parent
  • context
  • view more: β€Ή prev next β€Ί