Hacker News new | ask | show | jobs
by qayxc 2284 days ago
> I’m pretty sure the terminal app was advertised as the next generation console experience for Windows, which means it is going to replace cmd, and will be used by non-power users.

I'd love to hear a legit day-to-day use case, though. I'm honestly very curious to hear about that since even as a developer, I pretty much never use the command line (outside of WSL, which I don't consider a typical use-case either).

3 comments

I work outside of software (or any technology really), so I deal with around 30 people who are the opposite of power users, all using Windows (with one on a Mac laptop). Not a single one of them would even know what a terminal is, and I include powershell and the standard command line in that. The only thing that runs on their machines via Windows cmd are scripts I install so I can use their machines if I have to get something done on it.
I bump terminal stuff on random non IT useres and my exprience is the opposite.
How do you as a developer never use a shell? I'm genuinely curious. How do you compile, install dependencies, etc?
I didn't say I never use a shell - I even explicitly excluded WSL.

When developing software in Windows, however, there's simply no need.

> How do you compile

I press F6 in my IDE.

> install dependencies

I click "Add nu-get package"

> etc. [I assume version control operations and the like]

Again, I simply use the built-in tools of my IDE of choice which are usually bound to hotkeys.

This is hard to fathom, especially for modern web development, but I don't do web development and the embedded systems I work with don't have a shell while the GUI programs have, well, graphical interfaces :)

> When developing software in Windows, however, there's simply no need.

This tells more about your skils then anything else. If there is NO NEED for that in your world, there is defintelly a NEED for you to dive into it - something you don't know you can't use or find a need for it.

Integrated development environments, or IDEs for short.
Its double work. You mandatory need CLI for build server anyway, and you generally DONT need IDE for anything
I use the shell everyday for git, code search, running my code, SSH. I think on windows it's more common to use an IDE with a GUI for some of these things, but the CLI is generally more powerful.
I was rather curious about strictly non-power-user use cases. Someone who develops software and uses distributed version control systems isn't exactly the average user.

Especially on Windows.

I think you are babysitting users too much.

Terminal is basic IT literacy. Or at least, it should be. And it can't be if you protect people from it like its some kind of baba yaga.