Microsoft open sources .NET

Microsoft open sources .NET, takes it to Linux and OS X

NEW YORK—Earlier this year, Microsoft open sourced a big chunk of .NET, publishing its new compiler, Roslyn, and many .NET libraries under the Apache license. Today, the company took that same open sourcing effort a great deal further. Microsoft announced that its full server .NET stack, including the just-in-time compiler and runtime and the core class libraries that all .NET software depends on, will all be open sourced.

The code will be hosted on GitHub and published under a permissive MIT-style license.

With this release, Microsoft wants to make sure that the .NET stack is fully functional and production quality on both Linux and OS X. The company is working with the Mono community to make sure that this platform is “enterprise-ready.”

Microsoft Open Sources .NET, Saying It Will Run on Linux and Mac

Satya Nadella’s rapid reinvention of Microsoft continues.

In yet another bid to make up lost ground in the long march to the future of computing, Microsoft is now open sourcing the very foundation of .NET—the software that millions of developers use to build and operate websites and other large online applications—and it says this free code will eventually run not only on computer servers that use its own Windows operating system, but also atop machines equipped with Linux or Apple’s Mac OS, Microsoft’s two main operating system rivals.

“We want to have a developer offering that is relevant and attractive and valuable to any developer working on any kind of application,” says S. “Soma” Somasegar, the 25-year Microsoft veteran oversees the company’s wide range of tools for software developers.

Panasonic Viera DLNA client always lists album tracks in alphabetical order

Problem: The Panasonic Viera DLNA client always lists album tracks in alphabetical order when typically album track order is what is expected.



The Viera DLNA client does not request album tracks in track order, nor does the client have an option to do so. The workaround for this problem is to modify minidlna, specifically the file, upnpsoap.c. N.B. This change is not an attempt to fix a bug in minidlna, but a way to get around a limitation in a DLNA client.

I’ve created a GitHub repository for minidlna with my changes. If you already have the source to minidlna 1.1.4, you only need the file, upnpsoap.c.

Hewlett-Packard looks to end support for OpenVMS in 2020

OpenVMS, R.I.P.: 1977-2020?

Hewlett-Packard looks to end support for OpenVMS, a system long valued for its reliability and break-through features, in 2020.

There’s an entire generation of people who were born, graduated college and are well into their IT careers, who may have no idea that this OS, introduced in October 1977 by Digital Equipment Corp., even exists. That alone puts a limit on the operating system’s life expectancy.

HP says it has about 2,500 unique customers running OpenVMS, but that count only includes customers with whom it has a relationship. There are other users who are either supporting themselves or using third parties to keep the 36-year-old OS in shape. DEC was acquired by Compaq and Compaq by HP.

HP said Monday that it will continue support for OpenVMS on its Integrity i2 servers “through at least the end of 2020.”

The dates are not carved in stone, said Lorraine Bartlett, vice president of marketing strategy and operations for HP’s Business Critical Systems unit. “While we do have a targeted end date, that doesn’t mean support will definitely end,” she said.

HP will assess customer needs as time goes on, she said.

HP will continue to sell OpenVMS on Itanium platforms running the Tukwila chip, but it will not be supporting the latest Poulson chip, which was released last fall. The announcement came just before the start of HP’s big user conference here.

OpenVMS has long been praised by its users for clustering and disaster-tolerant capabilities, security and overall reliability. It runs mission-critical systems and because of its consistent performance it tends to get little attention, except from a dedicated user community.

One consultant, who didn’t want to be identified for fear of jeopardizing existing relationships, said porting OpenVMS systems to another platform will entail much work.

The OpenVMS operating system provides a lot of the capabilities that other operating systems either don’t have, or don’t do in a similar enough manner, said the consultant. “You typically end up re-architecting the whole thing, which can take several years for a large and complex set of applications.”

End-of-life decisions are likely to trigger push-back from users, consultants and anyone involved in support and operations. HP’s decision to end support for the HP 3000 more than a decade ago caused quite a stir and prompted users to organize an effort to keep the system operational.

Stephen De Dalto, OpenVMS consultant, said: “It’s been a slow, but definite, migration from VMS, because customers have to continue to justify the OS since the higher-ups keep saying, ‘Move to Linux or Windows or Unix,’ without knowing the consequences of such a move.”

Dalto said he was shocked by HP’s decision because he would have expected HP to continue to develop and move to the latest Itanium chips.

“It’s a bad decision, because not moving forward to the latest and greatest is the same as moving backwards — and no one wants to move backwards,” said Dalto.