Language Selection

English French German Italian Portuguese Spanish

Linux: Strong and getting stronger

Filed under
Linux

At the Linux Foundation's annual collaboration summit in San Francisco on Wednesday, Executive Director Jim Zemlin kicked off the event with some interesting perspectives on the state of the Linux marketplace today.

The short version: Linux is going strong and getting stronger.
According to Zemlin, the macro-economic trends have played to the strengths of Linux and open source. Few can dispute that Linux is cheaper to procure and run in comparison to proprietary platforms. This applies not only to end users but also to device manufacturers and development shops building platforms.

Would Google be the company it is today using proprietary technologies like Microsoft.NET? The answer is likely not. Service providers in any form (aka cloud providers) need to maintain control over their platform and only Linux and open source allow for that control.

Because there are new devices in the market and the nature of client computing is changing in the industry, Linux is much more attractive.

rest here




More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.