Real Developers use Tools
I responded to this like I respond to everything on the Twitter — sarcastically:
Adrian responded in good humor, encouraging me to wait to pass judgement until I had actually watched the talk, saying the tweet was taken out of context.
Web developers want to emulate native apps, which he thinks is not possible.
Peter-Paul Koch complains in his talk about the complexity created by separating React from React-DOM. He misses that by separating these two components React becomes an interface for rendering UIs that can be implemented by React-DOM to render in the browser. By coding to the React interface we can implement renderers (renders?) for other UI environments like iPhone and Android in React Native, or Virtual Reality with React VR.
Browsers are adding too many features!
Excluding Yaddah Yaddah Yaddah because its a fake tool used to make the list look longer we deduce that the minimum amount of tools required to meet the “too many tools” threshold for a programming language is six. I wonder if the six count zero indexed? If so maybe we could add Yaddah Yaddah Yaddah back in.
In reality the modern JS stack looks more like this:
- Webpack (Replacing Browserify AND Gulp)
Six tools is not too many tools. Four tools is only two more tools than the Merriam-Webster definition of a couple of tools, which we can all agree is not that many tools.
Every language ever created has at least four tools that come with it, and at least one tool who created it. Because every language needs a package manager, build scripts, frameworks, and code analysis.
A key distinction of front-end web programming is that users download your code when visiting a web page, which means users get “punished” if your code is bloated. Source
Back end developers run their tools on something called a “server” which saves the client from loading the extra bytes these bloated libraries need to help us reuse code more efficiently. This part of the talk is especially confusing because front end tools are exactly like their back end counterparts in that the only library code that gets delivered to the client is the framework code.
We don’t measure a developer’s skill by the number of tools their programming language requires for same reason we don’t evaluate developer productivity by lines of code written: its a poor indicator that is easily manipulated.
So how do we measure real developers? Laurie Voss hit the nail on the head… Probably with a hammer… Which is a tool.
About the Author:
John used to be an enterprise Java developer for a large consulting firm. In his free time he enjoys large object hierarchies, inheritance over composition, and searching for overly verbose class names in the Spring framework.