Re:Top Developer Tools of 2016
by shuntress on Wednesday January 11, 2017 @04:21PM
(#13377580)
I disagree. It makes more sense to me to consider the language the material or medium (that is shaped by a tool) rather than a tool itself.
To examine another simple example, consider a potter who crafts a vase from clay. The potter's wheel and his hands are the tools he uses to form the clay medium. I do not consider the clay itself to be a tool.
I think that the analogy fits. Javascript is more accurately represented by the clay than by the wheel. If your final product is "function foo(bar){...};" you are forming that function from javascript using a text editor. The same way a vase is formaed from clay using a wheel.
Also worth noting, the same way that vase can become a tool used by some other craftsman on some other project, that javascript could be packaged in a way that lets you take it with you to other projects. But just like the original clay is not a tool, the javascript isn't a tool. But the package you make with it might be.
To examine another simple example, consider a potter who crafts a vase from clay. The potter's wheel and his hands are the tools he uses to form the clay medium. I do not consider the clay itself to be a tool.
I think that the analogy fits. Javascript is more accurately represented by the clay than by the wheel. If your final product is "function foo(bar){...};" you are forming that function from javascript using a text editor. The same way a vase is formaed from clay using a wheel.
Also worth noting, the same way that vase can become a tool used by some other craftsman on some other project, that javascript could be packaged in a way that lets you take it with you to other projects. But just like the original clay is not a tool, the javascript isn't a tool. But the package you make with it might be.