I still have an original Pebble someplace, and to this day it was the only smartwatch that actually got calendaring “right”–its timeline view was an excellent bit of UX that Apple completely ignored (they even killed doing “time travel” with the crown recently, so it’s pretty much impossible to have a decent overview of your day at a glance).

It’s good to know bits of it live on, although realistically it is extremely unlikely to ever recover and come back as a commercial product, regardless of the brilliant engineering involved.

The Google event this week barely registered in my mind (not out of any bias, but simply because all the announcements felt very “meh”), but Ben Thompson’s post adds a little depth to it.

However, I can’t help but wonder if large tech companies are just blurring into essentially the same kind of unfocused, all-encompassing, uninspiring offerings.

There seems to be a gigantic void of creativity (let alone any actual meaning) in the tech industry these days, and I think that speaks a lot to the lack of impact FAANG’s initiatives have in real life (i.e., outside the tech hype circle).

Even though the Python 3.8 release is getting all the news coverage in the Python universe today, PyPy 7.2 is a lot more interesting to me since it has full 3.6 support and some of the fixes I’ve been waiting for.

I’ll be updating my runtime images when I can find the time.

I am definitely going to wait this one out. About half of the folk I know is actually considering waiting for the .2 minor release.

Update: there seems to be a chance of data loss in Mail.app, which is borderline criminal in terms of QA. I have no idea what Apple is doing to macOS in general other than killing it with a million paper cuts…

This is very cool, and a good (if not deep) overview of what you can do with the Pi 4 hardware.

Having built a few digital signage solutions atop the Pi (one of which entailed H.264 streaming to the original hardware and another which evolved into what is used yearly at Pixels Camp), the HEVC split display support is especially interesting to me, and I hope this surfaces someplace as a reusable solution.

This makes perfect sense, and I would expect a few more features to be retrofitted to current hardware–we’re well past the time when it would be even borderline defensible to tie new software features to new hardware when older hardware shares the same architecture and design constraints.

I wasn’t planning on upgrading until 13.1 anyway because I wanted to make sure I was running the same version on the iPad as well, but apparently that’s been moved up to the 24th, which is great news.

Even with Android Wear devices having had a variety of always on displays from the beginning, the Series 5 is a bit of a surprise in the way Apple decided to go with that feature, and probably the only thing announced yesterday that appeals to me.

The rest (other than TV+ pricing for the US and no OS release dates mentioned on stage) was pretty predictable, and by no means life-changing: My iPhone XS is fine, the new iPad is just an A10 (and is great in other aspects), etc. I am still on the fence regarding getting a Pro or something else, and there were no interesting updates in that regard.

Also, good thing the Series 3 watch is still on the lineup - that means it will still have a few more OS updates.

This has been in the cards for so long and there has been so much (often uninformed) discussion I’m actually surprised the FAQ has an entry titled “I didn’t hear anything about this till just now.”

I switched all my projects to Python 3 gradually (targeting 3.5, a little over a year ago), and it’s been truly painless. Having used it since 1.2, I can appreciate how far it’s come and how things have changed since (literally) the turn of the century.

It’s still my go-to programming language, and I’m looking forward to PyPy and Cython improvements in ARM - it will never be the fastest language on the planet (I look to plain C, Go and Java for that), but its ecosystem still gives me the most bang for the buck with the least hassle, and that, I think, is the real reason why it’s been so successful over the years.

An extraordinarily beefy review.

I like to keep tabs on Android (after all, I used to do custom builds of it for my own devices, and still fiddle with x86 builds now and then), but looking at this is like dipping into an alternate timeline – it looks enough like iOS to be familiar, and yet can do so much more even as its ecosystem, reference hardware and update policy all remain a broken mess.

And it’s been this way for so long that I don’t think even single-source reference hardware from a brand with actual global retail presence (and an end to Samsung-like pastiches) would be able to fix things now–or, indeed, ever.

(I have seen exactly zero Pixel phones in my neck of the woods over the past couple of years, excepting two Googlers I hang out with from time to time.)

Out of the rumor extravaganza that’s hit the news this week, this is the most interesting bit for me, since despite having bought an XS last year, the prospect of going back to a smaller, saner phone is vastly appealing. Of course, Apple doesnt care one whit what anyone thinks, but speculating about the bits that make most sense to us is a large part of the human condition, so there you have it.

As to the rest of the news regarding next week, I am actually surprised it took them this long to adopt the Pro moniker for the iPhone – it’s a coherent (for Apple) naming scheme that, at last, spans all their (major) product lines. And, of course, I’m quite interested in the rumors of an iPad Pro refresh, since I’ve held off upgrading my iPad mini 4 in order to see what would happen to the rest of the range.

But, overall, I don’t expect many surprises from Apple, either next week or next year. Unless we’re talking about a radical redesign of the MacBook keyboards, I’m not even likely to bother.

piku now has its own GitHub organization, after almost three years. It’s not as if I have any shortage of personal projects, but this one has become a bit more useful to other people than most (thanks largely to contributors like Chris McCormik), so I decided to take the time and split it off into a standalone thing.

It runs pretty much everywhere (any cloud, any kind of CPU) and can currently deploy Python, NodeJS and Java apps (as well as arbitrary binaries). Near-zero overhead, Heroku-like workflow, and just a smidgeon over 1000 lines of code (1087 right now), which means you can understand all of it in one sitting.

It also comes with comprehensive docs (which need cleaning up) and bootstrapping scripts, but most importantly it keeps saving me time whenever I need to deploy simple services, so I’d say it’s been time well spent.

I wish this had happened a little sooner (at least to save me the trouble of wrangling NodeJS a couple of weeks back), but it’s welcome nonetheless, especially with full Linux support tacked on.

There is also a durable Functions SDK in the works, so now I’ve got that to look forward to.

The commoditization of CI/CD is a thing these days, and I, for one, welcome our build automation overlords. Or, rather, more overlords.

This is becoming a very crowded market: I used GitLab CI since the very beginning, have a bunch of things in Travis (which I’ve been moving to Azure DevOps, namely my multi-architecture Docker pipelines), and everyone seems to be running Jenkins on-premise (it became the de facto standard, despite its temperamental nature and sharp edges)…

So for me the real issue these days is not whether you should use CI/CD or which tools to adopt, but whether you actually take advantage of it in your internal processes.

Also, I’m really curious as to what this means for the Azure DevOps free tier, (since this is actually running a fork of the same agents and appears to be running on Azure compute), but that’s anothet story.

An interesting read, and a timely reminder that there are a lot of traditional, background (almost legacy) services that can be exploited on any mobile device.

The Visual Voicemail bits were especially interesting to me, since I was involved in getting that to work at Vodafone and I always felt the entire thing was a bit of a hack (for which our voicemail provider - Comverse at the time, if I recall correctly - happily charged us an insane amount of money, but I digress).