6 ms·
From further down in the comment thread, Linus says that speeding this up should help other workloads too, and he's sick of using make replacements: --- +Pete
by josephg 13y ago
From further down in the comment thread, Linus says that speeding this up should help other workloads too, and he's sick of using make replacements:
---
+Peter oh, it's absolutely true that 'make' is a pig, and does too much, and we don't exactly help the situation by using tons of GNU make features and complex variables and various random shell escapes etc etc.
So there's no question that some "makefile compiler" could optimize this all. But quite frankly, I've had my fill of random make replacements. imake, cmake, qmake, they all solve some problem, and they all have their own quirks and idiocies.
So while I'd love for 'make' to be super-efficient, at the same time I'd much rather optimize the kernel to do what make needs really well, and have CPU's that don't take too long either.
Because let's face it, even if the kernel build process was some super-efficient thing, real life isn't that anyway. I guarantee you that the "tons of small scripts etc" that the kernel build does is a real load somewhere totally unrelated. Optimizing page faults will help other loads.
- danudey 13y agoMaybe he'll get so fed up with make that he'll write his own that everyone can just switch to instead of all the crud we have.
- tedks 13y agoOh no. Not on your life. It would be better for the entire world if Linus had a heart attack rather than rewriting Make. Make is already unusable; git-style make would be an abomination. Can you even imagine reading the man pages of all the different git-make commands? The syntax? I hope Linus keeps contributing to humanity and doing what he's doing. He's obviously a great engineer, and if he works hard, he might undo the wrong of releasing git into the world.
- taeric 13y agoHuh? Since the comparison would be to the likes of svn and cvs, git is a hella good improvement. If you are willing to learn what it is that it does, git is actually fairly frigg'n good. Of course, mayhap I've just not used a better tool.
- lytol 13y ago> he might undo the wrong of releasing git into the world I've never seen a comment with which I more vehemently disagree.
- jeffreyrogers 13y agoI can't tell if you're joking or not. The popularity of GitHub and its position as the defacto modern source control management tool demonstrate that very few people hold your point of view. Sure, Git has a lot of options, but what do you need to actually be productive with Git? Probably only a handful of commands: git clone, git pull, git push, git commit, git add, git checkout, git branch, git log. And not too much more than that. At my university Git is used in every single lab based CS course and I don't know of a single person who has had trouble learning to use it.
- scotth 13y agoOne of the main criticisms of git has been its user interface (which to be fair, has improved considerably over time). People often compare it to Mercurial's, unfavourably.
- tedks 13y agoNo, it demonstrates that things that the Linux kernel adopts tend to get adopted. That isn't very surprising. Git being faster than the dVCS's of the time probably helped. Popularity doesn't equate to quality. QWERTY is still the default keyboard layout. I am willing to bet money (let's say 0.1 bitcoins) that there are plenty of people at your university who have trouble with Git. We can haggle on terms, but I'd bet that you'd see 10 people at least struggling with git in an intro course. Once you learn to give it the right incantations, and learn never to deviate from the path you know, any tool can become usable. But it will never be a part of you and will never make you stronger. This has crippled a generation of developers and I'm afraid it will be a massive barrier to entry, stunting humanity's growth probably by 10-20 years. See http://homes.cs.washington.edu/~asampson/blog/git.html http://homes.cs.washington.edu/~asampson/blog/git.html for a more in-depth treatment of Git's insanity.
- XorNot 13y agoQWERTY exists because alternatives were not objectively better. Everytime anyone proposed an alternative, they had to not just be a little better, they had to be so much better that a lifetime of QWERTY muscle-memory being undone was justified. It's the same reason so many new display technologies have failed: its not good enough to be better then an LCD eventually. You need to be better now, and better then the LCD which will come about as evolutionary improvements in manufacturing too. Being a little cheaper in the initial plant cost is meaningless if the plant has been built and we understand its processes. Which of course is why the commentary on Git is absurd: people struggle with Git? People struggled with CVS. People struggle with the notion of "files" and programming in general. The alternative has to both exist, and be easier to use from the get-go. Not just a different set of traps.
- joe_the_user 13y agoHah ha, The parent quote doesn't deserve to be downvoted but it seems to have been massively downvoted for the same reason a massive number of people use GIT who shouldn't - the bandwagon effect. Git may well be a perfect tool for the Linux kernel but it's still an opaque nightmare for the many average non-kernel-developers who use it as "the new good version control system" (which it isn't, it's only a tool for a specific purpose made by a famous person). The poster's point is valid - if Linus created a make replacement for his purposes, the effects of everyone else inappropriately adopting it would be horrific (even if it was indeed, a great make for the kernel and just for the kernel).
- gwern 13y ago> Because let's face it, even if the kernel build process was some super-efficient thing, real life isn't that anyway. I guarantee you that the "tons of small scripts etc" that the kernel build does is a real load somewhere totally unrelated. Optimizing page faults will help other loads. This is true as far as it goes, but a silly argument. Let's apply a reversal test (http://www.nickbostrom.com/ethics/statusquo.pdf http://www.nickbostrom.com/ethics/statusquo.pdf). Suppose the kernel build were as efficient as Chrome's is claimed to be on this page (<5s) and wasn't stressing his system. Would Linus then approve of anyone submitting patches to deliberately slow down the Linux kernel build just to show up slownesses in page fault and encourage kernel devs to spend time on optimizing that? No, of course not! That would be idiocy and the person submitting the patches would probably be banned by Linus in his titanic rage. However, since the slow build & page faults is the status quo, Linus is making lemonade of it...
- sp332 13y agoNot sure why, but your URL has a bunch of junk on the end of it. I don't get what you're arguing against. Even if the kernel were superfast, there's probably another "real load" out there somewhere that legitimately runs into lots of page faults.
- loup-vaillant 13y agoIt's a question of what should be addressed first. Linus is actively arguing against a faster kernel build. It sounds like it makes sense, because it gives him leverage with CPU vendors. But it doesn't, really. If kernel build were already fast, he would never in a million years slow it down just to get that leverage. Now maybe he's perfectly aware of this status quo bias, and he's taking advantage of it to meliorate something he would otherwise have no power over. Sneaky. Still, what's the priority? He's made his point now, hasn't he? He could work on making a faster build process, now.
- Dylan16807 13y agoSlowing it down wouldn't give him the same leverage that it has as a real use case. Anyway he's not saying slowness is better in and of itself, just that there are better places to work on than replacing make.