The keyboard shortcuts for math input are so nice! I have tried Lyx and Mathtype, and still found GNU TeXmacs better.

It's pleasing to see the following in the "donate" section:

"If you are interested in the intersection between technology and politics we invite you to donate to the Electronic Frontier Foundation ( https://supporters.eff.org/donate ). For 25 years the EFF has been a champion for civil liberties, privacy, and education on politics around emerging technologies. With your support they will continue to aid in technological progression with humanity in mind."

Structure and Interpretation of Computer Programs. This famous book emphasized controlling complexity and how to build a structure that is easy to extend.

The cost of complexity is exponential -Rob Pike

The release notes: https://spark.apache.org/releases/spark-release-1-4-0.html

Another major change is that it supports Python 3 now. https://issues.apache.org/jira/browse/SPARK-4897

They've integrated Tungsten / native sorting into shuffle and observed some decent speedups:

* https://issues.apache.org/jira/browse/SPARK-7081

* https://github.com/apache/spark/pull/5868#issuecomment-10183...

However, I guess reduceByKey (and friends) don't benefit yet.

Their SGD implementation still uses TreeAggregate ( https://github.com/apache/spark/blob/e3e9c70384028cc0c322cce... ) so I wonder when they're planning to add some of the "Parameter Server" stuff (e.g. perhaps butterfly mixing or Kylix http://www.cs.berkeley.edu/~jfc/papers/14/Kylix.pdf )

There is an important difference between the algorithm and personal career: climbing the other hill has nothing to do with climbing the highest hill, but that's not the case regarding career development. Startups are creating new things and jobs, so how do you know that current jobs would not provide valuable assets in the future?

Similar thoughts were seen in the SICP book.

"In this book we don't use many comments; we try to make our programs self-documenting by using descriptive names."

http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-15.html...

From the era when two poles were Lisp and C, I can sort of see that. In part because of the preference for longer identifier names in Lisp, versus cryptic abbreviations in C, some kinds of comments prevalent in C aren't as necessarily in Lisp. Instead of atoi() you'd have something like convert-ascii-to-integer.

In modern Lisp, though, it's still considered good form to include both a docstring, and internal comments explaining anything particularly tricky.

I find that your "Apply to YC" path is also very interesting. http://www.mysliderule.com/apply-to-Ycombinator

Haha thanks, that was just a fun side project when we were applying to YC S14. :-)

It's also interesting to think about the points mentioned in PG's "Being Popular" [1]. I think the most important one is "to have a system to hack". Emacs lisp is popular because of Emacs, Javascript is popular because of the web, and how about Haskell?

[1] http://www.paulgraham.com/popular.html

Xmonad! Seriously, it's a great window manager that has brought a lot of people into Haskell.

Thank you. I enjoyed the read very much. I agree with you that Asia is going to be an important market.

Some quick thoughts: 1. It should be good to create a "Silicon Valley-Singapore" or "Silicon Valley-Taiwan" ecosystem to bring the startup culture, funding, and people who know local market together. 2. Although “American companies really suck at international expansion and localisation," as said by Werner Vogels, I am afraid that Asian companies do not have much success either? I could only think of NAVER LINE as an example.

Thanks. I just tried to put it in less than 80 characters. Your suggestion is more accurate, but I could not change it now.