Replace Grunt with with Gulp about baumeister HOT 10 CLOSED

A big nope! We do not send our sensitive data through the internet. Considering the potential of having unreleased layouts this is a no-go.

The measured times are sobering however. It looks like you used features from Gulp 4? I think gulp 4 is not stable yet and I know they have some issues they want to have resolved (1, 2) before the official release.

from baumeister.

At the moment there is a minimal performance advantage for Grunt.

The following is measured:

• Less compiling
• Auto prefixing
• Sourcemap generation

1.07s vs. 955ms

$ gulp styles
[00:37:09] Using gulpfile ~/Documents/Projects/bootstrap-kickstart/gulpfile.js
[00:37:09] Starting 'styles'...
[gulp] less compiling: 808 ms
[gulp] auto prefixing: 341 ms
[00:37:10] Finished 'styles' after 1.07 s

$ grunt styles                  
Running "less:dev" (less) task
>> 1 stylesheet created.
>> 1 sourcemap created.

Running "autoprefixer:dev" (autoprefixer) task
>> 1 autoprefixed stylesheet created.
>> 1 sourcemap created.

Done, without errors.


Execution Time (2015-12-21 23:37:57 UTC)
less:dev          696ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 73%
autoprefixer:dev  255ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 27%
Total 955ms

But I ❤️ the way and simplicity of Gulp. So I will continue with the dev task in the gulp branch.

from baumeister.

woot. How is grunt faster without using pipes and at the same time creating and removing tons of temp files... This is magic. THIS. IS. MADNESS.

However, the grunt vs gulp startup times are not measured yet.

from baumeister.

jep sounds weird 😂

from baumeister.

Just because it doesn't uses a "magic" tec, it doesn't has to be slower.
Bootstrapping and other weird stuff can take away all advantages. It will be interesting how much faster it is when it is started and running the processes over and over :)

from baumeister.

@tuxBurner X-Ref: #42

from baumeister.

@tuxBurner

Just because it doesn't uses a "magic" tec, it doesn't has to be slower.

It’s not magic but the fact that Gulp can handle task parallel instead of sequential which is a big plus compared to Grunt 😘

from baumeister.

I’m done with the dev task.

Final result:

• Gulp → 6.55 s
• Grunt → 2.8 s

Grunt:

Execution Time (2016-01-02 20:40:38 UTC)
clean:server       34ms  ▇▇ 1%
less:dev          713ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 26%
autoprefixer:dev  259ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇ 9%
copy:server       125ms  ▇▇▇▇▇▇▇ 4%
generator:dev      40ms  ▇▇▇ 1%
htmllint:all       1.1s  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 39%
bootlint:files    219ms  ▇▇▇▇▇▇▇▇▇▇▇ 8%
eslint:target     306ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 11%
Total 2.8s

Gulp:

[21:37:07] Starting 'dev'...
[21:37:07] Starting 'cleanServer'...
[21:37:07] Finished 'cleanServer' after 68 ms
[21:37:07] Starting 'parallel'...
[21:37:07] Starting 'scripts'...
[21:37:07] Starting 'css'...
[21:37:07] Starting 'copyLibsToServer'...
[21:37:07] Starting 'html'...
[21:37:08] Finished 'scripts' after 1.07 s
[21:37:09] Finished 'html' after 1.42 s
[21:37:09] Finished 'css' after 1.42 s
[21:37:09] Finished 'copyLibsToServer' after 1.51 s
[21:37:09] Finished 'parallel' after 1.51 s
[21:37:09] Starting 'parallel'...
[21:37:09] Starting 'htmllint'...
[21:37:09] Starting 'copyAssetsToServer'...
[21:37:09] Finished 'copyAssetsToServer' after 18 ms
[21:37:14] Finished 'htmllint' after 4.96 s
[21:37:14] Finished 'parallel' after 4.96 s
[21:37:14] Finished 'dev' after 6.55 s

The biggest problem is HTML validation using gulp-html taking approximately 4 seconds. If we would replace that with gulp-w3cjs we could take the dev task down to 3 seconds and make it as fast as Grunt. But we don’t want to send our markup through the internet, do we?

from baumeister.

This change is in the making.
Grunt is gone in the v4-dev branch and almost every task has been replaced.

See #127 for details.

from baumeister.

Done 🎉

from baumeister.