Drush vs. Drupal Console

What's the Dif?

We have officially entered the world of Drupal 8. With it comes both the old and the new, and in the new category there is a fresh command-line tool for developers. It's called Drupal Console . There are a lot of questions about it, like the ones you just asked yourself: "What happened to Drush?" "Why do I need to switch to Drupal Console?"

Do not fret, I'm here to help. I'll explain the similarities and differences between the two. I'll also show you a few new things that Drupal Console brings to the table to improve your developer experience in the Drupal 8 era.

Drupal [1] is an open source content management system (CMS) that powers some of your favorite websites. Drush [2] and Drupal Console [3] are both command-line tools that interact with an existing Drupal installation or help you get one up and running. Both of these tools help developers increase their productivity by reducing the time it takes to do the same tasks without them. They are extensible with custom-written commands and personalization of configuration files. Beyond that, these two tools begin to diverge from each other ever so slightly.

The shift in Drupal 8 to the Symfony framework [4] has made things different, much different even to the veteran Drupal developer. Drupal Console is written with both the veteran and the new-to-Drupal developer in mind. Its primary purpose is to assist a developer's transition to the world of Drupal 8, and it is only intended to be used with Drupal 8 – mainly for development reasons, much less in the context of a production website.

What does this mean for Drush? Well, not too much. Drush still functions much like it always has, and is still deeply part of the Drupal ecosystem. In the areas that

... comments powered by Disqus