9 ms·
> None of these "fancy" tools still builds by a traditional make command. Is there anything more "get-off-my-lawn" than "These tools don't use the thing I like
by pc86 9y ago
> None of these "fancy" tools still builds by a traditional make command.
Is there anything more "get-off-my-lawn" than "These tools don't use the thing I like!"
- ProAm 9y agoIn reality it's all peachy until stuff doesn't work and no one knows why, or how to investigate an issue or remotely where to begin to troubleshoot it. Change and evolution is good, but I think there is still a lot to be said about knowing the basics to anything. Levels of abstractions eventually hurt more than it helps.
- icebraining 9y agoHow are these tools any more abstract than make?
- Angostura 9y agoI think that may be hehind some of these tales of 'luddite sysadmins'. Sysadmins need to keep things running and complexity and dependencies, even if they being convenience is something that makes them nervous. It's not about being a luddite, its about being able to hold a mental map of how it all works, so that when it stops working you can dive in.
- kazen44 9y agoThis is very true. Having a mental map of how things work is vital for correct (and good) troubleshooting. Also, a ton of people use abstraction as an excuse to not learn a body of knowledge that contains fundementals (especially on the systems side). In comparison to network engineering for instance, where having (quite) low level knowledge of how protocols work and interact with each other is vital.
- mancerayder 9y agoAnd not to mention getting called at 2 am because something didn't build or the release bombed and having to examine, for the first time, some over-complicated mechanism to build things that goes through some pipeline where you're eyeballing large log files full of long exception chains. Devs see the world as one where velocity and progress is among the most important, while 'sysadmins' (a term no longer used by companies and recruiters, unfortunately) have to worry about keeping the applications actually up so they can be used. DevOps just seemed to have swept the sysadmin under the rug under some pretty words about breaking down barriers. It feels more that devs broke down the wall sometimes. The amount of infrastructure chaos and mess and confusion I see today (as a contractor bouncing around different places) seems higher than traditional infrastructure shops of 10+ years ago.
- mmt 9y ago> It feels more that devs broke down the wall sometimes. That's because only programmers get Peter Principled into the manager roles[1] that decide on whom to hire and how to run "Devops". [1] or become startup founders
- pc86 9y ago> Levels of abstractions eventually hurt more than it helps. This is just not true, otherwise everyone would need to know ASM or be able to easily contract someone who does.
- mmt 9y agoIsn't that reductio ad absurdum, though, epecially considering the original comment is saying that the levels of abstraction eventually hurt more than helping?
- megaman22 9y agoBut I just don't understand why we have to have 47 half-built over-complicated build systems or job runners or whatever the new fad term is for every language, when there's something that does what they all do, is battle-tested, and has been around for decades. Everyone repeat after me. Makefiles are not scary. I can write a shell script. Do I really need to learn grunt/gulp/webpack/npm/rake/fake/maven/gradle/ant and on and on and on? Probably somebody has released another one in the time it's taken me to write this comment.
- kingbirdy 9y agoSystems besides make are used because they offer advantages make doesn't
- Kalium 9y agoFor many of those systems, the biggest advantage is often that tasks are written in the language of the application. A lot of the Rake tasks I've encountered in my career would have been easier to write in bash. Not a majority, but a sizable minority. I suspect that in many cases, the gain was that the authors were more comfortable in Ruby than in bash.
- eropple 9y agoI'm pretty comfortable in both, but I'll pretty regularly use Ruby via Pry for stuff I know I can do in bash. It's easier to write, much much much easier to write correctly, and it presents a unified interface to other developers.
- usrusr 9y agoLanguage specific build tools will usually behave predictably across all development platforms supported by the language. Once you start building on a third party, developer experience will be bounded by the quality of platform support of that third party. You don't want to send everybody off on a hunt for the right version of Python unless you are Python. (Just picking Python as an example because of the recent xkcd. The same is true for everything else, e.g. a Windows computer will rarely contain exactly one make.exe, it's usually either none or a whole bunch of them)
- Tehchops 9y ago> "These tools don't use the thing I like!" Pretty much. I know several admins who appear to be joining a growing pool of luddites who rail against anything new. They're particularly butt-mad about anyone drawing more salary than them. "DevOps" is their favored totem to direct their ire at. I used to try and convince them otherwise, but it turned out to be a completely futile waste of time. At the end of the day, persistent FUD just means a more lucrative job market for the engineers who are pragmatic and fearless enough to give an honest try at making the newer paradigms work for their employers.
- subway 9y agoAlso means fat fat contracting gigs for us luddites to clean up after the move-fast-break-shit-gtfo kids.
- mcguire 9y agoYou know all those people who say, "Never rewrite a project! It'll always fail and take forever and cost too much and..."? I've spend much of the last decade getting paid reasonably well rewriting their projects. (Anyone remember mod_perl 1.x?)
- Tehchops 9y agoHey, if you want to take 18 month stints without healthcare to clean up mis-managed "digital transitions" at places like GE, more power to you ;-)
- ConceptJunkie 9y agoHey, if JCL was good enough for IBM, it's good enough for me.
- gaius 9y agoOld way: we have one tool, it’s got a few quirks but it does most of what we want and then gets out of the way. Noone is impressed by this, tools are supposed to just work aren’t they? New way: we have a dozen tools, they collectively do less than the old one and integrating them is a full time job for someone since any upgrade breaks something. But we all get to put the names of all of these things on our CVs! And that’s what’s important. I wish I was kidding.
- nunez 9y agoSort of Every build system is like Make, but more friendly for their language (IIRC Make was originally for compiling C and C++). Make just so happened to become generic enough to build damn nearly anything and also get bundled into most Linux distros. I think the author is arguing that having to install a shit ton of dependencies to use some other Make-like build system is garbage. That’s true in some cases. But I wouldn’t want to use a Makefile for packaging Node; npm is great for that and understands how Node works.