Over the past three weeks I’ve had the opportunity to investigate modern web development tools and I feel a little bit like a kid in a sweet shop. Firstly, I’m excited to be here. Secondly, there’s so much to choose from. In the past you may have been able to pick up a selection box containing a few pre-defined dev tool options. Now, there are so many technologies and tools available it’s like being in the pic ‘n’ mix section.
There are so many tools to choose from when undertaking a web development project that it’s difficult to know where to get started. How do you approach choosing what’s right for your project? How can you really know without trying them all out?
Let’s be honest; very few of us have time to really try out everything.
So, you probably choose techniques, technologies and tools that have similarities to the ones you are familiar with, the ones used and talked about by those you ‘follow’ and from selective reading and testing.
“Node.js is trending; we should probably try that out”
“We can now loosely couple our web front-ends from our backends thanks to modern browsers and by building APIs”
“I’m seeing Yeoman mentioned a lot and those guys from Google are involved in it; that must be the way to go”
“I’ve seen people migrating from TextMate to Sublime; we should be using Sublime”.
From runtime to editor; it’s a minefield that has to be navigated quite frequently as technology naturally progresses at an amazing rate.
A lot of us (developers) like to have the choice. We like picking the pieces of technology that suit us. Our development workflow really is created from a pic ‘n’ mix of tools; from runtimes, to productivity apps, to editors, to build tools, and beyond!
IDEs (Integrated Development Environments) were commonplace in the not too distant past. But now, and for quite some time – in the scripted-language circles I’ve been in, anyway – there has been little use of IDEs and the choice has been to pic ‘n’ mix web development tooling. There are obvious benefits in being able to select small tools that do one (or a few things) very well.
Editors: Sublime, TextMate or Vim combined with editor customisations and hooks into the terminal/console represent a common web development setup. The terminal is then used to kick off tasks from running tests to full builds and deployments. Certainly no pointing and clicking.
The real need for effort comes when those tools – executed from the terminal – have to integrate with each other. Scripts have to be written, tested, debugged and managed in the very same way as the code for the product that’s being built. It feels like we’re spending more and more time playing with tooling and less time creating products. Others seem to agree.
Relatedly: I'm often concerned that the web industry is getting way too hung up on techniques/tooling than the actual product/thing itself.— Matt Andrews (@mattpointblank) July 15, 2013
Also see Matt’s post, The web: less engine, more gas
Some developers – and businesses – simply want a set of web development tools, and a runtime stack, that just works and helps productivity as close to “out of the box” as possible. This may be through buying-in to a technology stack such as the ones provided by Microsoft (whether you like it or not, Visual Studio is a solid IDE and developers can be very productive using it) or by using a web toolkit which consists of a collection of small tools pre-configured in a way that has been agreed by the toolkit’s contributors to be a productive default.
These don’t provide editors, but do provide things like:
- default application structure (skeletons) from templates
- scaffolding functionality to help generate common files for common functionality (e.g. models, views, controllers and tests)
- development runtime tools (e.g server and logging)
- a common build process
They also generally provide some sort of plugin or extension support. Exactly what can be customised by these really depends on the toolkit; Yeoman appears to be massively flexible while Mimosa is a little more restrictive.
You could still look upon these toolkits as being too flexible, or as requiring too much additional configuration, but the defaults are consistently being reviewed – Yeoman only at 1.0 release candidate 1.
I’m particularly interested in Yeoman. It’s already had great take-up by a community that live on the cutting edge and has had a large number of contributions. It consists of Grunt and Bower which both have a high level of adoption on their own. What interests me is that I can see a number of light weight wrappers being created around these tools to provide more defined (rigid/opinionated) developer workflows that fit certain work environments or where some development processes need to be adhered to; maybe the types of environment that IDEs presently inhabit? This may require an acceptance of Node.js in larger institutions, but I think that’s coming and is certainly being helped by Microsoft’s adoption of it and incorporation in Windows Azure.
Would the wider, more cutting edge community, adopt a more defined workflow if it were proven to help productivity and could demonstrate that using it resulted in quality scalable web applications?
Pic ‘n’ mix web development tooling is popular right now, but maybe the day will come when a number of proven quality selection box developer toolkits – consisting of the very best of the pic ‘n’ mix – will return to popularity?