Reimagining the Windows Command Line
tltjr.github.com
tltjr.github.com
His target price for the released product is hopefully $10 ( a good deal )
The $20 pledge gets you 2 licenses Cost Per License: $10 Additional Perk: Nothing
The $50 pledge gets you 1 license Cost Per License: $50 Additional Perk: Beta Access
The $100 pledge gets you 5 licenses Cost Per License: $20 Additional Perk: Immediate Access
And that's just a small analysis of those 3 price points. The higher points also seem a little off to me as well. It just seems odd to have the Cost Per License to vary so wildly, in my unsolicited opinion, anyways.
I understand trying to play to the draw of people wanting quicker access to use the tool, but his pricing model creates tiers that are counter-intuitive to people who want to contribute, but do not want to receive what could be perceived as a poor value for the cash they have available to contribute.
http://sourceforge.net/projects/console
I've been using it for a while, and it works pretty well.
From the project page: "Console is a Windows console window enhancement. Console features include: multiple tabs, text editor-like text selection, different background types, alpha and color-key transparency, configurable font, different window styles."
http://code.google.com/p/conemu-maximus5/
ConEmu starts a console program in a hidden console window, and provides an alternative customizable GUI window with various features:
I hope it didn't come across as negative, it was just something I noticed and wondered if other people saw the same thing, or if I was just being nitpicky.
I hope your project reaches funding, this looks like a really cool idea
If you suggested you would dive into the WinAPI and use your C++ skills to write a new console _engine_ I would gladly pledge 50 bucks or more.
I'm afraid many people will pledge thinking this will bring a usable console emulator to Windows, instead of just another Console2 like hack around the severely limited windows api.
I think 5 years of .Net experience won't cut it for that ..
Might I suggest you compiled x64, too? x64 seems to be more commonly sold over x86 these days -- at least in the US.
I've started learning Symfony2, and the default is to get it up and running using the dependancy manager composer, a commandline based tool. I've spent a week trying to finish the simple task of installing the framework. No success. Now, I don't make a living programming, so I'm definitely at the shallow end of the programming pool. But still. A week.
There are several problems as I see it:
- No discoverability. You are given no clues whatsoever as to what commands are available to you. You have to know exactly what you want to do. Yes, you can read manpages, forum posts, etc. but finding, learning and memorising a whole set of commands used in some program you might never use again seems like a terrible waste of productive time. Without the manual you're flying blind.
- All sorts of opaque dependencies. Composer for instance apparently requires git installed for it to work. But it doesn't say that anywhere. You also need to define paths, etc. which isn't covered anywhere.
- A million minor flaws and bugs. Until now I've run up against at least a few bugs, either in composer or in some other part of the chain of software. Only opaque general warnings are given, and finding out exactly what is wrong is next to impossible.
- Terrible UI. Copying and pasting doesn't follow convention, copying from a commandline to a notepad inserts linebreaks that you have to clean up manually, there's no way to maximise the cmd.exe window. The list of basic usability flaws goes on.
This isn't meant as trolling or ranting, although I must say I'm genuinely alienated by the commandline. I understand that text is great way for programs to talk to each other, I understand that the commandline is a great way to talk to a remote server, and I understand the power that piping, etc. gives you, so it's not like I'm denouncing the power that's inherent in the tool.
The problem is that the learning curve is tremendously steep, and I just don't feel it's worth it. To do the simplest thing I need to learn how a whole ecosystem works. I also have to page the information I need together from a number of different sources that I first have to find. It's kind of like having to build a car just to ride down to the baker to get some bread. It's quicker to walk than assemble a car before you can drive.
You've asked the question and answered it yourself ;-)
Using a GUI over the CLI is probably preferred for 90% of the tasks 95% of the users typically perform. I don't agree with all the drawbacks you listed, but I can see where they are coming from. The CLI is simply not so great for typical computer users.
That said, a good CLI is absolutely invaluable for power users, system adminstrators, developers, etc. There's only so much you can conveniently do through a GUI, as soon as you need to compose multiple complex actions into a script or perform advanced data extraction, search operations, automate tasks, etc. there really is no alternative for a good CLI.
The funny thing about a powerful CLI is that it isn't very accessible unless you invest quite a bit of time mastering it, but once you do, you'll find out that you can do many (most?) things more efficiently by typing up commands and composing them into scripts. Once you get proficient using the CLI, you'll find yourself using the CLI for all kinds of things you used to do through a GUI before. For example selecting and copying around files or extracting archives, personally I think CLI tools (in my case unix CLI tools) to be much more flexible and convenient than something like WinZip.
But just like most people will never use their computer to write scripts or computer programs, they will also never invest time in learning the CLI. And usually they don't really need to anyway, just like most people don't need (or want) to learn how to change the oil on their car themselves, no matter how easy it is if you know how to do it. It's not something they enjoy learning about, but that doesn't mean changing oil is useless or difficult.
The lack of a proper CLI in Windows 9x and XP has always bothered me a great deal, as a developer and power user. It was one of the main reasons to switch to Linux and later OS X. Apparently these days Windows has a pretty good CLI with PowerShell, but the Windows train has already departed a long time ago for me. But it's still a good thing Microsoft finally decided they had to provide power tools like a CLI, it's one reason less blocking me from every going back to Windows (a lot of others still remain though ;-)
The problem is that people like me, who are somewhat technically inclined but not fulltime programmers, fall in between two chairs. I need to do some reasonably advanced stuff, but I face a steep learning curve before I can do it, and I'm not sure it's worth it since it's not my main occupation.
I think many people often discard technologies for their implementation rather than their ideas.
For example, there's absolutely no reason why command line tool options can't be discoverable in the same way object methods in Java/C#-ish IDEs are.
- Discoverability: tab completion, apropos manpages, listing out your search path directories, using your Debian GNU/Linux distribution's package management tools to search / explain packages and commands.
- Dependencies: Debian GNU/Linux, APT, and policy. There's a reason I'm an unrepentant bigot. Debian-based distros are a fair substitute. RPM remains a pale shadow, largely for lack of policy. Proprietary operating systems have fundamental conflicts of interest which preclude an effective solution.
- Bugs: Addressed in policy and via an active user and developer community, with low barriers to communication and interaction between them. Again, Debian GNU/Linux nails this. No, it's not bug-free, but you'll find very, very few showstoppers in stable releases.
- UI: If you're not using pipes, command expansion, xargs, etc., you're mostly doing it wrong. Pasting into vim allows you to sort your linebreaks via regex replacement or any of numerous other means.
How old are you, kid?
proper command line shells and tools offer auto-completion and inline help.
> - All sorts of opaque dependencies.
Bad or unfinished products is a concept orthogonal with command line. I've had to manually install a particular unspecified version of .NET to get some graphical application to work, for instance.
> - A million minor flaws and bugs.
Again, totally unrelated to CLI. Most applications are barely usable, for instance almost all of professional in-house applications at most companies are abysmal, though graphical.
> - Terrible UI.
Probably a unix program; you shouldn't use Notepad, it doesn't understand any other line end convention than <CR><LF>. Notepad is mostly useless, and there are many valid replacements.
This is not discoverability. How will it help me figure out curl's command line options? How will it help me not having to remember whether tool X wants "command [files] [options]" or "command [options] [files]" or either? How will it help me reuse something i just ls'ed into vision without having to retype half the path i just typed into that ls command?
Try typing "curl", the output (on Ubuntu 12.10) is: "curl: try 'curl --help' or 'curl --manual' for more information"
>How will it help me not having to remember whether tool X wants "command [files] [options]" or "command [options] [files]" or either?
Both are almost always excepted, but command [options] [files] is standard. Also, if you do something wrong, you are often given an explanation as to what you did. Also `command -h` or `man command`.
>How will it help me reuse something i just ls'ed into vision without having to retype half the path i just typed into that ls command?
Up arrow.
I feel like this is a Git conversation from several months ago all over again. The CLI is not magic. You have to invest in learning how to use it. Next we're going to hear about how Java/C#/PHP isn't intuitive or discoverable enough.
For me, at least, the dependency issue has been resolved with automatic build systems like MacPorts. It's been a while since I had to manually seek out the dependencies for a command line program by hand.
Discoverability is very much an issue. I tried to figure out how to get ffmpeg to do something last night, and it took me hours. I find Google to be far more indispensable when using the command line than the man pages.
Despite all these issues, I still find the command line invaluable. :)
I think the way most people learn these things is to have someone who knows what they're doing sit down next to them for an hour or so and explain how everything works. I suggest finding someone like that -- flailing around with google is orders of magnitude slower.
I started really investing in cygwin last year and I'm constantly moving more and more of my work into it. All my coworkers have a tedious build process that involves lots of clicking around windows explorer while mine is a two character sequence that has some other value-add factored in.
In addition to these benefits, shell tools take much less memory than gui ones, and I really notice the difference running mysql & psql on the command line vs firing up pgAdmin or MySQL workbench.
Besides you can never learn everything all at once, but you slowly pick things up over time as you need them. Then, one day, you wake up and the command line feels like home. My advice, don't try to learn any of it until you have a specific need of doing something, only then will you really retain anything you gleam from it. And don't try to use/learn it on windows.
moving around a filesystem for instance, in a GUI based tool I click on a folder and view it's contents. In a commandline tool I type an often long path, hit enter and view a list of files and/or folders in that particular folder. If I want to move up or down I issue another command that I have to type. I don't get any visual cues as to where I am in the structure either.
I fail to see how typing 20 letters and hitting enter is easier than one click with a mouse. In respect to histoory I think that what happened was that normal users moved on to a more intuitive and faster interface for normal things.
Instead of 20 letters, just type the first couple, tab complete (z-shell makes this fluid) and hit enter. If some directories have a single sub directory, it's just tab-tab-tab and you're at the base.
To get a "visual cue", type pwd or have a setting for your shell that follows your directory path.
You can also set up aliases or shell variables for common paths. This has the benefit of not being cluttered (like shortcuts on a desktop) while allowing you to "cd essays" instead of "cd documents/writing/essays".
Also, there's the benefit of find/grep. If you can't remember where a file is, but you know generally where it is, cd there, find "part-you-remember" or grep -R "some unique text" and you'll get your answer soon enough. This has the benefit over full desktop search in that you get local results, so you may have to only sift through 3 or 4 "README" files instead of dozens.
Sometimes I use a graphical file browser, but mostly for images. For that, I use nautilus. But I can open nautilus from my current directory. For example, to get to my code, I can just "cd project-name; nautilus ." (having set up a variable) instead of trying to navigate there from /.
I'm not saying GUI tools are bad; I'm saying that for many tasks, the command-line is more efficient, but a GUI tool is just a command away.
I can think of several GUI apps that have ALL of those problems but I also can't script them, alias them or fix them.
I spent 75% of my day in the terminal because I'm proficient and fast with it. Most of programming has a learning curve, I don't see why people expect otherwise when it comes to an interface that is every bit as powerful as a GUI but with a specific interface.
No offense but with the number of misconceptions in that post, maybe you need to spend more time with it before dismissing it out of hand. (edit) seriously, you don't know about Notepad.exe and line breaks. :/ Man... if you would spend a bit of time on tooling and learning your environment you probably wouldn't be spending half the time you are doing whatever it is you're doing. Jumping into something is fun, but for sufficiently complex things, you DO have to step back and read the manual.
Knowing what Symphony does, I'm quite sure that learning the CLI tool would be a far better use of everyone's effort than a GUI tool. This is even a place where I think the CLI tool makes exceedingly more sense to use.
edit: To be fair, if I had to use Windows default tools and a PHP generator tool all day long, my words would probably be more angry than yours.
First, I'm certainly not dismissing it. Yes, I'm frustrated, but I'm also aware that a lot of people much smarter than me swear by this tool, so there's obviously a lot of value there. I'm more dismayed by the learning curve. I come from a sales/marketing/ux/business kind of background so my mindset is different. I like my tools to be beautiful and intuitive. As simple as possible but no simpler as Einstein famously said.
The problem, as I see it, is that the commandline is like a marathon you have to run before you reap any rewards. Learning the commandline involves a whole sleuth of different things. Finding the right tools (I can infer from your post I obviously don't have those :-)), learning how filesystems work, unixy commands, git, cygwin, the list goes on. Seen from my perspective (and this might well be wrong) you basically have to have a good grasp of a whole boatload of ideas, technologies and concepts before a commandline tool is of any use to you. There's no easy way to learn a bit at a time. It's an either/or kind of deal.
I don't see any easy solutions to this, but I think it's a problem.
I slowly accumulate knowledge of how to use other programs as I needed to use them (the same way I learn how to use gui programs.) The only conceptual block for me with the command-line was the concept of piping the output of one command into another.
Computers are complicated. Most users have no idea how hard. You HAVE to be willing to learn. I honestly have no idea what you expect and I don't think you do either. I don't honestly think there's anything to do.
As much as I recommend that a serious power user learn and use a solid shell (bash or zsh, as my earlier comment suggests), several nines worth of users probably never will do so. Many could, though it's still probably somewhere between 10-25% of all users who would really have the aptitude to do so. And I do feel that the time invested in learning good tools on a well engineered platform pays of in spades.
That said: general-purpose computers are hard to use, very complex, and far more users know how to use them in some small way but really have little or no deep understanding of what they're doing or why. It's something that the tablet/handheld market's addressing, though I fear that the inclination to turn these into pure consumption devices will ultimately torpedo this goal.
* viM instead of Visual Studio has made me a better programmer * think more, guess less * I can keep customizations when I remote in and patch production code * Bash is much more productive than .bat files * Piping is amazing (cat file | sed | awk | ...) * Tons of documentation online
If Windows had a decent command-line (with decent documentation of course), I might convince myself to put up with less malleable tools just to play games without rebooting.
Don't get me wrong, Windows is fine, but it's not Unix. A better command-line app can't change that.
Isn't the point of a commandline that it makes basic tools far more malleable? For example, I recently was working with an OCR tool that took as an input 1 image file path, and an output name, and extracted plaintext from the image.
If this were a gui tool, I would be stuck manually running it on hundreds of images at once. As a command-ling tool, I can do: `find . | grep *.jpg | xargs -n 1 -I{} | tesseract '{}' '{}'`
Although it seems it is not working well on Windows 8 x64, I am having a good experience on Windows 7 x64.
A couple of suggestions:
- Wish takes a while to become responsive after starting the program (3-4 seconds for me). I am not sure if this is just me, I just wanted to make you aware!
- Add a keystroke for clearing the terminal. I am addicted to Ctrl + L in bash.
- Perhaps consider adding select to copy.
Keep up the good work, and I'll keep an eye on this project :).
* Make shortcuts for tab splits in both vertical and horizontal
* Tab titles are not so necessary, right? Just draw a line between vertically or horizontally split Windows, like iTerm2 does (it is really neat).
* Word-wraps?
* I was in c:\demo, I wrote a nonexisting command (let's say lls), now I'm in c:\program files\wish.
* On a prompt, I can use Backspace to delete PS1-like string, and after deleting something and pressing return, it crashes
* Add it to PATH so that people can run it via Run window (Windows+R).
* "set" command runs without params in cmd.exe, http://technet.microsoft.com/en-us/library/bb490890.aspx this doc might help.
I have recently joined Microsoft and I was using Linux-OSX before that for work and I miss zsh+iterm2 quite a lot.
One reason I switched to Mac for Web dev is the tightly integrated unix command line. I love it, but I don't think Apple does. I don't think the integrated unix CLI is any emblem of enlightenment on Apple's part; it's a historical accident. A company that believes that even granting users a "files and folders" view is giving them too much power (iOS) is no stalwart defender of the command line interface. As we make the Windows -> Metro, Mac -> iOS shift, the time may come when any command line access to a commercial OS is part of a "developer tools" package available only to "registered" developers who have "signed zee papers."
I've only used Linux servers for years. I wonder if I'll end up a few short years from now with some sort of hackers' Android laptop, built with Apple-quality hardware/software integration by somebody like Samsung for the niche of people who want real computers instead of media purchasing appliances.
http://en.wikipedia.org/wiki/Windows_PowerShell
And Powershell ISE is like bash with Intellisense.
You can access .Net from Powershell and pretty much do anything you want. You can easily write new commands in C#.
Everything you want is already there. You just have to step slightly out of the Unix mindset to find the Windows equivalent. And I'd have to say that the powershell idea of passing objects around instead of text is exceptionally useful.
ls C:\ | foreach{echo $_.Name}
ls C:\ | foreach{echo $_.CreationTime}
ls C:\ | foreach{echo $_.CreationTime.DayOfWeek}
ls C:\ | foreach{echo $_}
I played with it for a bit and one thing I noticed was that the "Home" key took me to the beginning of the line/prompt instead of the start of my input. Also if I backspace far enough it will start to kill my prompt.
One thing that would make this awesome for me is emacs keybindings.
Overall though, I think this has nice potential to be a super useful tool. Thanks for sharing!
Also, cli in wpf ?! Come on....
Sounds all too familiar :-).
I don't have a windowsbox available right now, but demo looks great.
See, your 'dead OS' is not walking - it is marching bravely here and there and all over the planet, led by army of Windows admins. Who, being just as smart as their other-OS-admin-brothers, are always looking for better tools to do their job.
Not that I think linux is going anywhere :)