Explore how to get angry in a technical community and talk about Haskell's learning and Application Path

My blog column is named "a column that few people Reply ". This is also true, with fewer people looking at and fewer replies.

Helpless, I have always chosen a very small number of things. The Haskell language is regarded by most people as a tool for research and learning even among study researchers, without considering its practical use.

Even in tietong
Haskell has fallen out of the top 50 in this ranking. The best result in history is 32. Compared to Erlang, there are now 28 users, which are often promising.

I started to actively participate in Python five years ago.CommunitySo far, Python has ranked among the "Standing Committee. So I don't need to introduce Python any more.

 

Let's talk about how to get angry. In the developer community, there is a very simple way to be called a "celebrity": A verbal war. Because the technicians are relatively pure or simple. This is not an easy argument, because I am also a technician. It is easy to become paranoid, coupled with prejudice and preconceived factors. It is easy to blindly maintain the concepts and ideas you know.

As a result, it is difficult to think about the following topics:

 

• Is technology promising? Is it necessary to switch to the bank for management, products, and markets?
• Java and C # which is more promising?
• Windows is too bad.
• Linux is too bad.
• Mac is too bad
• Vim is better than Emacs (this is not obvious in csdn)
• Oo is good.
• EJB Nb or spring Nb
• How sinox beat Microsoft
• How Linux beat Microsoft
• How HTML5 beat flash
• Open-source software defeating commercial software
• Free Software is not open source software

......

 

I 'd better hide in the corner of Haskell.

 

Think back to the pain of learning HASKELL: there is almost no Chinese information, and the only Chinese Blog only introduces some functions in prelude for a math game. Let's look at the English documents. I don't know where to start learning it. When it comes to types, monad, catalog, a lot of things. It seems that you want to learn how to drive, but throw you a pile of books on mechanical principles, internal combustion engine structures, and so on. It should be said that I am interested in these principles, structures, and other basic theoretical things, or I will not stick to it.

But for a practical purposeProgramPersonnel, this is not necessary.

He can use it to write something that is suitable for Haskell. Instead of taking care of monad, monad transformer, and so on, he can first set up the development environment and write utilities, find the library to be used, learn and use the library, learn theoretical things slowly, and then read some theoreticalArticle.

Theory guides practice, but it is necessary to have a simple understanding in practice, so that the theory will not be empty.

Therefore, this column has not involved much theoretical content in functional programming since its establishment. The content is much written by others than me. What is missing now is a practical guide.

 

I hope more and more people will discover the beauty of Haskell and apply it to their daily work.