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

161–170 of 187 posts

Re: Why I develop on Windows

#161

Post by hparadiz »

bombolo wrote: post #114
hparadiz wrote: post #36

Earlier quoted context omitted.

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.

Tell my old job not me lol

Re: Why I develop on Windows

#162

Post by bombolo »

shortrounddev wrote: post #158
bombolo wrote: post #146

Earlier quoted context omitted.

If languages were intuitive, it wouldn't take years to learn them.

Okay? Are we still talking about preferred shells or are we talking about chinese

We're talking about how your argument made no sense, for any kind of language that exists.

Re: Why I develop on Windows

#163

Post by bombolo »

shortrounddev wrote: post #154
bombolo wrote: post #152

Earlier quoted context omitted.

so they didn't learn about fork/exec in that course? I don't believe it wasn't mentioned :)

OS class is not about Linux, its about OS theory. You learn the algorithms for priority queues and preempting tasks and even build a simple OS (depending on the class). Very little of it is about how IRL operating systems/kernels like NT or Linux work, though they did use some examples to demonstrate. Forking was more in Systems programming class, but that class was more about C, system calls, linking, and gdb. Not m…

"forking" has absolutely nothing to do with "the syntax of shell scripts".

Proving my point more and more here…

Re: Why I develop on Windows

#164

Post by cryptonector »

bombolo wrote: post #152
cryptonector wrote: post #144

Earlier quoted context omitted.

My son shined in that course, but I'd be surprised if he knew this particular bit of trivia.

so they didn't learn about fork/exec in that course? I don't believe it wasn't mentioned :)

That particular bit of trivia wasn't covered. Why should it have been?

Re: Why I develop on Windows

#165

Post by tpoacher »

No hate to OP, but almost every single argument in the article regarding Powershell boils down to them not knowing a thing about bash. I know this is the case, despite the claim in the article that they do, because it's clear from the text.

I also felt bash was cryptic before I decided to actually learn it. Now it's one of my favourite languages. All it took was reading "man bash", which is actually super clear and surprisingly enjoyable to read for a manpage.

As I was reading this article, initially I felt like I wanted to "rebut" the claims, but by the time I finished reading, I realised I would basically end up having to rebut the whole thing. (and doing so on a phone is simply not worth it).

Honestly, learn bash. It's actually beautiful. By all means, use PS too; but judging from your article, you're missing out on a lot of great stuff.

Re: Why I develop on Windows

#166

Post by subjectsigma »

shortrounddev wrote: post #159
subjectsigma wrote: post #133

I have no idea what the point of this article is. It just seemed like rambling. Are you trying to get us to switch to Windows? To shame macOS into a better dev experience? To justify your own decisions to yourself?

I wrote it after reading several articles on Microsoft's docs page which are all stories of developers moving from Mac to Windows. All of those stories boiled down to: "WSL makes it easier to have the same development workflow on the PC as on a mac". I felt this was short-changing a lot of the other features of windows that I like and wanted to point those out and make the point that windows is, I believe, a good dev…

See, now that makes a lot more sense. As someone who owns a Mac for personal projects and uses Linux+Windows at work, the article felt like a random collection of facts. I think with that upfront information and a little structure it could be an interesting read.

Re: Why I develop on Windows

#167

Post by shortrounddev »

bombolo wrote: post #163
shortrounddev wrote: post #154

Earlier quoted context omitted.

OS class is not about Linux, its about OS theory. You learn the algorithms for priority queues and preempting tasks and even build a simple OS (depending on the class). Very little of it is about how IRL operating systems/kernels like NT or Linux work, though they did use some examples to demonstrate. Forking was more in Systems programming class, but that class was more about C, system calls, linking, and gdb. Not m…

"forking" has absolutely nothing to do with "the syntax of shell scripts". Proving my point more and more here…

Again, try to remain polite. I understand how forking works. Knowing how shebangs work is not something they teach directly. Forking is.

Re: Why I develop on Windows

#168

Post by ygra »

justeleblanc wrote: post #128
overthrow wrote: post #35

Earlier quoted context omitted.

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.

I think they have changed it so that you can by now create files with forbidden names and an extension. But that's a somewhat recent change.

Also you could always create such names with the right APIs, so one application could create such files, but another can't delete them or open them.

Re: Why I develop on Windows

#169

Post by deafpolygon »

cyberbanjo wrote: post #150
deafpolygon wrote: post #131

Earlier quoted context omitted.

ForEach-Object and ForEach are the same thing. Get-Help ForEach-Object ... ALIASES foreach %

I have seen that, and that's partially why it seemed so confusing to me but at least one difference is The ForEach-Object cmdlet works much like the Foreach statement, except that you can't pipe input to a Foreach statement. For more information about the Foreach statement, see about_Foreach. https://learn.microsoft.com/en-us/powershell/module/microsof... And another appears to be performance PS /home/me> $time = (Me…

Hey TIL, though, I knew there was a difference (the foreach statement is meant to be typed all lower-cased, since it is not a cmdlet but really a shell built-in but PowerShell is case-insensitive). Get-Help gets you information on cmdlets, not shell built-ins.

Though I was referring to the cmdlet, you're absolutely correct.

Re: Why I develop on Windows

#170

Post by bombolo »

shortrounddev wrote: post #167
bombolo wrote: post #163

Earlier quoted context omitted.

"forking" has absolutely nothing to do with "the syntax of shell scripts". Proving my point more and more here…

Again, try to remain polite. I understand how forking works. Knowing how shebangs work is not something they teach directly. Forking is.

so you know about fork but not about exec. It's not impolite to point out you didn't know something.

It's impolite to get offended.

Post reply on HN