The Village поговорил с людьми, которые работают руками и зарабатывают больше простых офисных работников

http://www.the-village.ru/village/business/citypeople/240825-bogatye-rabochie

Well, alright, since you asked...
Python is a pretty okay first language, with a tendency towards style enforcement, monoculture, and group-think. Python is more interested in giving you one adequate way to do something than it is in giving you a workshop that you, the programmer, get to choose the best tool from. So it works well for certain problems that can use an existing tool, but less well for other problems that require a machine shop to make a new tool. For instance, if you only want to think of your list processings as list comprehensions, Python 3 tends to enforce that culturally. If you want several ways to map over a list depending on which order makes more sense in context, Perl 6 will be more accommodating. If you want concurrency with a global interpreter lock, Python might suit. But if you want a concurrency model designed to scale to multicore/manycore, look to Perl 6, which avoids global bottlenecks and non-composable primitives, but instead borrows composable ideas from Haskell, Go, Erlang, and C# instead.

— Larry Wall, when asked what he thinks about Python. (Thanks to Paul Wise.)
https://developers.slashdot.org/story/16/07/14/1349207/the-slashdot-interview-with-larry-wall

I mean, we can certainly stop developing Fedora, because of fear that fixing things might break apps we never heard of that rely on a very specific bug or misdesign in some very specific software. But I am not convinced that fear-driven development is really the best strategy to win the future...

угадал автора

C to Rust translator (written in Haskell)

https://github.com/jameysharp/corrode