A week before my annual subscription of CrashPlan would expire I got an e-mail informing me that the CrashPlan for Home service was discontinued. My subscription was extended by 60 days to give me enough time to find another service. I’ve used it for a couple of years and have been quite happy with it, except maybe for the micro stuttering I experienced. It had the possibility to back up to a local external drive as well as online (offsite) with plenty of configurable options.
I have recently migrated my blog from WordPress to Hugo. That is, switching from a database-based web content management system with loads of themes, plugins and a large user base to a statically generated site with no server-side logic and a small feature set where I must build most things myself. The switch was by no means necessary, I had cheap hosting at a web hotel I will still use for other sites after the migration, speed was good with WP Super Cache and so on.
As I have worked more and more with CSS during the last year, both at work and with an updated version of this blog, I have come to the following conclusions regarding the Sass vs SCSS syntax. SCSS is the obvious default choice as it’s a more natural extension of CSS and that you can simply rename an existing .css file. In a team with several developers focused more on server-side, it’s usually easier to explain SCSS than Sass syntax.
I recently started to look at migrating this blog from WordPress to a static site engine. Hugo got my attention and I decided to try it out. One thing I have in WordPress is a tag cloud. I couldn’t find an example of how to create one with varying font sizes in Hugo, so I tried creating my own. Hugo discussion forum topics Weighted tag cloud and Tag Cloud talk about this.
For some time I have tried to figure out what’s been causing the micro stuttering I’ve experienced on my Windows 10 machine. Under moderate load applications have stopped responding for short periods of time, most obvious is audio playback where an unpleasant sound has interrupted playback. I could not see any correlation between this behaviour and a specific application, high CPU, disk or memory utilisation. My machine is a desktop computer I have built myself from parts, so I thought I might have made some bad decision regarding hardware compatibility.