5 ms·

I still don't understand why people would recommend going away from a true UNIX with a decent UI, to switch to Windows. Windows remains an abomination in my per

by sgt 6y ago

I still don't understand why people would recommend going away from a true UNIX with a decent UI, to switch to Windows. Windows remains an abomination in my personal experience, and sprinkling a Linux subsystem on it doesn't sound like a truly great argument to switch.

nix23 6y ago
I'm NOT a Windows Fan, in Fact i use BSD, but if you want "a no problem solution" where you can develop and everything else..windows is your goto. That true Unix sentence is getting old...i really means nothing
- toyg 6y ago
  > "a no problem solution" where you can develop You'll have to jump through some hoops to develop web stuff on Windows (unless you do it The MS Way ™). The fact that WSL exists is testament to this fact.
  - nix23 6y ago
    That's what i mean, develop on Linux, Play/work on Windows ;)
  - scarface74 6y ago
    In what way will you have trouble developing “web stuff” on Windows? I develop on Windows and deploy to Linux all of the time. Admittedly, I stay away from the clusterf%%% that is the modern front end environment like the plague. But I code in Python, C# (.Net Core) and Node all of the time.
    - toyg 6y ago
      You said it yourself: you do the part that actually matters NOT on Windows. That's a big hoop. You do Python - so you likely have to do things like remembering venv/bin vs venv/Scripts, or you're using containers exclusively. Those are hoops. The fact you got used to it and MS tried hard to lower that friction in recent years, is fundamentally irrelevant. The web stack is Linux-first.
      - scarface74 6y ago
        As far as Python. I don’t have to remember to do anything. I use pip install from the command line. I write and debug my code locally, push it and my CI/CD pipeline build either my Lambda zip file or Docker container and push it. The same is true for .Net Core and Node. When would I ever build directly from my computer and push to another computer? This is 2020. We have CI/CD pipelines. If I did actually deploy to a VM, the only difference would be that pipeline would do that instead.
        toyg 6y ago
        > my CI/CD pipeline build either my Lambda zip file or Docker container I guess you've already forgotten how long Docker took to work decently under Windows. Pretty much all those magic CI/CD tools you are effectively forced to use, are written on (and for) Linux first. Linux/Mac/BSD users get first pickings and can always choose to ignore this or that tool if they feel like it. You don't.
        scarface74 6y ago
        My CI/CD pipeline doesn’t run on Windows. When I’m writing my code in any of the three languages I mentioned, I am running them straight on my Windows box. I push the code and my Linux based build server, pulls in the dependencies, builds the artifacts - either Docker container or Lambda - and deploys it. I first played with Docker on Windows in 2014. I didn’t really start using it for anything in production until 2019. But talking about who did it first is about like Mac nerds bragging about having long file names before Windows. No one cares.

by sgt 6y ago

nix23 6y ago

I'm NOT a Windows Fan, in Fact i use BSD, but if you want "a no problem solution" where you can develop and everything else..windows is your goto. That true Unix sentence is getting old...i really means nothing

toyg 6y ago
> "a no problem solution" where you can develop You'll have to jump through some hoops to develop web stuff on Windows (unless you do it The MS Way ™). The fact that WSL exists is testament to this fact.
- nix23 6y ago
  That's what i mean, develop on Linux, Play/work on Windows ;)
- scarface74 6y ago
  In what way will you have trouble developing “web stuff” on Windows? I develop on Windows and deploy to Linux all of the time. Admittedly, I stay away from the clusterf%%% that is the modern front end environment like the plague. But I code in Python, C# (.Net Core) and Node all of the time.
  - toyg 6y ago
    You said it yourself: you do the part that actually matters NOT on Windows. That's a big hoop. You do Python - so you likely have to do things like remembering venv/bin vs venv/Scripts, or you're using containers exclusively. Those are hoops. The fact you got used to it and MS tried hard to lower that friction in recent years, is fundamentally irrelevant. The web stack is Linux-first.
    - scarface74 6y ago
      As far as Python. I don’t have to remember to do anything. I use pip install from the command line. I write and debug my code locally, push it and my CI/CD pipeline build either my Lambda zip file or Docker container and push it. The same is true for .Net Core and Node. When would I ever build directly from my computer and push to another computer? This is 2020. We have CI/CD pipelines. If I did actually deploy to a VM, the only difference would be that pipeline would do that instead.
      - toyg 6y ago
        > my CI/CD pipeline build either my Lambda zip file or Docker container I guess you've already forgotten how long Docker took to work decently under Windows. Pretty much all those magic CI/CD tools you are effectively forced to use, are written on (and for) Linux first. Linux/Mac/BSD users get first pickings and can always choose to ignore this or that tool if they feel like it. You don't.
        scarface74 6y ago
        My CI/CD pipeline doesn’t run on Windows. When I’m writing my code in any of the three languages I mentioned, I am running them straight on my Windows box. I push the code and my Linux based build server, pulls in the dependencies, builds the artifacts - either Docker container or Lambda - and deploys it. I first played with Docker on Windows in 2014. I didn’t really start using it for anything in production until 2019. But talking about who did it first is about like Mac nerds bragging about having long file names before Windows. No one cares.