You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@OneSeven, I think there is no special reason. @0xAX set it up like that at the beginning and it does the job. Since we don't build the semantic-ui project during the angular-semantic-ui building process, no matter if we use Grunt or Gulp (IMHO).
I used to build my projects with Grunt and to be honest, I never needed Gulp. What could be benefit of switching to Gulp?
We need better reasons to switch to Gulp. We never had trouble with it and Grunt is still maintain.
I keep this issue open and wait for more pro and con
Keep using Grunt, you already have it implemented. There's no reason to switch, it will only cause more hassle. To choose either, do so at the beginning of a project, not halfway through.
If Grunt works for you, use Grunt. If you prefer Gulp, use Gulp.
Also as mentioned, the official SemanticUI uses Gulp but you aren't building SemanticUI, so that has nothing to do with the other, stick with Grunt.
I noticed that official semantic is using gulp for building tools, why angular version are using grunt, any special reason?
The text was updated successfully, but these errors were encountered: