Python Learning Manual Note 1

Looking at Udacity's IOS learning route today, the author's view is that it's best to learn swift rather than objective-c, on the one hand because Swift is simpler, and Apple intends to replace OC with Swift as the official language of the future.

In universities, programming language courses are C and C + +. I don't know who made it, maybe they have good enough reason. But for most people, the two languages – one too low, one too complex – are not necessarily so important. It's better to learn more abstract, explanatory languages like Ruby and Python, easy to use, and built-in powerful tools that make it easier to feel fulfilled without compromising on programming, but at the expense of a bit of bottom-level knowledge-which can be made up from the computer architecture course.

After two months of objective-c, I thought it was too much trouble. Swift is simpler, but only for Apple-based platforms and not as a core foundation. The core foundation is nothing more than two classes: the bottom C, the high-level Python and Ruby. I believe that learning from the bottom of the knowledge will be more solid, but from the high school more consistent with the human cognitive law. So I decided to start with Python and break it down from high-level intuition to machine-level instructions.

I really do not know which books to choose as textbooks, but because I do not want to use pirated books, but also want to use the IPad to do everything, so simply buy the Kindle store and read more books in the store. And this is the Python Learning Handbook.

The author began by telling a bunch of Python's benefits, as if it were a language war. I do not know whether it is old, I began to think "this sentence the word is really special what meaning?" "What do you mean by high development efficiency?" How to measure development efficiency? Python's program is of high quality? How do you quantify program quality? How do you know if the program is an OS problem, a user problem, a hardware problem, or a programmer's problem? ............

You see, a lot of things are very complicated, many people put it to the simple, the next few happy conclusions, and then these things seem to be simple. It was as if Zhu said that physicists had reached the top of the mountain and found that Buddhism had been waiting there ... I'll go, who's going to talk to a Buddhist guru about quantum mechanics, the distribution of dark matter in the solar system? Anyway, you've been waiting on the top of the mountain.

To tell you the truth, I hate the notion of vague definitions--except for the point and the line--something that can't be defined ...

Reading the first chapter of this book, my brain automatically generates a bunch of questions, and I don't believe you see:

1. Readability (what is a standard or template that can be read?) ), consistency (what does that mean?) ), software quality (how to measure the quality of software?) ), reuse (how to reuse?) ）
2. Development efficiency (equivalent to c++/j Ava 's 0.2~0.3)
3. Portability (direct replication is possible?) Are you sure? ）
4. Standard library (NumPy)
5. Component Integration ( calls to and from C + + , integrated with Java)
6. What does fun ("Easy to use" mean?) What do you use it for? , "powerful built-in tools", what is powerful? ）

I was hopeless.

However, the author's sentence is quite occasional: "The late the mid 1990s, the internet brought about by the explosion, so that limited programmers difficult to cope with a wide range of software development projects, often require developers to develop the system at the same speed as the Internet evolution." “

My classmates are too tired to be in BAT every day ...

Python Learning Manual Note 1