You install git and you get git bash that works great in the Windows terminal. That's something you do once. I use the terminal daily, not an issue at all.

[–] r1veRRR@feddit.org 6 points 22 hours ago (1 children)

Cool, and then there's NEVER any problems with different paths? With back and forward slashes? With the limit on path length? With missing permissions on the file system requiring weird workarounds?

Most importantly, your server is likely not Windows, yet you test on Windows, and that's never ever been a serious source of issues?

And don't say WSL. That's like saying the fix to using Windows is to use Linux, but fiddlier. Not to mention you still get issues with the mounted file system.

[–] blackn1ght@feddit.uk 1 points 22 hours ago

Cool, and then there’s NEVER any problems with different paths? With back and forward slashes? With the limit on path length? With missing permissions on the file system requiring weird workarounds?

Nope. The language we use handles that for us. I don't think path length has been an issue for a while now?

Most importantly, your server is likely not Windows, yet you test on Windows, and that’s never ever been a serious source of issues?

We use serverless functions using Linux and it's never an issue. My previous employer, we had Windows servers and Linux based containers, and that wasn't an issue either.

[–] RagingRobot@lemmy.world 3 points 1 day ago (1 children)

I never had to do anything on my Mac it just works every time

[–] ChairmanMeow@programming.dev 1 points 1 day ago (1 children)

Enterprise Windows does not get all those ads. I haven't seen a single ad on any of my Windows machines.

[–] RagingRobot@lemmy.world 1 points 20 hours ago (1 children)

Apples doesn't sell a Mac version with ads and a version without so that seems better to me too. Why do I have to pay extra for that?

[–] W98BSoD@lemmy.dbzer0.com 1 points 16 hours ago* (last edited 16 hours ago)

Because you’re already paying more for the hardware with a Mac.