ytimoschenko

You can't be sure it is him, it could be someone else from the company he'd worked at. The page is just a mirror of their old company's website.

And it was a long time ago, I've submitted this page purely on historical reasons. Don't treat it this way.

And yeah, give Erlang a try. It is the best thing since sliced bread.

OS X on MacBook Air, OpenBSD on servers.

I use Make, Vi, and interpreters/compilers of various programming languages (Erlang, Golang, Clojure, Perl, etc).

I also use most of generic software from OpenBSD base.

Sticking with the same set of technologies is a premature death for your career as a programmer.

The whole article builds up on a point that people tend to fail more when they are using new tools. That point is false. In reality, when you use a wrong but ’accustomed’ tooling in inappropriate situation, you end up writing code that you would never write if you had chosen right tools. You are effectively reinventing the wheel.

You also have an idea about ’innovation tokens’ that builds up on a static representation of weight of a new technology in a project. That is ridiculous.

There is no definition of ’boring’ in this article. I don't understand why you call PHP, Postgres and Cron ’boring’. What is ’interesting’ then?

It seems like you have made a wrong choice while thinking about the problem. The problem is clear: people fuck up projects by using modern, hyped technologies that are inappropriate for project's domain. They are just as wrong as you are.

Core Bitcoin: https://github.com/oleganza/CoreBitcoin

Bitcoin Core: https://github.com/bitcoin/bitcoin

Now it is Bitcore. Project names are hardly distinguishable, feels kind of messy.

The same here.

You are completely missing the point.

The first problem is: reasons you've listed are stereotypical rants that young PHP developers say. Reasons #2 #4 #7 #9 are just false. For templating here you are: http://tornado.readthedocs.org/en/latest/template.html, the others you could find yourself. Moreover, reasons #3 #6 just don't matter (who cares about quantity of books on PHP? Do you need to read them all? Functions beginning from _ not being imported is not enough for your encapsulation needs?), and #5 #8 are completely subjective. Please don't say any more of that.

The second problem is: you don't understand that language is just a tool to solve your problem. You should find a suitable tool for your problem, not vice versa. While it is definitely easier to build classical websites (no websockets) in PHP, you won't be able to write a system daemon or SMTP server or a concurrent messaging server in PHP.

You shouldn't concentrate on one tool, it is slowing you down. Python is great when it comes to science: https://wiki.python.org/moin/NumericAndScientific, you won't find this number of scientific packages anywhere but in Python. It also, in my opinion, is much better suited for API servers than PHP with its perfect Flask http://flask.pocoo.org and creepy but pretty fast Tornado http://www.tornadoweb.org/en/stable/.

There are dozens of languages that everyone should use in their specific domain. Erlang for stable concurrency systems, Go for productive network and system programming, PHP for building simple websites, Python and Julia for scientific applications, Lua for embedding, Perl for parsing and scripts, Clojure for general-purpose language with immutable structures and concurrency, Haskell for learning great new ideas.

Programmer should be able to program on everything, that's the difference between a programmer and just a person who needs a website.