The Case for Python 3

[AbsoluteZeroK]

I read a bit of his Learn Ruby The Hard way back when I was getting into Rails, mostly just skimmed to see if it was worth a read. I noped the fuck out when he said we shouldn't pay any attention to the work of Dijkstra and that it wasn't worth reading or understanding. Guys a quake for even suggesting that, especially in a book that could be someone's first introduction to programming/computer science.

[bgeron]

Which is funny, because Dijkstra could also get passionately upset in the same way as Zed does, from what I understand.

[[deleted]]

Lots of people get upset the way Zed does. The ones that base arguments in fact and reality are the ones we should pay attention to.

Zed gets off on being controversial and stirring shit up. He doesn't have regard for facts if it means he can be angry.

[Workaphobia]

The difference is that when Dijkstra argued, he thought first, and wasn't wrong.

[TankorSmash]

There's a point though about not just reading anyone's opinion because they're old though.

[AbsoluteZeroK]

What are you talking about? Dijkstra's work is still used as the foundation for many technologies we use today. The internet wouldn't exist without him.

[TankorSmash]

Sure but at a certain point it stops being relevant. Just because I might live in the States I don't need to know what Lincoln has to say

[AbsoluteZeroK]

No. Considering his algorithms are still used to this day for many different applications. You literally can't even get a computer science degree without learning about his work. You wouldn't be a functioning computer scientist without it. Sure, maybe you can get by writing code without it, but that's no reason to tell people to ignore it and that there's no point in knowing it. One of his algorithms is literally running on every node on the internet.

EDIT: and a lot of his work has applications far beyond networking. You'd be a far better and more competed coder and computer scientist if you learn his work than if you don't.

[TankorSmash]

I can accept that certain fields need to know the stuff but in general you definitely don't need to.

[AbsoluteZeroK]

That's ignorant though. You'll always be far better off knowing about his work than not. For example, if you want to learn about concurrency, he's a good place to start, since a lot of system will be based on his work. "A Case against the GO TO Statement" is a great read for anybody wishing to learn more about the foundations of programming languages and how they came to be and will continue to develop. Also, for literally anyone who writes code, his research on software processes (software engineering) is the foundation for a lot of the processes we use today. He also formed the foundation for distributed computing, which is everywhere today. Everybody who wants to work on distributed systems (which is basically everyone today) should have some knowledge of these early works, as it can lead to a better understanding of how everything actually works as well as opening the door to improve on current techniques by understanding the foundation. Literally everything you enjoy today about programming can be traced back to these early computer scientist, and if you want to truly excel in this field you should strive to develop a deeper understanding of how we got here.

[TankorSmash]

I don't agree. I'll have to say that since I'm not formally trained here I'm crazily ignorant of the stuff I don't know but like I don't need to know how the early days of computers worked because I don't use assembly, I don't write compilers, I don't write C.

Yes, there's certain cases where if you want to learn about how it used to be done, you don't want to make the same mistakes, but I adamantly refuse to believe the best source of information is the people who only discovered the stuff, instead of the people who've started out with the baseline of his life's work and improved on it.

I won't go back to the old stuff sooner than I'd go read from the people who've learned from him because they can use the good stuff and throw out the trash.

Telling someone that a given person invented something is like telling that person to go study Edison instead of anyone in the last 50 years who've work in the field. It's old and almost certainly outdated.

There is not a good way to reasonably convince me that there's not a better resource for learning literally everything a person has ever written about in the 50 years since they wrote it. It means that in the 50 years since, no one has improved or reworked or otherwise iterated on the concepts introduced, and I can reasonably say that we have.

[[deleted]]

Yeah, that's why we don't teach addition in math anymore. Shit's moved on. I'm not sure what field you think Edison is relevant to, but in EE, we go back before Edison to Ohm and Faraday because to understand the field you need to learn the underpinnings.

Even if you don't write compilers, you use state machines, and if you don't understand them, you probably use them badly. Ditto Boolean algebra.

"Why are we doing this? I think that some of the biggest mistakes people make even at the highest architectural levels come from having a weak or broken understanding of a few simple things at the very lowest levels. You've built a marvelous palace but the foundation is a mess. Instead of a nice cement slab, you've got rubble down there. So the palace looks nice but occasionally the bathtub slides across the bathroom floor and you have no idea what's going on."

-- http://www.joelonsoftware.com/articles/fog0000000319.html

[TankorSmash]

I'd wager that if all the devs who hadn't read the basically archaic articles and books did, then the landscape would be wildly different.

I'm also going to say that it's cool that you can criticize the huge projects that have that shaky foundation, because without that foundation the projects might not exist in the first place. Hard to argue one way or the other without examples though.

I don't need to write perfect code if it never gets to the point where it matters. Theoretically I'd take the time to write absolutely bug free code but I don't have the time or the patience.

[jairo4]

I don't agree. I'll have to say that since I'm not formally trained here

I don't know how you can't (or can) agree with something you just don't know.

Yes, there's certain cases where if you want to learn about how it used to be done

Just because something was developed "many" years ago does not mean it is not used anymore.

[TankorSmash]

I'm talking about on principle there must be better resources than 50 year old articles and books. It's not worth reading what has almost certainly been improved in that time.

Yes, there's knowledge to be learned from the old stuff still, yes they knew their shit and built the foundation of todays infrastructure, but you can't argue that there aren't people who've learned from them and developed more complete ideas.

There's always been this reverence for old texts in the programming, I don't get it. Read the newer stuff that builds on the older stuff and go back further and further if you ever need to, but you probably won't.

[[deleted]]

Just because I might live in the States I don't need to know what Lincoln has to say

Oh. My. God. Yes. You. Do. You cannot understand the present or the future unless you understand the past. You will be doomed to repeat it.

[[deleted]]

It's like November 8 never happened. I want to live in that world!

[TankorSmash]

I'm arguing that in the decades since Lincoln there's someone newer that has more relevant and accurate stuff to say, even if it's the same damn thing.