Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Thursday August 10 2017, @10:41PM   Printer-friendly
from the bashing-Windows dept.

Arthur T Knackerbracket has found the following story:

Microsoft has announced that Windows Subsystem for Linux (WSL) is coming to Windows Server.

Microsoft's adding it to Windows Server for the same reasons it added it to Windows: it wants developers to have whatever tools they prefer at their disposal.

Sysadmins are also on Redmond's mind, it says. "If you're a server engineer that needs to run node.js, Ruby, Python, Perl, Bash scripts or other tools that expect Linux behaviors, environment or filesystem-layout, the ability to install and run Linux with WSL expands the tools at your disposal on Windows Server."

Redmond snuck WSL into Windows Server Insider Build 16237 without including it in the announcement. It's now issued instructions on how to install it.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by edIII on Friday August 11 2017, @02:58AM (3 children)

    by edIII (791) on Friday August 11 2017, @02:58AM (#552073)

    That's what forking is for. You go back to what isn't now patent encumbered by Redmond and start work from there. I think that those communities would be incredibly stupid to pay attention to Microsoft for one second. When somebody comes around complaining their MS-Linux isn't working, you remind them that Linux can be installed without MS Server in the mix. In fact, that's predominately how servers ARE operating right now. Without Microsoft :) That and I'm pretty sure it's just as easy to virtualize a true Linux server on the same Windows Server, and then use networking to have your programs/APIs communicate between them. I'm no stranger to making Windows platforms work with Linux platforms, and I didn't need to shove Linux into Microsoft to do it. I wonder which one is truly more cost effective?

    If commercial support contracts get involved they may try and throw their weight around, but again, anybody getting into bed with Microsoft knows this. Or seemingly Redhat at this point.

    "If you're a server engineer that needs to run node.js, Ruby, Python, Perl, Bash scripts or other tools that expect Linux behaviors, environment or filesystem-layout, the ability to install and run Linux with WSL expands the tools at your disposal on Windows Server."

    Uh huh. Except that node.js, Ruby, Python, PERL, and Bash scripts can install and run on BSD and deal with BSD environments, filesystem-layouts, and behaviors. They imply those platforms and languages strongly expect only Linux environments, which may be misleading. For that matter, to my knowledge, all of them except Bash can run on Windows. Bash is pure Linux/BSD commands so probably not, but even Perl has Strawberry and ActiveState Perl to use it on Windows. The rest of them has similar support to run natively and directly in Windows. So why does Window need native support for Linux again?

    I'm certainly not finding any great difficulty using anyone of those in OpenBSD at the moment, excepting Ruby. Not using anything with Ruby under the hood. That I know of.

    So if they fuck up Linux land too much, there might be a ton of refugees coming in to BSD land. That's just fine. Bring us your tired, sick, and wretched poor :)

    --
    Technically, lunchtime is at any moment. It's just a wave function.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by kaszz on Friday August 11 2017, @03:23AM (2 children)

    by kaszz (4211) on Friday August 11 2017, @03:23AM (#552089) Journal

    You can fork code but patents are harder to get around.

    One problem area is that manufacturers of cameras, printers, recorders, etc makes use of exFAT a successor to FAT32 which is encumbered. Even if someone implements the code independently, it's fucked with patents. And if a free format is created, manufacturers of equipment will not implement it.

    So why does Window need native support for Linux again?

    Because Windows is particularly messy to get it to work with Unix programs?
    Most Unix machines are just download-configure-compile Done! Windows.. not so.

    When somebody comes around complaining their MS-Linux isn't working

    That is the time to remind that if they go for shit, they pay with $$. Unless it contributes to screwing Microsoft.

    • (Score: 0) by Anonymous Coward on Friday August 11 2017, @09:29AM (1 child)

      by Anonymous Coward on Friday August 11 2017, @09:29AM (#552220)

      You can fork code but patents are harder to get around.

      Bullshit. Get a lawyer. If the code is forked, if it can be forked, it is not subject to copyright. And if it is, fuck it, change five words in the doc, and rename it. How can we have this level of stupidity and MicroSerf shilling on SoylentNews?

      • (Score: 0) by Anonymous Coward on Friday August 11 2017, @02:16PM

        by Anonymous Coward on Friday August 11 2017, @02:16PM (#552283)

        You apparently don't understand the difference between copyright and patents.

        Or maybe you are just trolling?