Apricity OS: A Beautiful Arch Linux Distro
apricityos.com
apricityos.com
SigLevel = Never
Server = http://apricityos.com/apricity-core/
This instructs the package manager (pacman) to load system packages over an unencrypted connection and disables all signature checks.
Source:
https://github.com/agajews/ApricityOS/blob/master/build/pacm...
https://wiki.archlinux.org/index.php/Pacman/Package_signing#...
Arch is great and all. I love using it, but I get pretty impatient with people who think they're smarter than everyone else because they can follow the detailed instructions in a well-written and lovingly maintained wiki. I get similarly impatient with B.S. Arch derivatives. If you want Ubuntu, just use Ubuntu. It's based on a perfectly legit distribution.
Back when I had freedom of choice for my OS at my place of employment, I wanted to learn about Linux so I chose it. Then I wanted to learn more about Linux so I moved from Ubuntu to Arch. At first, the documentation is a lifesaver. However, a bit of time invested in reading it carefully will also really educate someone in so many aspects of an OS. Not only that, but so many of the things that someone would really want to use are so well documented. I learned more about PostgreSQL administration and X from the Arch Wiki than the documentation from the actual projects themselves.
Or at least that's the theory. In practice I'm mostly still trying to get my mouse to work. :-P
*As opposed to layering a declarative system over an imperative one, which I think is more or less what Chef, Docker, Ansible, et cetera are doing.
/nix/store/b6gvzjyb2pg0kjfwrjmg1vfhh54ad73z-firefox-33.1/
if a package is "installed" in an environment (it could be global, user local or temporary), its files are sym-linked in the "original" position (e.g. /usr/bin/firefox etc etc)This has several consequences. It means binaries distributed with the expectation of libraries being in their original position (e.g. /usr/lib/libc.so) don't work as is. It also means scripts depending on the presence of /usr/bin/bash are broken (which happen far too often).
I love NixOS, but that is one of the biggest annoyance I have with the system.
The problem comes from anything that's not packaged. Things that exist outside the nixos ecosystem.
For instance, the Android SDK is a bit of pain in the neck to install via the nixpkgs : it's a mutable piece of software with pieces that auto-update themselves, made of lots of smaller packages that aren't bundled in the main package, etc...
However, the binaries google provide doesn't run properly on nixos by default because of the non-standard install (has to set LD_PRELOAD so it can find the libc).
nix packages are not exactly packages, as in rpm or deb files, they are expressions in a functional language (think build recipes). there is a central repository of recipes on github: https://github.com/NixOS/nixpkgs/tree/master/pkgs
but you can make your own, and eventually make a pull request. They are more similar to Arch's PKGBUILDs. Packages in the central repository are constantly built by a continuos built process (http://nixos.org/hydra/), that works both as a binary cache and as a testing system. This is an expression I wrote to install SuperCollider plugins https://gist.github.com/gosub/a42e265ec38d9df203d6 using the Arch PKGBUILD as a reference https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sc3-p...
He is styling himself and the OS as a professional project (at least that's the vibe I get from the website[2]) and he is actually asking for money[3] while he is putting his users in serious danger (as the current top post[4] illustrates) caused by his "rookie choices". This is deceptive and prompts unsuspecting users to install a High School project on their personal computers in the mistaken belief that they deal with someone skilled. I have very little sympathy for that.
Don't get me wrong, I'm young and I put up my projects as well, but I don't style myself a professional or ask for financial support for my half-assed code while keeping silent about the real nature of my project. Thinking about it, I might take down some code on GitHub or at least put up a big disclaimer.
[1] https://github.com/agajews/ApricityOS/issues/11
[2] check the "about the team" section, for example
(Plus when someone posts your GitHub repo to HN for some random reason, that disclaimer can save you a lot of hassle.)
> We are a Chicago based team of developers, dedicated to creating useful, intuitive software that helps people better integrate digital computing into their daily lives
The GitHub repository also proves it's not "we": https://github.com/agajews/ApricityOS/graphs/contributors
http://storage.j0.hn/Screen%20Shot%202016-04-04%20at%209.35....
3.2 million additions, 916k deletions 20 commits.
The beauty of Arch is that you set it up from head to toe, so you only have the things you need most. And if something breaks, you're more likely to be able to fix it.
Accept no substitute. Vanilla Arch forever.
(I accept that some people don't care about how the sausages are made. In that case, use Fedora or Debian or Ubuntu, in order of similarity to Arch.)
> without having the hassle of having to know how things are configured and what not
Really ? User doesn't need to know how to set and fix things on Ubuntu/Fedora/Debian ? Now that's a bold statement.
Or Apricity?
I won't be using this distro, but you've done a seriously poor job of condemning it in favor of some cherry-picked alternatives.
I use Arch for my SoC devices (RPi2 and Odroid XU-4), and for that it is hard to beat. I install what I need, configure it and then forget about it. But for a desktop? I didn't get a computer so that I could spend an hour getting WIFI to work the way I want.
I have built LFS more than a dozen times, I used gentoo for the better part of a decade (back in the days when linux actually was harder to use than osx/windows). I don't have to prove myself worthy any more. Give me an easy way to setup arch with stuff like X, network-manager and media hotkeys working out of the box and I'd switch any day.
So: arch is a very nice distro, but online it has somewhat become what gentoo was in the early 2000: an e-penis enlarger. The only thing it proves is that you have the time and knows how to copy and paste commands from the arch wiki.
Now I run emacs on CentOS 7. I only do security updates and have been using guix to handle userspace (Userspace = mostly emacs).
For work I have an Ubuntu laptop. We code pascal, so I almost never leave the GUI. After configuring Unity I actually like it a lot. I might switch to ubuntu on their next LTS release (which, after all the kinks are worked out, will be 16.04 + ~4 months)
Setting up wifi was as simple as just installing whichever manager you want and getting going, though. Contrary to a lot of peoples' experiences I seem to have a really easy time with Arch. Most of it just works after install.
I just recently bought a new laptop that I had set up within a day. A lot of that time was spent playing around with various hidpi settings, though.
And it certainly helps that I have most of my configurations in my dotfiles repo (including media key bindings).
I love Arch, but Debian min install will always have a place in my heart for getting set up easily while still being extremely fast and custom.
That's it, really. There's a bunch of stuff you probably want for a functional system, like user accounts and graphics drivers and stuff. And yes, Arch is still a pain with laptops. But with practice you can get it up "from scratch" in 20 minutes tops.
Hopefully you'll note that I didn't actually say anything about proving yourself. I even gave a list of other distros. But my point was that you don't need an Arch-based distro when there are plenty of distros that are better at giving you an easy way to set them up.
If one's ego is so seriously fragile that they depend on an operating system to feel adequate... well, it's kind of sad. It wasn't my intent to imply anything about people using distros I like less, if that's what you got. But this distro in particular is probably not as useful, because there are many more "user-friendly" distributions.
[1] https://www.reddit.com/r/unixporn
[2] https://www.reddit.com/r/unixporn/comments/3r85qh/bspwm_ligh...
[3] https://www.reddit.com/r/unixporn/comments/3og32q/bspwm_wip_...
[4] https://www.reddit.com/r/unixporn/comments/3xen3g/bspwm_func...
Most of the stuff there is nice but it's nothing more than this really:
- A nice background.
- GTK themes and icons which I have, easy enough.
- A nice looking bar, but the one most commonly used with bspwm is made up by a messy shell script.
- Custom terminal colours, looks good in ncmpcpp but I need a usable terminal.
There's an excellent open source project which does this and much more: https://play.google.com/store/apps/details?id=org.kde.kdecon...
My favorite things about KDE Connect:
1) shared clipboard between mobile and PC
2) "send file to phone" - context menu in Dolphin / "send file to PC" in Android to quickly exchange single files
3) browse the whole Android file system (and copy/delete/edit files) directly from your file manager in Linux
KDEConnect still pulls in a few dependencies, but it's not 300MB anymore.
Storage is cheap nowadays and KDE applications generally are of such high quality that it's definitely worth it.
Other examples are Digikam (hands-down the best picture organizer) and Krita (which rivals Photoshop for digital artists).
Things just break or otherwise don't work far too often.
So, kudos to the guy who put this distro together but without addressing this issue I don't think we're going to see an "easy to use" Arch-based distro any time soon.
I'm definitely speaking just as an onlooker and a novice here as I'm not involved in any open source development, but it feels like the whole Linux community would benefit from more rigorous API versioning and better documentation of interfaces between components. Even with distros that presumably do a lot of QA on their core packages like Fedora or Ubuntu, it feels like stuff breaks a LOT in Linux because of dependencies on the wrong versions of components. It must be a really tough problem.
It could be that I'm just more of a unix beast now and so do it automatically without thinking. I remember having to edit Xorg configuration files, having tons of unsupported hardware, etc.
Arch has basically just worked for me on all my machines with the exception of some esoteric features (e.g. zfs requires a bit of fiddling).
What problems have you had in particular?
Being any sort of early-adopter on the hardware front will, as always, get you punished with configuration file editing, though.
Arch will make a better foundation distro IMO.
But I like Arch too. I just switched away from it because I got tired of things breaking if I wasn't religiously upgrading.
I found that upgrading Ubuntu/Debian to the next release always screwed everything up as basically all the packages changed. Heck fedora couldn't even update to the next release until fed up came out.
[1] my wifi chip took minutes to initialize due to proprietary blob issues.
After trying Arch and running into too many irritating bugs that I didn't have the patience to fix I gave up on it.
Plus this didn't give me a good impression of the community's professionalism either: http://news.softpedia.com/news/Manjaro-Devs-Fix-Embarrassing...
That said, I don't feel the idea of the Arch community revolves around professionalism; it is really an amateur thing, in the positive sense.
lyk dis if u cringe evrytiem
Seriously though, it's such a cop out and it cheapens whatever you're trying to sell.
It's up there with "nice" and "interesting" in terms of non-value words, IMO.
Much more useful would be to describe some of the goals that you, if you're the developer, consider beautiful. What, specifically, are you going for? If I'm looking at a project that's what I want to know. Most people don't set out to make ugly projects (well, mostly [1]) so that's the key differentiator: what subjective definition of "beautiful" is operative in the project's design, and what tradeoffs are being made to pursue it?
[1]: Maybe not if you're really into "New Jersey Style" / https://en.wikipedia.org/wiki/Worse_is_better
Firefox 45.0.1 64bit Fedora 23
They use the default archlinux mirrors and add one for the extra packages
https://github.com/agajews/ApricityOS - binaries in source control, sigh.
Edit: Looks like it could be profitable - I wonder how much of this makes it back to Arch: https://github.com/agajews/ApricityOS/blob/master/PATRONS
FWIW, it now correctly asks you in the setup flow and you can add/remove yourself in the preferences: https://i7.createsend1.com/ei/d/A1/835/432/153754/csfinal/pr...
You might want to think over how you communicate with your customers. Customer privacy isn't something you can just shrug away.
Relatedly, if anyone reading is interested in a full time developer relations/evangelist role at a small startup, please send me a note! :)