Earlier quoted context omitted.
And yet most contemporary hipster build systems are all just shiny make reinventions.
Reinventions that are cross-platform (this actually matters).
The Ultimate Frontend Build tool: make
41–50 of 121 posts
Re: The Ultimate Frontend Build tool: make
#42Earlier quoted context omitted.
A cursory google search should have shown that gmake (GNU Make) is widely available and used on FreeBSD.
Yes it is available and I guess I sort of boxed myself in when I said not available. It's not available as a default install ... at least not on the FreeBSD 10 install disk I used.
Re: The Ultimate Frontend Build tool: make
#43God I hate make. I hate make so very, very much. Compiling code isn't that hard. I swear to the programming lords on high it isn't. Here's a wonderfully useful open source project - Google gperftools [1]. It includes TCMalloc amongst other things. The Makefile.in is 6390 lines long. Configure is 20,767 lines long. Libtool is 10247 lines long. That's fucking insane. Compiling OpenSource is such a pain in the ass. Part…
Count me in as a Makefile hater. I'm even using it to manage a portable /home directory and it's just making me hate it even more. Why did all the alternatives have to fail or be worse than Make?
http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to...
Re: The Ultimate Frontend Build tool: make
#44Re: The Ultimate Frontend Build tool: make
#45Somewhat relevant: I've also found gulp much easier to use and maintain than Grunt.
Re: The Ultimate Frontend Build tool: make
#46Earlier quoted context omitted.
Reinventions that are cross-platform (this actually matters).
What platforms doesn't make support? AFAIK GNU make supports pretty much everything and there are versions of make for Solaris/BSDs.
Re: The Ultimate Frontend Build tool: make
#47https://gist.github.com/Breton/7556390
This enables you to put a lot of your configuration in a json file, such as actual lists of files (which make is actually terrible at), have a decent way of getting json data out into make processes, and build files templated out of that json configuration, such as ssi files that set whether to load built JS or seperate script tags (also generated out of the same json config).
SO you get the declarative stuff in the declarative JSON format, and the stuff that make is good at: incremental builds, stays in make.
Re: The Ultimate Frontend Build tool: make
#48You can't write a blog article about make while comparing it to a bunch of Node.js build tools and not mention the word Windows once. Make is good for you because you're not an open-source project built on a cross-platform development platform. All of your employees use Macs and your servers are Linux. For OS Node projects make is simply out of the question because it is janky on Windows and every makefile ever writt…
Re: The Ultimate Frontend Build tool: make
#49While I'm a big fan of the Unix Philosophy, I've found gulp to be incredibly satisfying as a build tool. I cd into my project directory and run gulp, then all my SCSS/CS gets compiled, watched, and re-compiled on change, with LiveReload pushing style changes straight to the browser; and whenever I make a change to my server (Node.js) code, it gets compiled and run against my tests. Then when I'm ready to push to prod…
With that being said, it's miles above Grunt.