4 ms·
In a linked article about why the "command-line" is "bullshittery" in the first place he compares Python to Excel and declares Excel superior because it can mak
by lucb1e 12y ago
In a linked article about why the "command-line" is "bullshittery" in the first place he compares Python to Excel and declares Excel superior because it can make graphs much more easily. His students apparently ask why use Python when you can use Excel.
First off, Python is not a command line. Secondly, what the fuck does he think Excel's source code is written in? MS Publisher? They're just different things.
The author does not seem to understand why command line tools still work the way they worked in the sixties (as he loves to point out), which is because it just works. He mentions git, the version management system that uses the command line mostly, but forgets to mention that although git could surely have (and has) a GUI, it would disable you from doing many things. I often pipe git output to other tools, something you just cannot do with a GUI.
Oh, and he uses nano for command line text editing. I suppose that also explains a thing or two when working with Vim or Emacs is so much better than any other text editor.
- Kalium 12y agoIn fact, git has multiple GUIs. Often a user will use multiple in their git workflow, because git is too complex to fit neatly into one UI.
- aet 12y agoIs it possible to make Git as easy as Dropbox?
- cheald 12y agoSure, just remove everything except the "commit", "push", and "pull" commands. But it sure gets a whole lot less useful then.
- jackmaney 12y agoNo, because Dropbox does not support branching and merging.
- Kalium 12y agoYes, provided you're willing to give up all the complex ideas that make git more useful than Dropbox for some things.
- aet 12y agoI imagining a scenario in which I have a team and I have 10% git experts, 90% not -- can I create a system in which they are basically "drop boxing" and the merging etc gets handled automatically or decisioned by an expert? -- Maybe ultimately everyone should just learn git since it isn't that complicated.
- Kalium 12y agoI've been in such a scenario. Making it simple and drool-proof for some people while everyone else works around the consequences of that is not as lovely as it sounds. It winds up being much, much easier to just teach whoever else enough of the basics to use git. It's almost certainly less difficult to use than whatever ERP the company uses.
- loup-vaillant 12y agoProbably: http://tonsky.me/blog/reinventing-git-interface/ http://tonsky.me/blog/reinventing-git-interface/ (And no, you don't have to give up any power).
- Dewie 12y ago> Python to Excel and declares Excel superior because it can make graphs much more easily. I don't really think he meant to say that. I think he is using a writing style which emphasizes with different view points, namely seasoned programmers and their befuddlement with normal user's inefficient tools, and the normal users' befuddlement with the seasoned programmers seemingly arcane tools that seemingly accomplish the same things that their prettier, more easy to use tools already do.
- loup-vaillant 12y ago> [he] declares Excel superior because it can make graphs much more easily. You should read more carefully. He claimed no such thing. His real claim was that users tend to react like that. And we programmers must be prepared for such backlash. > The author does not seem to understand why command line tools still work the way they worked in the sixties The author is saying the users don't understand. He knows about their goodness. The problem is to teach it. > He mentions git, the version management system that uses the command line mostly, but forgets to mention that although git could surely have (and has) a GUI, it would disable you from doing many things. Not necessarily: http://tonsky.me/blog/reinventing-git-interface/ http://tonsky.me/blog/reinventing-git-interface/ > I often pipe git output to other tools, something you just cannot do with a GUI. A nice GUI could, among other things, record what you just did and translate it into the command line equivalent. But more importantly, when you have a GUI, the command line no longer have to act as an interactive user interface. It can now be dedicated to what it does best: API. Removing the command like would bring the apocalypse (as it mostly did on Windows), but merely adding a GUI can make things much better. > Oh, and he uses nano for command line text editing. I suppose that also explains a thing or two when working with Vim or Emacs is so much better than any other text editor. He knows about the Vim/Emacs holy flame wars, so he most likely used one or the other. But go teach either of them to the hapless student. The Emacs tutorial alone takes several dozens minutes to get through. Extremely useful, but quite steep. Nano on the other hand can be taught in seconds. So it is more likely the first text editor the students will see. If you want them to write Python code and you only have an hour before they leave, you have little choice.