that&#x27;s a silly&#x2F;wrongful quote IMO... I&#x27;ve produced&#x2F;recorded music for over 20 years and loops from other people are not only cheating, they are not your damned recordings and you sound like every other loop-arranger out there... it&#x27;s not really that difficult to record real-world sounds and guess what!? you can use those same audio tools (your daw + plugins etc) to manipulate and sweeten YOUR recordings just as easily as you do with others recordings aka loops.
making music with sample-pack loops is basically just dj&#x27;ing&#x2F;remixing... which I also have done for over 20 years so I know the difference...
Using boughten drums is not cheating, as it&#x27;s generally about the way you tune them and play them that make the difference, versus loop manipulation that literally is about modifying otherwise sample-for-sample copies...
Guitar tonality = 80% in the fingers and the ear&#x2F;mind of the player... The pickups and amp&#x2F;pre-amp combination DO make the other 20% perhaps...
As for making drums from goat-skins, well it&#x27;s not exactly rocket science...<p>now, onto the the problem I have with the actual issue at hand: it&#x27;s not like the author is saying to write your libraries in assembler. he&#x27;s saying that maybe you don&#x27;t need to include gems upon gems that themselves reference other gems, as the dependencies pileup and get ridiculous and the performance suffers, which is actually a major concern with Rails and other monolithic frameworks with single-threaded processing etc.
for crying out loud, he&#x27;s even giving you permission to specify your behaviors with a ridiculously high-level concise language aka Ruby... how much more direct and obvious can a point be and still be missed?