In recent times, unfortunately, I’ve been seeing a bunch of articles about “Elementary OS“.
TLDR; It’s an out-of-date version of Ubuntu, with some ugly skins thrown on top.
Just being realistic
According to the Elementary OS website, it’s designed to be “Speedy” – however, a quick comparison test by booting a vanilla Ubuntu 12.04 (of which, EOS is based), and ElementaryOS Luna, shows a whopping increase in boot time of 7 seconds.
It’s also marketed as “Beautiful and Usable.”
Upon booting and logging in, the cheap OSX dock rip-off “Plank” immediately crashed. Seems pretty usable.
Designed by a spotted face
Beautiful? The entire OS has directly tried to rip off Mac OSX, but, failed.
Do you remember trying to draw and copy cartoons as a child, only to be disappointed they weren’t quite the same? This is primarily what I feel with their clunky, ugly interface.
The user interfaces look like it’s been designed by a 15 year old high school student who has just discovered photoshop and a free icon pack. The entire icon set is rubbish – there’s no fixed color palette, and it’s basically a free for all.
After sitting around and using Brackets to develop a few sites, I decided to switch back to Sublime Text to see what I had missed while I was gone.
TLDR; Both Atom and Brackets have huge performance issues. I partly blame this on the fact that they are both based on new technology, and I also blame this on “over” doing it. Seriously, Atom is just so full of features it’s completely ridiculous. Even after disabling a bunch of modules, the editor lags when highlighting source code, and has noticeable visual lag when switching tabs.
I get that web isn’t as fast as native, but seriously, a tabbed WebKit view shouldn’t be that slow.
Brackets is better, and has some great front-end features, but it also suffers the same down fall.
I think I’ll come back and try the “web” technology editors in a couple of years.
Gitlab is great, however, there’s a few issues I’ve found with it that tend to annoy me:
It’s written in Ruby.
It’s a resource hog.
It’s backup system is completely terrible.
Facing a resource cut-back on our work server, Gitlab had to go for our in house git service. While it did a great job for a long time, the resource usage had gotten out of control.
After some quick research online, we came across Gogs, which immediately appeared to be a fitting candidate.
It’s written in Go (compiled is always faster, right?), and although it’s still in early development, it’s fast. Really freakin’ fast.
Gitlab was averaging around 1GB of memory usage at all times (ONE WHOLE GIGABYTE!). After installing Gogs, getting all of our git repositories moved over, we’re averaging just under 50MB of memory usage. This is a performance increase of ~20 times.
To keep things civilized, we’ve configured apache2 with mod_proxy to pass traffic between the browser and the service, allowing us to tighten down security for sensitive projects.