5 ms·
FWIW from the prelude: > Originally created during the Python 2.4 days, we've tried to keep the content universal and exercises relevant, even for newer releas
by danso 9y ago
FWIW from the prelude:
> Originally created during the Python 2.4 days, we've tried to keep the content universal and exercises relevant, even for newer releases. As mentioned on the setup page, this material covers Python 2. While we recommend "avoiding" Python 3 for now, recognize that it is the future, as all new features are only going there.
- yathern 9y agoI remember my freshman year of college, I was told how some 60% of what I learn will be out-of-date by the time I graduate. I always thought that was a ridiculous statement. But nevertheless - the prime example was Python. At the time we were being taught Python 2.7 or so, we were told how by the time we graduate - most of the world will be using Python 3.X
- fhood 9y agoI feel like that means they were teaching from the wrong perspective. All of my cs classes were about principles, and the language was incidental, and I don't feel that the things I learned have gone out of date at all. Edit: On a related note, I don't think python is a very good first language, despite it being my absolute favorite, because it uses kind of a mishmash of paradigms.
- stordoff 9y agoMy university had an interesting approach to that problem - where it was necessary or useful to use real code, different classes were deliberately taught in different languages (mix of Java/ML/C/MIPS/Verilog). What language would you say is a good first language? To me, Python seems very readable to a new programmer without having a capability/tooling ceiling that you will eventually reach, which seem to make it a decent choice.
- fhood 9y agoAs much as I hate to say it, probably C. Actually, I wonder if there are any toy languages out there that are basically C without raw pointers? If so I would go with that.
- polotics 9y agoMuch less than 60% of my Python2 knowledge when I upgraded to Python3, more like 5% I would say, even then.
- aidenn0 9y agoSince computing is a young field, that gets less true every year. I would say less than 60% of what I learned 15 years ago is out-of-date, but talking with my dad, it was a much higher percentage when he got his MS in the early 80s.
- btilly 9y agoI am willing to bet that computing is a much older field than you realize. And the amount of change is much more than you're aware of. Furthermore I do not believe that the rate of change will stop in several lifetimes. On how old computing is, automated computing using punch cards was invented in the 1800s. "Programmer" has been a viable job title since WW II. Essays about programming written 50 years ago are still relevant today. On how much things change, that depends on your environment. Across the hall from me there is a company of COBOL programmers. A lot of what they need to know hasn't changed since before I was born. Sitting next to me are people implementing code in node.js with react. Most of the libraries and best practices that they are trying to follow were invented in the last 10 years. I'm maintaining a legacy project that isn't using any technology less than 10 years old. The experience of how much things change is highly dependent on what exactly you are doing. However I'm minded of what my sister said about nursing. When she started as a nurse she was told that on average half of what she knew would be out of date in 10 years. This is why nurses need continual retraining. This was ridiculous to her. But guess what? When she retired it was true, every 10 years about half of what she knew went out of date! Between new research, new technologies, new best practices and so on, nursing never stopped changing. And hasn't stopped changing since modern nursing was invented in the 1800s. If a profession so much older than ours shows such sustained change, and our profession has shown an extended sustained rate of change, why would I expect this to change? The truth is that I don't. Sustained change is more the rule than the exception in technology, and none of the fundamental reasons why have changed. Some knowledge is core - the ways that programmers get defensive and have trouble accepting their own bugs and mistakes has not changed since before I was born - and others change constantly. Learn the principles. Learn what is core. And be prepared to continue learning trivia forever because programming is continuing to change.
- otakucode 9y agoYeah, for some reason Google is adamantly opposed to adopting Python 3. I have no idea why. It's clearly much better, more well designed, etc. I mean come on... print as a statement rather than a function call? That alone should be enough to make the decision I'd think.
- geofft 9y agoDropbox, which is a much smaller company and codebase than Google, is (as far as I've heard) still on Python 2, despite having hired Guido van Rossum away from Google to work on static type annotations for Python to fix all the str/bytes stuff and related incompatibilities in their codebase so that they can move. Certainly this was the status in mid-2016, about four years after they hired van Rossum: https://us.pycon.org/2016/schedule/presentation/2266/ https://us.pycon.org/2016/schedule/presentation/2266/ The difficult engineering problems in the world aren't greenfield engineering.
- pebers 9y agoprint as a statement vs. function doesn't carry that much weight when you have tens of millions of lines of currently working code to migrate.
- newen 9y ago> print as a statement rather than a function call? That alone should be enough to make the decision I'd think. I seriously cannot tell if this is a joke or not.
- joshuamorton 9y agoI don't think this is true, as a python user at Google. There's momentum that has to be shifted, and that can't happen overnight. But it is absolutely a work in progress. The writing is on the wall for py2 at Google, and in some ways it has been for years.
- dsl 9y agoGoogle has billions of lines of code, a non-trivial amount of which is Python. Moving to Python 3 would require an all-hands-on-deck massive effort.