title: Is it possible to use multiple template engines in Sails.js?
body: <h1>Express</h1>
  
  <p>In vanilla Express.js, the following code works nicely.</p>
  
  <pre><code>var app = require('express')();
  
  app.get('/jade', function(req, res) {
    res.render('slash.jade');
  });
  
  app.get('/ejs', function(req, res) {
    res.render('slash.ejs');
  });
  
  app.listen(1338);
  </code></pre>
  
  <p>As long as the modules are present in <code>node_modules</code>, both templates are rendered by the appropriate engines. </p>
  
  <p>You can also specify a default engine like so:</p>
  
  <pre><code>app.set('view engine', 'haml');
  app.get('/', function(req, res) {
    res.render('slash'); //looks for slash.haml in views directory
  });
  </code></pre>
  
  <p>In Express, the default view engine is only used when <a href="http://expressjs.com/en/api.html#app.settings.table" rel="noreferrer">the extension is omitted</a>.  </p>
  
  <h1>Sails</h1>
  
  <p>In Sails.js, it seems like the engine specified <code>config/view.js</code> is the only engine ever used. </p>
  
  <p>If I try to specify the extension directly, I get the following error:</p>
  
  <pre><code>error: Ignoring attempt to bind route (/barn) to unknown view: barn.jade
  </code></pre>
  
  <p>Is it possible to use different view engines without a large amount of voodoo in Sails?</p>