SoylentNews is people
SoylentNews
from the temperature-in-Hell-plummets dept.
NEW YORK—At its first Connect event in 2013, Microsoft released Visual Studio 2013. In 2014, it announced the open sourcing of .NET, and in 2015, the open sourcing of the Visual Studio Code editor. The big news this year? Microsoft, the company that has built an empire on proprietary, closed-source software, has joined the Linux Foundation as a platinum member.
Microsoft has been a big contributor to Linux over the past several years, primarily focusing on improving support for its Hyper-V hypervisor. Jim Zemlin, executive director of the Linux Foundation, said that in becoming a member, "Microsoft is better able to collaborate with the open source community to deliver transformative mobile and cloud experiences to more people."
Microsoft's increasing commitment to open source has been met with some cynicism (and please, beloved commenters—try to refrain from "embrace, extend, extinguish" posts, as the very concept is preposterous when it comes to Linux), but with projects such as Visual Studio Code and .NET, is starting to win hearts and minds. The company does appear to be a reasonably good open source citizen, not merely publishing source code repositories that are occasionally updated from an internal development branch, but actually performing development in the open, accepting community contributions, and seeking community consensus when it comes to new features.
(Score: 2) by acid andy on Thursday November 17 2016, @05:43PM
What trouble? I wasn't aware they caused any trouble for the users. Are you talking about trouble for the distro developers?
If a cat has kittens, does a rat have rittens, a bat bittens and a mat mittens?
(Score: 2) by HiThere on Thursday November 17 2016, @07:57PM
You may not be aware that systemd causes end users trouble, but I am, and my problems are trivial compared to some that have been reported. (I've always eventually been able to get my systems back up, even if it meant reinstalling the OS.) If you are a user who follows the most common use case, then probably systemd won't cause you any problems. If you have an unusual configuration, be prepared for some work, at best. A couple of times it caused so much trouble I started thinking of BSD, but I was always able to eventually get the thing working again. It's just that every time I re-install my alternate system (i.e., the one in the partition I'm not doing most of my work in...which varies) I need to go through and hand edit the fstab table. For awhile it was worse, but they seem to have polished systemd a bit. I still don't like the concept of binary logs, but I'm not much of a sysadmin, so that doesn't directly impact me unless problems different from what have happened so far occur. And I think the problems with it bricking systems were usually with the beta version (which apparently should have really been called the alpha version).
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 2) by acid andy on Thursday November 17 2016, @08:55PM
No, I'm quite sure systemd can cause end users trouble in a distro that uses it. I don't use systemd - I do all I can to avoid it! The GP was saying it causes trouble for non-systemd distributions (or that they have trouble). I'm asking what kind of trouble it is, as I've not had any as a user.
If a cat has kittens, does a rat have rittens, a bat bittens and a mat mittens?
(Score: 2) by HiThere on Thursday November 17 2016, @10:58PM
For users of distros that avoid systemd, the problem is packages that are re-written to depend on its presence.
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.