Linux vs. Macintosh


Both of them trace their ancestry from Unix. That explains the robustness vis a vis Windows, which remains downright crappy and buggy operating system. The similarity ends there.
Linux does not boast of the top of the line corporation promoting it- yet for millions of users, it means freedom of choice. I believe it is this freedom of choice that initially attracted me to it. Perhaps the fact that I could easily run Linux on my old AMD Athlon without any costly upgrade. Or high initial cost of the hardware. Giving me essentially the same peace of mind that Apple users claim.
Linux gives the users a vast choice. The newer versions of Linux are truly plug and play compatible.
To back up Linux users, there are host of newbie websites, IRC channels, forums et al where in someone would be there to solve your problem.
The fact is that Linux is the perfect answer to proprietary software like Apple. I strongly believe that Linux has shown us a path to achieve that goal of bridging the digital divide. Apple could learn a few things from this.
-
- Login or register to post comments
Printer-friendly version
- 1702 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Events: Video Conferences, Code.gov, and LibreOffice
| GitLab Web IDE
|
Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
| Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
|
Recent comments
3 hours 55 min ago
3 hours 55 min ago
3 hours 57 min ago
7 hours 3 min ago
7 hours 15 min ago
14 hours 7 min ago
1 day 16 hours ago
1 day 17 hours ago
1 day 22 hours ago
2 days 23 hours ago