Skip to main content

3-years of Ubuntu MATE - Good and the bad

Many people are getting shocked to know that I'm using Ubuntu in my workplace. Linux/Ubuntu is more of an alien here as Windows 10 and Mac OSX is having good market here.



First of all, I'm a very happy Windows XP user. In XP, I used to do most of my JavaScript and PHP in Devl, the editor that our team has developed.

Reason for switching to Ubuntu MATE

Primary reason for switching to Ubuntu was, at one point of time PHP team stopped supporting Windows XP. So, we're left with few options: 1. Upgrade to Windows Vista, 2. Switch to Ubuntu.

We chose the second option to experiment it. One of the major challenges was choosing the right code editor and we chose VS Code.

Ubuntu MATE - Pros

Linux comes with lots of command line tools. I have started to do many tasks using these shell scripts and found very productive.

We switched from Google Chrome to Chromium for good.

Ubuntu MATE - Cons

We started with GNOME for desktop, but it was memory hungry and was not suitable for our old machines and so had to switch to MATE. MATE is great for memory and good when we compare with other desktops. But, the speed is still not good as compared to Windows XP--if we don't add at least 2-GB RAM.

Though we switched to Chromium and happy, few things like translate options won't work out of the box; will need manual steps to enable it.

But, the major challenge is the editor. VS Code is good, but being an Electron app, it is more of a memory hog. In my experiment, the only editor that is somewhat reasonable in performance is Pluma.

In Ubuntu, we have LibreOffice (previously, OpenOffice) and WPS Office as two alternatives for MS Office. But, neither of them are real alternatives for MS Office. If your work is heavily based on MS Office, unfortunately Ubuntu/Linux is not yet ready for that.

Of late, we're feeling the heat from 64-bit push. As we're in 32-bit, we can't use tools like docker that are only 64-bit.

Comments

Popular posts from this blog

NETELLER - Privacy and security design flaw

Yesterday, colleague of mine brought to my notice about a payment system called NETELLER and it's merchant API named NETELLER Direct API V4 . This NETELLER Direct API V4, helps the merchant to collect amount from users. It's simple--same just like early Authorize.net , along with the required amount you collect the user's id and password and post them to their API URL and they'll send you back with success or error codes in XML format. The major problem with these types of system is security and privacy --you lose both as you're forced to type your username and password in alien web page. If I remember right, this is was the case with Authorize.net and they changed their design to something like PayPal . The PayPal design is somewhat better as you never type or forced to type your username and password in other alien web pages. The alien merchant web page uses NETELLER Direct API V4 is forced to get user's NETELLER account and password. I'm much s...

Stampede and the "Dirty" "Dark" Crowd

Actor Ajith Kumar’s recent interview has sparked quite a few conversations on social media. The part that caught my attention, was his take on crowds. About 30 years ago, when I first joined a college in Madurai after growing up in other places, I experienced a few cultural shocks. Perhaps these weren’t unique to Madurai, but that’s where I first noticed them. One major thing that stood out was the behavior of crowds. For instance, if you suddenly see people rushing to board a bus, chances are there’s a pickpocket in action. During one of Madurai's annual festivals, I noticed some young men carrying water bags — not to distribute water, but to spill it on women, often on their chests. Shockingly, this was almost normalized; parents would quietly tolerate it to avoid public embarrassment, walking a little farther behind the crowd. When some women happened to witness this, they would just shoo the boys away instead of confronting them. The crowd, in such cases, became a kind of...

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...