After playing a little bit with QBasic when I was a kid, I was given a K&R C book. My takeaway: programming is not for me. I didn't look at programming seriously again until I was 23. This article is terrible advice.https://www.zeroequalsfalse.press/2017/11/29/c/
-
-
Yes, you can learn how to get away with certain wrong things in Go as well, but it's not the first thing you will learn - in Go is easier to do things right, and you have to go deeper to break the rules - in Ruby, JS, Python etc. it's the other way around.
-
I really want you to provide me with an example, not just rhetoric.
-
I don't think my post is at all rhetorical though. In my experience, devs who don't know any of the stricter languages, even if they create working products, tend to write code that no one else can understand. Programming requires discipline - the loose languages don't teach it.
-
My experience is that trying to bootstrap with a strict language causes people who could be great programmers to bounce off. I wrote Ruby and JS for years before writing way more code in Rust and TS and I have not experienced years of bad habits to unlearn.
-
On the other hand, as I said in my original post, sentiments about what it means to be a "real programmer" pushed me off of the path that eventually led me to working on the Rust programming language. So I just disagree with your empirical claim.
-
Isn't it possible you just didn't really have the interest or patience when you were younger though? People change. I've changed my opinions on lots of things over the years. Maybe you just weren't ready yet? ;-)
-
As an older programmer I plain don't know what "unlearnable bad habits" you're talking about. Did I understand you as saying that writing code in Ruby makes people resistant to code documentation earlier?
-
No, what I'm saying is you will initially learn to count on a person deducing, or a computer to determine at runtime, the state of your program, the pre/post conditions of a function, etc. - which is costly both in computer and human resources, and a habit you must then unlearn.
- 6 more replies
New conversation -
-
-
Put any JS code through the Typescript compiler in strict mode - it will show you everything that's wrong, missing, undocumented, etc. Correct everything, and you will discover that most JS is jam-packed with subtle (or sometimes horrible) bugs.
-
That isn't the question I asked. What's an example of something you can get away with in JS and Ruby (the "loose languages") in your post that Go protects you from?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.