Earlier quoted context omitted.
What’s the dirs -v, pushd and popd equivalent in PS?
What do those do
Keep a stack of dirs where u can jump very quickly into.
Why I develop on Windows
121–130 of 187 posts
Re: Why I develop on Windows
#122Earlier quoted context omitted.
The default OS-provided shell is irrelevant; anyone who cares an iota about DX on their dev machine is going to set up their terminal and shell from scratch anyway.
Only if you use osx… on linux there is no need to do such a strange thing.
Right, because Linux users are famously content to accept OS defaults and have no interest in tool selection or customizing their setup.
/s
Re: Why I develop on Windows
#123Earlier quoted context omitted.
Interested in copy/paste stuff - mind adding details? I use it very often and works for me. For tabs I don't care much as not using them.
If you do copy on highlight (no need to press ctrl-c or similar) its pretty broken. eg. create a split so you have 2 sessions on the screen, highlight text in split A, then highlight text in split B it doesn't un-highlight the text in split A. There are also times when highlighted text doesn't make it to the copy buffer for whatever reason.
Yeah, I do use "copy on select" since mIRC/Putty days.
Coming back to split - checked, thanks!
For me, who prefers having separate windows, not splitting by means of terminal (splitting in tmux on rare occasions though), it's natural to act those independent on selection, giving me visual hint on what I was working on - I see it more as advantage.
Re: Why I develop on Windows
#124Earlier quoted context omitted.
> > even putting #!/bin/python3 at the head of a script so that it runs through the shell. Uh, not, in that case the shell is not involved at all. The kernel implements shebang and will automatically start the interpreter, whatever it is, without having to go through the shell.
so, a typical noob. Even though he claims he shined in the operating systems course.
This was a rude comment, and I think youre better than this
Re: Why I develop on Windows
#125Earlier quoted context omitted.
I personally disagree on both accounts. Bash is gibberish to me and the year I had to dev python professionally was miserable
I am also miserable when speaking chinese. But I have no dobut that to people who actually speak chinese, it isn't gibberish.
This isn't really an argument against what I said. You can pick and choose your shell language based on preference for syntax. You generally learn a human language because you have to for one reason or another. I think bash has an unintuitive syntax, and I think powershell's is more readable
Re: Why I develop on Windows
#126Earlier quoted context omitted.
It's just a knee-jerk reaction people have in any thread where powershell is mentioned. "Hur hur long command names." Doesn't bring anything to the discussion.
I can see where you're coming from, but to me it's not some meme or joke. I find it similarly annoying in Java, for example, and it makes me want to use that language less. Obviously it's only a small part of the whole consideration.
Every common command has a short alias, or often multiple short alias. Get-ChildItem => "ls", "gci". Get-Content => "gc", "cat". These aliases are standardized, you can look them up with Get-Alias (or "gal" ;) ).
It means that working in the terminal, you can use short commands, and when you write a long-term script, you use the long names so that the script is more readable.
What I find great is that flags also have aliases that are standardized across commands.
This is why I'm annoyed at this meme. It just stems from ignorance.
Re: Why I develop on Windows
#127I'm disappointed that 90% of the discussion is on the first 3 paragraphs of the article. I wrote about C++ and DirectX, too.
Almost nobody works with DirectX outside of game engine developers working on low level parts of the renderer, and there are probably only a few hundred of those worldwide. That's why the new generation (dx12, metal, Vulkan) are so painful to use. No need to make them usable when so few people use them and they want performance and control.
I just think nobody read that far
Re: Why I develop on Windows
#128Earlier quoted context omitted.
> There's a "aux.rs", also a verboten filename in Windows. That's not true. > And then there were some that differed only in case, which honestly I don't know how we manage that, as the non-Windows side is macOS, and yet roughly once per year someone introduces two files, same name, differing case into the repo. Sounds like a crappily maintained repo.
It is true. https://stackoverflow.com/questions/40794287/cannot-write-to... https://www.howtogeek.com/wp-content/uploads/2018/11/img_5be...
Look, I just created a file named "aux.rs" on my Windows machine. It's not true.
Re: Why I develop on Windows
#129Earlier quoted context omitted.
After 3 decades working on Windows, I recently got into Linux and stared learning bash through "The Linux Command Line, 5th ed." book and watching youtube videos. Powershell is so much nicer and a lot more productive to work with compared to bash. Unlike the bash commands that returns strings, Powershell commands return objects. Working in any OOP language and Powershell feels very natural.
Just to corroborate from the opposite direction, I have run exclusively Linux on my personal machines for nearly a decade, and I started a new job where I get to use PowerShell, and it's really amazing, the amount of grep/tail/head (or Get-ChildItem/Select -First/-Last) I have to do is so much less, it feels so much less klunky. Probably the only thing I don't like more so far is Get-Help, because it doesnt put you i…
I thought the PSReadline module had some of that but then it might be a "nearly" compatible experience which can be really jarring when you hit the edge cases.
Re: Why I develop on Windows
#130What a breath of fresh air. A well reasoned post about development on Windows when it seems to be the popular thing on HN just to shit on it [Windows].