Language Selection

English French German Italian Portuguese Spanish

John Carmack thinks the Steam Machine’s biggest problem is Linux

Filed under
Linux
Gaming

Ever since Valve announced its three-tier approach to bringing PC gaming to the living room — Steam OS, the Steam Machine, and the Steam Controller — people have been divided on whether or not it’s a sound idea. John Carmack, a man who changed the face of PC gaming at Id Software, thinks the Steam Machine’s odds of succeeding are “a bit dicey.”

Once upon a time, Carmack — though regularly heralded as a PC gaming genius and visionary to this day — thought Valve’s digitial distribution platform, Steam, wasn’t the greatest of ideas. He points that out himself, but maintains that despite his previously incorrect prediction regarding one of Valve’s ambitious ideas, the Steam Machine still won’t be an instant hit. Rather than think the Steam Machine will travel down a rocky path because it’s basically just a regular PC, or because Valve has gone a little crazy, Carmack feels the biggest hurdle the Steam Machine faces is Linux.

more here and 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.