syko

It does however spell out the right conclusion: a) it doesn't have to be a replacement and b) configuration vs code.

Btw there's also brunch (http://brunch.io) that you might want to check out. That one really does need only minimal configuration.

I wrote an article about all three not too long ago: http://blog.toggl.com/2014/03/grunt-vs-gulp-vs-brunch/

Call me paranoid, but this looks like a good tactic to spread the maximum amount of Fear, Uncertainty and Doubt into the already-collapsing Flash community while still keeping support for the platform.

Reminds me of the OpenGL vs DirectX wars. (not implying the situation is similar in any way, only the FUD tactic :) )

http://blog.wolfire.com/2010/01/Why-you-should-use-OpenGL-an...

I agree. Unless all you know are functional languages, you should understand all of these concepts. Of course, we don't know what the recruiter's idea of "clear and concise" answer is.

I would just like to note that the have an error on that page. <b>Warning</b>: INSERT command denied to user &#039;dbo325141527&#039;@&#039;74.208.180.97&#039; for table &#039;bs_watchdog&#039; query: INSERT INTO bs_watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (0, &#039;php&#039;, &#039;%message in %file on line %line.&#039;, &#039;a:4:{s:6:\&quot;%error\&quot;;s:12:\&quot;user warning\&quot;;s:8:\&quot;%message\&quot;;s:655:\&quot;INSERT command denied to user &amp;#039;dbo325141527&amp;#039;@&amp;#039;74.208.180.97&amp;#039; for table &amp;#039;bs_accesslog&amp;#039;\nquery: INSERT INTO bs_accesslog (title, path, url, hostname, uid, sid, timer, timestamp) values(&amp;#039;Cybersecurity For The 21st Century, Hacking Challenge: Change this website&amp;amp;#039;s homepage picture and win $10K and a position working with Senior Cybersecurity Advisor, Joe Black. DONE, THAT WAS EASY. KEEP YOUR MONEY WE DO IT FOR THE LULZ&amp;#039;, &amp;#039;node/1&amp;#039;, &amp;#039;http://www.google.com/reader/view/?at=A_uCkSZxuRDNUf in <b>/homepages/6/d325020610/htdocs/includes/database.mysql.inc</b> on line <b>128</b><br />

Not only is the UI bad and filled with popups, frames and java-based security features, a friend of mine had to take a web-based test through the blackboard system and the test was all based on JavaScript - You could actually find out the correct answers by viewing the page source!

Not leaving the polish for the last. I've noticed that it's bugfixes and the final polishing that are the most tedious (everything's done and most of it works).

I now polish, test and debug every bit of the project as I go along. It's very tempting to pinch all the fun parts out of the project right away (the core functionality) and leave the little stuff to the end, but this is gonna leave you with heck of a lot of little things to do after the project's ready.

But once you're already trapped in the little things, it's the todo lists: dividing it all up into as little pieces as possible and going at them one by one. This also forces you to measure how much of it is still to be done - otherwise you feel like every one of those last bits is going to be the last one. And when it isn't, it's going to feel like puke. .. and fixing bugs like this is also prone to create other bugs.