351 karma · joined November 7, 2011
What does this tell you?
I am sure my cousin in law would not agree with whatever I could have written in NYT as a member of the Tibetan elite though.
What I am saying is that the elite may not represents the best interests of the people they claim to represent.
On the other hand, theocracy is never a good thing. Separation of state and religion is.
As to cultural revolution, there's nothing special in Tibet. Fired up populace did all the damages. At that time, Tibetan common people were equally zealous about Chairman Mao, if not more so.
On the ground, for the people, the real justification are different. It used to be the liberation of common Tibetan people from a regressive serfdom and a brutal theocracy, not unlike the communists' justification for themselves elsewhere in China. Similarly, after Deng, the justification is more about improving people's economic status and living conditions.
I grow up in Seda County in the late 70 and early 80s, and am intimately familiar with culture there. Tibetan Buddhism is not what people in the west think what it is. It is actually quite repressive and brutal. After 1950s, many regular Tibetans were glad to worship the new religion of Chairman Mao instead. Yes, it was true. Chairman Mao was worshiped as one of major Gods at Tibet when I grow up there. Then Deng Xiaoping took power and demolished Chairman Mao worshiping (one of his major blunders, on the same scale as that of 89 Tienanmen massacre), now we got this huge slum town of "religious learning" at a hot basin of Buddhist rebellions. Yes, going unchecked, that town would surely become such a terrorists base, because Buddhist monks in that area had always been very militant and had launched numerous rebellions in 60 and 70s. As a child, I heard all kinds of horrific stories Tibetan monks and their rebellious army inflicted on the Chinese soldiers and civilians alike. For that reason, many Han Chinese families kept firearms at home in that area, a rare thing in China.
On the other hand, Tibetan people in general are good people. One of my cousins married a Tibetan man and we are good drinking buddies. However, Tibetan religious upper class are representatives of a theocracy at worst: greedy, deceptive and brutal.
I am surprised that this town was tolerated for so long. I guess Deng's power was still strong even after his death.
Read Washington DC. vs. Heller to understand this. Don't argue on the Internet.
What neural network have demonstrated so far is that it can do a form of perception given enough ground truth data. Speech recognition and image recognition are all form of perception. Go playing is also mostly about perception: recognizing good patterns.
There are multiple issues with extrapolating this achievement to anything more than what it is.
First, perception is a only minuscule part of the brain's functionality. One only needs to glance at the table of content page of any cognitive psychology 101 textbook to see that. Second, it is not clear human's perceptual ability is the same as what NN has demonstrated. For example, human's perceptual learning is mostly based on unsupervised learning, not supervised like in NN.
Finally, his dismissal of "traditional" approach is extremely short-sighted. He seems to suggest that we can solve AI by just throwing more hardware and power at NN. This view is very narrow minded.
He also seems to overlook the high possibility that the "traditional" approach could benefit similarly from the advances in hardware and power. I predict the next breakthrough in AI will come from that direction.
Human has unlimited memory capacity and fast memory access, whereas human logical processing power is fairly limited and error prone. That's why any real human language has a large vocabulary.
Basically, you are saying, when the max of a sequence is increasing, the mean/median stays or even decreases. That would require that the frequencies on the lower end to increase much faster than that on the higher end, which is certainly not the case. For example, the number of C programmers is growing faster than the number of Java programmer today? No one would think that's correct.
Computer science has too short a history to make any sound arguments from history. However, if you insists on arguing from history, let's look at the long term trend. Would you agree that the trend of programming language is progressing to higher and higher level of abstraction and further and further away from the machine details? From machine code, to assembly language, to C, to Java, and now FP languages, this trend of mainstream programming language evolution is very clear. In this sense, if you take Lisp as a pioneer of function programming, it was simply ahead of its time.
If you are implying that Lisp syntax is somehow an impediment to its popularity. That may well be. It's a personal preference issue. Some people like more syntax in their language, some people like less. If you are in the later camp, Lisp is surely very attractive. For example, in your kotlin one-liner, there are just too much syntax to understand "()", "..", ".", "{}", etc. Life is too short, I just don't want to learn all these idiosyncrasy invented by someone just for the sake of being different. I wished I had knew Lisp sooner, certainly not having programmed for 20 years.
I am sure you will lose that bet.
In Clojure, readability is obtained through standardization. Every Clojure programmer instantly knows what the functions in the standard library do. Because there's not much syntax in a Lisp, code is very easy to read once one knows the functions.
Any competent Clojure programmer would likely have known most of the Clojure core functions by heart: map, reduce, filter, etc. There are maybe about a hundred of them?
Unlike imperative programming languages, where you use three primitives (assignment, condition and loop) to construct everything, in Clojure, you use these core functions to construct your program. In a sense, the process of learning Clojure is the process of learning the use of core functions. These functions are simply at a higher level of abstraction than the three primitives, hence some people say that Clojure is more expressive, because it's closer to human thoughts than Von Neumann machine specificity.
The Clojure coding process is REPL driven, so basically one tests every changes. Also, one codes in a bottom up fashion, starting from simple and small functions, and composing them into big functionalities. There' no big design up-front. It's an exploratory process, and it's fun.
Yes, macros are good for developing DSLs, so they are mostly used in developing libraries, but most application developers do not need to use macro. The wide spread macro usage probably contributed to the fragmentation of CL community. Taking such lessons to heart, Clojure library authors tend to reuse commonly accepted DSL forms, e.g. hiccup is the DSL for writing HTML, and most authors have adopted it when developing their own libraries. I think this is a good thing.
The feel of programming in Clojure is very very different from what you are describing in a language such as Java. I have programmed Java since 1997, ever since I switched to Clojure, all those pains and fears of changing code has evaporated. I am not afraid of changing things in Clojure at all, because I know the effects of my changes are local.
Of course, Clojure toolings do include some convenient features such as "extract function", "rename symbol", etc, but these are just some niceties that save some typing and editing. They are not indispensable like those in Java.
A fundamental point in the philosophy of Clojure is the emphasis on raw data. This is actually the reason why we love the language, because it lets us work directly with data, instead of dealing with language related complexity, such as API, type, syntax, etc. The Clojure community only realizes this advantage a couple of years ago. This Rich Hickey's talk in JavaOne gives a flavor of this idea: https://www.youtube.com/watch?v=VSdnJDO-xdg
As a person who doesn't even know what language this is written in, I don't think it is readable at all. For example, this "Select(i => i + 2)" piece looks totally strange for me. What does it do?
After learned Lisp, I feel there's too much syntax to learn for non-lisp languages. Every language introduces some idiosyncratic syntax. Life is too short, I just don't want to learn syntax that someone else invented to just be able to say "this is different".
Of course, renaming symbols in Clojure is not such a big requirement as in Java IDE, because most of the things are isolated within a single function in Clojure. Consequently, renaming symbols is just a convenience feature, not a must-have feature for Clojure development.