In a time before Slack and Discord, Arch's IRC channels were the place to ask and receive help from experts. It was the place to learn system administration. The wiki was so good that it wasn't just a reference for Arch Linux, but most other Linux distributions. Partitioning the disks, formatting the partitions, configuring the network, setting up a boot loader, installing a window manager, and even configuring basic things like laptop suspend and hibernate and bluetooth.īut it was maybe the community that was the best part. To install it, you'd set up each part of the operating system in a painstakingly manual way. Arch called this approach user-centric, as opposed to user-friendly. Instead, you'd download an installation image onto a USB drive and follow the instructions on the insanely detailed ArchWiki. Arch Linux didn't have an installation script. There was an explosion of Linux distributions in the 2000s but one stood out for hobbyists called Arch Linux.Īrch Linux took a much different philosophy than the distributions who tried to package Linux with bells and whistles for end-users in an installation script. Instead, there were higher-level pure software abstractions to play with: open source operating systems like Linux. By then, most programmers weren't interested in learning how to solder or ordering circuit boards. The Commodore 64 of the 2000s wasn't even a piece of hardware. These hackers might have taken one apart and put it back together or written a BASIC compiler for it (Gates got started on the Altair 8800 a decade before).īut programmers like me didn't start with the Commodore 64. It was a low-end computer that was sold in retail stores instead of electronics stores. In the 80s' a programmers origin story probably included the Commodore 64.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |