Every year since the dawn of time someone has declared “it will be the year of the Linux desktop!” I don’t know if that will be true in 2025 for everyone, but it is for me. I’m now using Kubuntu exclusively on my home desktop after initially leaving Windows on as a dual boot. Once I realized I went 4 months without even starting Windows once, I knew it was safe to drop it.

Now, I have been exposed to Linux for a long time. I first set up a system in 1999 with Mandrake Linux (most recently called Mandriva), and loved it. I set up a server for development at work with Ubuntu Server in 2006 and since have used Linux servers at work almost exclusively. For a few years in the late 2000s I had an Ubuntu Desktop as my work machine.

In this post I want to share why I switched now and some “risk free” things you can explore if you are interested in switching away from Windows on your PC.

Welcome to the newly redesigned gillius.org, built with Jekyll and CSS by hand, based on some CSS resets I found online.

This has been a long time coming – I last moved to Movable Type Open Source edition in 2011 and the last major CSS design I did in 2006. I’ve been working on this for some time and there’s still more updates I’d like to make, but it’s far past time to cutover at this point.

Some of my very old content has been removed such as C++ and Allegro tutorials and articles from the late 90s and early 2000s which is very out-of-date.

Keep reading for more details and my reasons in picking Jekyll.

Since 2011, the forums have been read-only since there was not much activity except for spammers. I am cleaning up all unnecessary old software after this site was compromised via a PHP exploit in the past few days. As the domain has been read only for 10 years, I have decided to shut down forums.gillius.org.

I developed a Pointing Poker backend and frontend web application (GitHub Page) that works well enough for an internal team to use. It requires nodejs on the backend. The front end was built with React.

I built it because I was frustrated with the performance and reliability of public servers, and because I wanted to learn more how to use React beyond a trivial tutorial. It’s based on websockets, and all data is immediately replicated between all clients. There’s no code to reconnect if the websocket fails or if websockets don’t work, but it’s worked without a single flaw within an internal network, which is how I’ve used it.

Thanks to Mischa Berlin for a submission allowing random name generation!

Read on for more details on the implementation.

I made a project ("lunchbus") to play with Spring Boot + websockets + AngularJS 1.5 + Groovy + Redis. This may be interesting to those who are interested to see how these are set up. The project also has the configuration to run on Heroku.

The lunchbus app keeps track of who owes lunches and to whom, a list of people and places that can be selected, a button to randomly select a place, a chat functionality, and a demonstration of high-speed log output from backend. Persistence is provided by Redis. Due to how it uses Redis, it's just almost ready for horizontal scaling with multiple servers, for that time that you have over 100,000 people going to lunch with you. All that's needed for that is to integrate Spring Boot to Redis pubsub.

My goal is to learn Spring Boot and websockets primarily, and also to see what does an application relying solely on websockets look like and its strengths/weaknesses.