November 2017
Intermediate to advanced
670 pages
17h 35m
English
If you have spent most of your time up to now programming in other languages such as Ruby, you may be surprised when you get cyclic dependency errors.
Why are there no cyclic dependency errors in a language like Ruby?
First, Ruby is an interpreted language, so we will never get a compile error. Furthermore, Ruby determines the scope by namespaces. As long as Ruby has a unique reference to a block of code and that code has been loaded into memory, there should be no dependency reference errors.
Does that mean Ruby is better than Go in this respect?
It depends. Do we want to develop as quickly as possible without concerning ourselves with the dependency rule? Do we expect our application to grow complex over time? Do we ...