Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I develop on Windows

blog.shortround.dev

Post reply on HN
Print view View original

111–120 of 187 posts

Re: Why I develop on Windows

#111

Post by kaba0 »

lucb1e wrote: post #75
justeleblanc wrote: post #33

Earlier 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.

What’s long in Java? It sure longer than the absolutely insane C convention of snrcph whatever, but these AbstractFactoryFactory things are just memes - the Java convention is to prefer full words, but that’s the same in I believe the majority of languages - JS, Rust, Python all use basically identical names, at most casing differs.

Re: Why I develop on Windows

#112

Post by kaba0 »

c7DJTLrn wrote: post #80
lucb1e wrote: post #13

Earlier quoted context omitted.

To be fair to OP, I would then go on to label these people as equally ignorant: > A lot of people coming from the Unix-like world of macOS and Linux don't tend to know [PS]. Many people don't know it even exists at all. When I mention the Windows Terminal to people, they think I'm talking about the Windows Command Prompt, a crappy little program I know that PS and the new terminal is not the same as cmd.exe, and that…

>A lot of people coming from the Unix-like world of macOS and Linux don't tend to know [PS] We all have different experiences of life but I have never found this to be the case. Linux users are savvy and curious about things even outside their bubble. The only people I can imagine this being true for is the true greybeards who have been daily driving Linux for 20 years.

Well, you also have an insane amount of linux users who hate on systemd/wayland/gnome non-stop with complete ignorance. Though they are more of a vocal minority given that they are the defaults on most distros.

Re: Why I develop on Windows

#113

Post by kaba0 »

smoldesu wrote: post #26
lucb1e wrote: post #13

Earlier quoted context omitted.

To be fair to OP, I would then go on to label these people as equally ignorant: > A lot of people coming from the Unix-like world of macOS and Linux don't tend to know [PS]. Many people don't know it even exists at all. When I mention the Windows Terminal to people, they think I'm talking about the Windows Command Prompt, a crappy little program I know that PS and the new terminal is not the same as cmd.exe, and that…

Yeah. Reading the 3-pipe solution in bash versus 4-pipe solution in Powershell felt like it was verging on parody. Yes, these object-oriented features are nice - but they're something of a self-imposed problem on an OS that's designed like a database. Even the tools we use to parse JSON in bash aren't all that bad, if you can keep yourself grounded in the world of text processing. I'm glad that the OP has a workflow…

Nah, passing text around is not a good thing, you can’t even write a properly maintainable script that queries the temperature of your hardware or whatever property you are interested in, these will be one-off hacks, breaking even from a change in locale.

Re: Why I develop on Windows

#114

Post by bombolo »

hparadiz wrote: post #36
AaronFriel wrote: post #21

I've followed a different path, but I've come to the same conclusion. Along my path, picking up languages like Haskell or Node early on meant using Linux. So since high school I've always had _a_ Linux machine available, but preferred to use Windows as the user interface. Two thing I can say for any naysayers who use a Mac and do devops, backend development etc.: 1. Are you sure your environment that matches your dep…

Your shell scripts on Linux don't even work the same way as the docker image based on ubuntu. Resolving those issues is just part of the job. I recently had this issue where my version of SSH was too new compared to that the servers were running and I was getting issues about the cryptographic algorithm being mismatched.

> I recently had this issue where my version of SSH was too new compared to that the servers were running and I was getting issues about the cryptographic algorithm being mismatched.

I think that when your encryption algorithm gets removed, after having been deprecated, is really time to upgrade instead of commenting on ycombinator.

Re: Why I develop on Windows

#115

Post by tomjen3 »

sys_64738 wrote: post #90

Microsoft has made Linux development cool again after got derailed by macOS. Nowadays you can use almost all Linux tools on Windows. They also provide Windows Terminal which is rather excellent.

Microsoft made win dev tolerable by including Linux.

To properly work with git I installed gitbash -- that is essentially Linux in a box, complete with git, ssh and the basic bash tools like cat.

To do more complicated things, you can install WSL, which is literally a virtual machine running Linux, well integrated with the Windows system.

The problem of course is that well-integrated is not the same as native, but MS does have some of the best languages available, C# is pretty great.

Re: Why I develop on Windows

#116

Post by bombolo »

deathanatos wrote: post #12
Swalden123 wrote: post #8

Regarding NodeJS and being cross platform, why didn’t the company just use path.join?

Because developers are lazy. I've given up the fight that is "use the language's features for path manipulation" in code review at this point. People just wanna string concat.

In python if you use a Path class for the left hand item you can do `a / "b"` and it is cross platform.

Re: Why I develop on Windows

#117

Post by bombolo »

shortrounddev wrote: post #65
0x445442 wrote: post #61

Powershell, an inferior shell to Bash and an inferior scripting language to Python. But probably quite useful for administering corporate windows instances.

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.

Re: Why I develop on Windows

#118

Post by nikau »

CoolCold wrote: post #103
nikau wrote: post #98

Earlier quoted context omitted.

> Windows Terminal which is rather excellent. I'd go more with buggy but functional once you know its limitations. Copy and paste is broken, tab naming and management is broken, its still pretty rough around the edges.

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.

Re: Why I develop on Windows

#119

Post by revelio »

shortrounddev wrote: post #81

I'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.

Re: Why I develop on Windows

#120

Post by minimaul »

AaronFriel wrote: post #21

I've followed a different path, but I've come to the same conclusion. Along my path, picking up languages like Haskell or Node early on meant using Linux. So since high school I've always had _a_ Linux machine available, but preferred to use Windows as the user interface. Two thing I can say for any naysayers who use a Mac and do devops, backend development etc.: 1. Are you sure your environment that matches your dep…

> 1. Are you sure your environment that matches your deployment environment? Do you have confidence your server code runs the same on an Apple Silicon Mac as the (very likely) x86-64 and Linux environment your users use?

I’d argue that a lot of us are developing SaaS etc and the browser is our main touch point, so this isn’t necessarily as relevant.

Post reply on HN