3 ms·
Not trying to sound like a stick in the mud, since my need for Javascript build systems is modest and currently satisfied by make (think Bootstrap, jquery, ugli
by tomcam 11y ago
Not trying to sound like a stick in the mud, since my need for Javascript build systems is modest and currently satisfied by make (think Bootstrap, jquery, uglify). After all, dependency management is a deep problem.
What is the primary advantage over make? I imagine it looks much easier to read for a novice than make, but there are probably much better reasons than this one.
- kevin_kroe 11y agoi also use make, it fits really well with coffee/stylus/jade + zsh/iterm2|tmux stack... anything different than this seems to become very messy super fast, specially compared to make files not to say, using identantion kills a lot of stuff people use this days, like js linters and whatnot. not saying this tools are not useful in specific circumstances, which i can happily say i never faced. *with a "setup" target you could even install node.js or fly or whatever you need before even being able to execute fly.
- bucaran 11y agoInnovation fosters more innovation. We are trying to improve status quo. Even if this initiative fails, it may spark the right idea on the next person. Fly tasks are co-routine-wrapped generators, so you get modern async flow inside your tasks out of the box and right off the bat. TBH I don't know exactly how Fly is better than make since I don't use make since college years.