←back to thread

452 points birdculture | 1 comments | | HN request time: 0.207s | source
Show context
GenshoTikamura ◴[] No.43982864[source]
> Stop resisting. That’s the most important lesson

> Accept that learning Rust requires...

> Leave your hubris at home

> Declare defeat

> Resistance is futile. The longer you refuse to learn, the longer you will suffer

> Forget what you think you knew...

Now it finally clicked to me that Orwell's telescreen OS was written in Rust

replies(1): >>43983002 #
atoav ◴[] No.43983002[source]
But it is true. My own biggest mistake when learning Rust was that I tried to torce Object Oriented paradigms on it. That went.. poorly. As soon as I went "fuck it, I just do it like you want" things went smoothly.
replies(2): >>43984144 #>>43987271 #
rikafurude21 ◴[] No.43984144[source]
Sounds like an abusive relationship if im being honest. Your programming language shouldnt constrict you in those ways.
replies(5): >>43984486 #>>43984523 #>>43984615 #>>43984649 #>>43993404 #
1. ModernMech ◴[] No.43984649[source]
Abusive relationships involve coercion, control, fear, and often violate personal autonomy and consent. One party dominates the other in a harmful way. Using Rust is not harmful.

Placing restrictions on the programs a programmer can write is not abusive. The rules exist to ensure clarity, safety, performance, and design goals. In an abusive relationship, rules are created to control or punish behavior, often changing capriciously and without reason or consultation. By contrast, Rust is designed by a group of people who work together to advance the language according to a set of articulated goals. The rules are clear and do not change capriciously.

Abuse causes emotional trauma, isolation, and long-term harm. Rust may cause feelings of frustration and annoyance, it may make you a less efficient programmer, but using it does not cause psychological or physical harm found in abusive relationships.