Miroirs/rubyisforfun
1
0
Fork 0
mirror of https://github.com/ro31337/rubyisforfun synced 2024-11-16 19:50:09 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Minor corrections

Browse source 
1. Removed an unnecessary comma.
2. Removed unnecessary capitalization.
3. Changed a preposition to a more natural one.
This commit is contained in:
Anton 2022-02-02 02:37:38 +00:00 committed by Anton Shcheglov
parent 481ca593be
commit 015e84960c
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
manuscript/002-ruby-vs-ybur.txt
View file

@ -12,7 +12,7 @@ There is no need to compare the other parameters. In other words, if what is imp
### Learning something simple and interesting
Ruby incorporates the Principle of Least Surprise, and that is not at all bad.
JavaScript was not initially created in accordance with this principle. It is more complicated than Ruby, because it is completely asynchronous (you’ll have to take my word for that for the time being).
JavaScript was not initially created in accordance with this principle. It is more complicated than Ruby because it is completely asynchronous (you’ll have to take my word for that for the time being).
We can show that JavaScript is not as simple as it looks at first glance. Let us consider a Ruby program for sorting numbers:
@ -41,6 +41,6 @@ Once you understand it, it isn’t difficult. But the question is something else
JavaScript is developing very dynamically. Knowledge gained ten years ago is not always up-to-date (in this case I am speaking of popular frameworks - sets of tools). In Ruby’s case, the Rails framework has existed for more than ten years. Knowledge gained ten years ago is still applicable.
Incidentally, it is worth making a separate comment about the applicability of knowledge. Knowledge of shell-scripting languages is still applicable. Little has changed in more than 30 years. Knowledge of the basics of Computer Science is still applicable in interviews and at work (this knowledge has hardly aged at all). So it is definitely something you want to learn at some point of time.
Incidentally, it is worth making a separate comment about the applicability of knowledge. Knowledge of shell-scripting languages is still applicable. Little has changed in more than 30 years. Knowledge of the basics of computer science is still applicable in interviews and at work (this knowledge has hardly aged at all). So it is definitely something you want to learn at some point of time.
But no-one can make precise predictions about the applicability of a particular _programming language_ in the future. However, one may look at the statistics for recent years. At the time this book was being written, Microsoft bought GitHub, written in Ruby, for 7.5 billion dollars. In other words, the language is in fine form today and widely used. Updates are being issued, the speed and syntax are being improved. And the number of available libraries makes a rapid solution of virtually any problem possible (within the framework of the field called web programming).
But no-one can make precise predictions about the applicability of a particular _programming language_ in the future. However, one may look at the statistics of recent years. At the time this book was being written, Microsoft bought GitHub, written in Ruby, for 7.5 billion dollars. In other words, the language is in fine form today and widely used. Updates are being issued, the speed and syntax are being improved. And the number of available libraries makes a rapid solution of virtually any problem possible (within the framework of the field called web programming).