On switching to Arch Linux 14 years ago
Hm. Interesting. So do you deploy your code to the VM? Or do you edit your work over an SSH connection and terminal editor?
HN user
TwinEngine
2 karma
Cofounder of Twin Engine Labs, a design and development firm largely for API-backed iOS apps. We work in Arch Linux, Postgres, Redis, CouchDB, MongoDB, and Rails. On the iOS side of the engineering department, we work natively in Objective-C and have extensive experience with data driven apps, as well as using the native APIs (camera, GPS, Push Notifications, etc).
Posts0
Comments4
No posts found.
On switching to Arch Linux 14 years ago
Wow. That's fantastic. I'll do that tonight actually. Because ArchLinux is constantly moving so quickly, I'd like to know what I might have to deal with when I run a pacman -Syu.
I think I'm a convert. Now, if I could get OSX to boot in a VM, and dedicate the entire HDD to Arch, that would be perfect. For some reason my Macbook won't boot the 64bit Archboot iso. But I'll wrestle that demon another day, heh.
Thanks for sharing your experience.
On switching to Arch Linux 14 years ago
I'm curious how you enjoy working with virtual machines instead of all native?
This is admittedly my first day of not being just a lurker here, so forgive me if I shouldn't ask this here, but what is your setup and environment like?
I've considered running VMs for each client I work on, but am unsure if it'd just be a hassle or not.
On switching to Arch Linux 14 years ago
I have switched from OS X, to Arch (2 months now full time?), so I'm not exactly coming from your angles, but I will say that every single piece of software I've ever needed has been in the main repos, and if it wasn't there, it was in the AUR.
What's fascinating is that AUR packages get voted up. Packages past a certain threshold get the choice to become a main repository package. Creating and maintaining community packages is a snap with their build system (though I've never done it personally, but understand the mechanism).
On top of that, re-building your kernel, should you ever need to (I did), is dead simple.
So to your main argument of more compromise, I believe it to be false. It's less compromise to me. I feel I have to compromise with an Ubuntu distro that has made all the choices for me (and for a client-services company at least, you'll come to the day where you need to know what those choices were). Now I have the power and ability to make the decisions I want to make, especially following the extensive wiki and super helpful forums (I feel like you could compare the helpful responses there with the type of intelligence that this community possesses).
To your final point, of the "just because I value things that help me learn Linux", this will absolutely help you learn Linux. And once you know it the Arch way, most of the other ways seem completely opaque. The standards of packages in Arch allow you to find all the important bits of all the software you installed. My company uses Arch for our servers as well because we know we can count on the standards and have up to date software that, for us, "just works".