Language Selection

English French German Italian Portuguese Spanish

What does Apple’s move mean for Linux?

Filed under
Linux
Mac

Now that the rumors have turned out to be true, what is this going to mean for Linux — if anything?

Well, let’s look at the facts that we have so far. Linux has taken off in large part because it runs on commodity hardware (Intel and Intel-compatible), and provides a Unix-like OS that’s great for a lot of tasks — and much cheaper than its proprietary Unix cousins. Linux has a solid presence in the server market, and is developing a presence in the desktop market.

Apple, on the other hand, is working on developing a presence in the server market and the desktop market. While it’s widely held that Apple has a wonderful desktop OS, it only runs on (pricey) PowerPC hardware from Apple and doesn’t run all the apps that people are used to from Windows.

Apple’s move to Intel isn’t going to change much. Firstly, Apple seems poised to continue its exclusionary stance, and will require users who want to run Mac OS X to buy the whole kit and kaboodle from Apple. The ZDNet piece quotes Apple Senior Vice President Phil Schiller as saying that "We will not allow running Mac OS X on anything other than an Apple Mac." This means that Apple computers will still continue to carry a price premium that many users are unwilling to pay unless they’re already convinced they want to run Mac OS X. Even Apple’s low-end Mac Mini is still high-priced compared to similarly-equipped Dell computer. (Apple users can now abandon the "but PowerPC is so much better than Intel!" since even Apple is giving up that line of reasoning.)

On the other hand, users can try out Linux today on the computer they’re using to run Windows. No serious financial risk involved, download a few ISOs or buy a boxed set and they’re off and running. If it doesn’t work out, they can go back to Linux secure in the knowlege that they won’t have wasted much more than a few dollars and the time to test out Linux.

Full Blog.

More in Tux Machines

Security Leftovers

  • Security updates for Thursday
  • Security Tips for Installing Linux on Your SysAdmin Workstation
    Once you’ve chosen a Linux distro that meets all the security guidelines set out in our last article, you’ll need to install the distro on your workstation.
  • Fedora 26 crypto policy Test Day today (2017-03-30)!
  • Open-source developers targeted in sophisticated malware attack
    For the past few months, developers who publish their code on GitHub have been targeted in an attack campaign that uses a little-known but potent cyberespionage malware. The attacks started in January and consisted of malicious emails specifically crafted to attract the attention of developers, such as requests for help with development projects and offers of payment for custom programming jobs. The emails had .gz attachments that contained Word documents with malicious macro code attached. If allowed to execute, the macro code executed a PowerShell script that reached out to a remote server and downloaded a malware program known as Dimnie.
  • A scramble at Cisco exposes uncomfortable truths about U.S. cyber defense
    When WikiLeaks founder Julian Assange disclosed earlier this month that his anti-secrecy group had obtained CIA tools for hacking into technology products made by U.S. companies, security engineers at Cisco Systems (CSCO.O) swung into action. The Wikileaks documents described how the Central Intelligence Agency had learned more than a year ago how to exploit flaws in Cisco's widely used Internet switches, which direct electronic traffic, to enable eavesdropping. Senior Cisco managers immediately reassigned staff from other projects to figure out how the CIA hacking tricks worked, so they could help customers patch their systems and prevent criminal hackers or spies from using the same methods, three employees told Reuters on condition of anonymity.
  • NTPsec: a Secure, Hardened NTP Implementation
    Network time synchronization—aligning your computer's clock to the same Universal Coordinated Time (UTC) that everyone else is using—is both necessary and a hard problem. Many internet protocols rely on being able to exchange UTC timestamps accurate to small tolerances, but the clock crystal in your computer drifts (its frequency varies by temperature), so it needs occasional adjustments. That's where life gets complicated. Sure, you can get another computer to tell you what time it thinks it is, but if you don't know how long that packet took to get to you, the report isn't very useful. On top of that, its clock might be broken—or lying. To get anywhere, you need to exchange packets with several computers that allow you to compare your notion of UTC with theirs, estimate network delays, apply statistical cluster analysis to the resulting inputs to get a plausible approximation of real UTC, and then adjust your local clock to it. Generally speaking, you can get sustained accuracy to on the close order of 10 milliseconds this way, although asymmetrical routing delays can make it much worse if you're in a bad neighborhood of the internet.
  • Zelda Coatings
    I assume that every permutation of scams will eventually be tried; it is interesting that the initial ones preyed on people's avarice and dishonesty: "I will transfer millions to your bank account, then you share with me" - with subsequent scams appealing to another demographic: "I want to donate a large sum to your religious charity" - to perhaps capture a more virtuous but still credulous lot. Where will it end ?

Tizen and Android

Linux and Linux Foundation

Mesa and Intel Graphics