One of the computers I was interested in at the beginning of this yearwas the Surface Pro 6 from Microsoft. I had owned a Surface Pro 3 in the past and was very happy with it. But, as mentioned in a previous article, I had noticed something like a moiré pattern on the screen when white background was displayed. It wasn’t as pronounced on the Surface Pro as it was on a lower resolution HP notebook, but it was there, and I was afraid it would bother me.
I managed to get my hands on a Surface Pro 6 base model with a Signature Type Cover in Alcantara and used it as my main computer for about a week instead of my MacBook Pro.
Guess what: it didn’t bother me, and I could have saved a lot of money compared to the MacBook Pro. But that’s only part of the story.
With the release of the Google Pixel 3a I once again started thinking about what I want in a smartphone. As a reminder, the last time I was pondering the purchase of one I was musing of tall phones, curved displays and notches. I am not in the market for a new phone right now as my iPhone 8 is more than capable of fulfilling my needs. But, with the recent launch of the Pixel 3a I wished that this device had already existed a year ago because it is basically the perfect phone for me. And I also wish Google would get back into the market of less expensive phones with the latest and greatest hardware as was the case with the Nexus line.
As discussed in a recent blog post, I was in the market for a laptop. Several days after I had written about that topic and spent countless hours researching pros and cons, I had made the decision and went out to buy one. As the title suggests, it resulted in the most expensive product of the three options I was looking at and I’m here to write about it. This, however, is not the review as it would clearly blow up this piece. I’ll leave that for another day (I have written >1000 words already *tease*). In this blog post I’ll be explaining myself. Why I went with the MacBook Pro over the much more affordable and better equipped non-Mac laptops.
If you are a user of any form of computer and care one bit about your sanity, then you probably have a backup strategy. Otherwise, if all hell breaks loose and your whole computer burns to ash or the hard drive melts to a heap of metal, turning it into an ugly door stop, you’ll likely be kinda angry, maybe slightly pissed, your pulse most definitely at 180, that you’ve lost all your data. I’d certainly be, especially about all my pictures of all the festivals and places I’ve been to.
(And maybe some family 😅)
But, to be honest, I’ve been a bit lazy about backups for some time now. I do have copies of all my important files, but that’s not a backup. It’s a copy. A backup lets you go back in time and get an older version of a file or folder, not just the most recent one that has been synced.
So why is it, that I’m not as diligent as I should be? There are a few factors in that equation. It’s laziness for one, knowledge that I do have at least one copy, the fact that I haven’t had any data loss so far and stinginess. Why the latter? Up until now, being a Windows user (not any more though, on my main machine), I was relying on Acronis True Image, a commercial backup software. However, the version that I own – 2014, I think – stopped being reliable in one of the past Windows 10 versions. I simply don’t want to spend the money any more.
I’m not here to tell you that I have changed my mind on that. No. I’m, of course, coding my own solution. Why wouldn’t I? Everything is done multiple times in the Open Source community.
As an avid listener of Windows Weekly I often hear discussions between Paul Thurrott, Mary Joe Foley and Leo Laporte about Microsoft’s Fluent Design. Microsoft continues to evolve the visual language of Windows and thus it’s a regular topic on one of my favorite podcasts. I’ve been noticing it here and there myself, mainly in system dialogs, but I’ve never really paid any attention because none of the applications I use on a regular basis make use of it – and currently I’m rather happy about that fact. Just recently though, I was struck by one effect in particular and that was the spark that got this blog post going. To be honest, in most cases where I notice these Fluent Design elements I think of them as rendering bugs. Like sometimes in games, when the graphics driver is not yet optimized, or a badly programmed game engine draws odd pictures sometimes, flaws in an otherwise normal picture. I have a few examples to show to you.
This is a rant about modern smartphone design. I’ve had a few ideas in my head for some time, since MWC 2018 in fact, but never bothered to write them down as it was only focused on this notch thing that keeps on spreading. However, recently my sister’s phone died – thanks for the boot loop issues LG (it was my Nexus 5X that I passed on to her) – and so I helped her searching for a suitable replacement.
Although there are plenty smartphone makers out there, our go-to list wasn’t very long. For one, we had ruled out LG from the start. It seems that the Nexus 5X wasn’t the only one with recurring hardware defects. The next ones that didn’t make it to the list were basically all Chinese manufacturers like Huawei, Honor, ZTE or Xiaomi. I understand that they make very good handsets, especially Huawei has upped their game, but I do have my doubts regarding software updates. The last time I had read about the Android update situation sometime last year, these companies didn’t have the best track record (I don’t have the link to the website anymore, sorry). In fact, just throwing it out there, some Android phone manufacturers even lie about the patch level of their firmware.
What started out as a reasonable decision at the beginning of 2014 now reached its climax with the Surface Pro 3: switching away from Apple, in every regard, and move to the Microsoft platform. First the PC, then the phone and lastly the tablet. Since having a Windows based PC is nothing unusual (although I might be one of the few that actually came to like Windows 8 – just as I was one of the few that liked Vista over XP; what does that say about me?) and the Surface is still too new to write about it in any meaningful way, that only leaves us with the phone. Read More »