For a while now I’ve had a Spotify Premium account, and since I told myself it was an experiment which I would then subsequently review, I really ought to actually do that rather than just letting it roll over and over each month.
I assume most of you are familiar with Spotify; if you’re not, then where the hell have you been the last year? It’s pretty much ubiquitous now.
Anyways, Spotify Premium is £9.99 a month, and that entitles you to higher quality music, offline mode, and use on mobile devices, like the iPhone. A full comparison of the different types of account is available on the Spotify website. The main thing that drew me to paying for premium was the use on mobile devices, like my iPhone, and I have used it pretty extensively.
And, based on that experience, I think I’m going to stop paying for it.
There’s a few reasons for this: the catalogue on Spotify isn’t as extensive I would like, and has a really large number of omissions, the software is occasionally unstable, etc. but the major one is mostly a strictly human limitation. I found myself just listening to the same set of music over and over, or I was undecided about what I actually wanted to listen to on any particular day, and Spotify just isn’t geared up to make it easy to browse to find something you want. The tools available for finding entirely new music on Spotify aren’t really very wonderful, either.
What I could do instead with my £10 is just buy a new album (or two) every month, add it to my collection, and then use tools like Genius playlists on the iPhone to listen to the whole damn lot in nicely selected chunks, which I find a really satisfying way of consuming music. This plan also has the advantage that I get to keep all this music if I every subsequently decide to stop paying monthly.
Anyways, I haven’t made any final decisions yet, so I’d be very interested to see what other people think about this, any tips/tricks or perspectives to share would be great.
(Coming up soon: a series of posts about my holiday to Ireland, and hopefully just more posts in general…)
As those of you who follow me on Twitter will know, I took the plunge and bought myself an iPad, as a kind of post-exams, post-degree celebratory splurge.
I have to say, so far I’m really rather enjoying it. It feels like this slab of glass and metal has just arrived from the future; it has this sense of violating usual expectations simply by existing.
The screen is glossy and beautiful, and it feels dense and sturdy. It’s heavier than you’d initially expect, but certainly not uncomfortably so. I’m not exactly a bulgingly muscular he-man, but I don’t find it uncomfortable to hold. They’re not wrong about the keyboard being large, it’s actually pretty comfortable to type on with the iPad in your lap, and you can get a pretty respectable typing speed with a little practice.
Pages load fast, browsing is fluid, and video on sites like the iPlayer work great. I started watching a Bettany Hughes documentary on Atlantis earlier on here, and it was a very pleasant experience. YouTube videos too look great, and I just last night found a service (although I now remember being told about it by Will Otter) called TV Catchup that allows me to stream live TV directly to my iPad, which is pretty cool.
As apps go, iPhone applications look flat-out ridiculous on the iPad. There’s not really a way around that one. They run, but you have the choice of running them at normal size, isolated in the middle of your display, or blown-up to fullscreen where they really just look appalling, pixellated, only having the iPhone keyboard rather than the superior iPad one, etc. You’ll want to use dedicated iPad apps wherever possible.
The catalogue of available iPad apps is comparatively smaller than its iPhone stablemate but there are already some pretty impressive apps available, and the number will only increase as more developers make iPad optimised versions of their existing apps. For instance the brilliant Google Reader client for the iPhone Reeder should be releasing and iPad version soon, and I can only hope that the Twitter for iPhone app formerly known as Tweetie will too receive an iPad version.
The in-built apps all look and work great, and one thing that surprised me was that even on the wifi-only model, location still seems to work fairly accurately, if not pin-point. I thought there was no GPS hardware, so I suppose it’s doing a trick using wifi hotspots to figure out my location. Whatever it’s doing, that’s quite cool.
I have a feeling that i’m going to change my habits quite a bit having this. I’ve already been tempted to impulse-purchase a movie from iTunes, and the iBook store would look terribly appealing if I didn’t already have a backlog of physical books (currently going through Neverwhere by Neil Gaiman) and I can see a lot of sitting in bed, browsing, tweeting and reading email in my future. Apart from high-powered hard-core gaming and writing code, there isn’t a huge amount of reason to go turn on my PC any more.
Anyways, I really like it, so there. This post was entirely written on the iPad.
So Google are in a bit of trouble because they captured a bunch of data from open wifi access points using their Street View cars.
Personally, I’m going to apply Hanlon’s razor to this: “Never attribute to malice that which can be adequately explained by stupidity.”
Google were collecting wifi data for the purposes of performing rough geolocation without the aid of a GPS module; if you collect the approximate position of a wifi access point (identified by its SSID and MAC address), then you can later calculate the location of a mobile device by cross-referencing with what wifi access points it can see. This is perfectly legitimate — all this data was being broadcast in the clear into public areas, it’s not personally identifiable, and Google were never going to disclose it directly anyway; only the results obtained from the use of the data.
The contentious bit is that they hoovered up payload data as well as just SSIDs and MACs. This means emails, web pages, downloads etc. etc. This isn’t too horrendous as anything actually important and sensitive e.g. financial stuff, is encrypted at the transport layer by SSL anyway. The collected data could potentially be compromising and embarrassing however, and it is legally very dubious to collect and store.
Given that it’s a PR disaster and potentially illegal, I think the most plausible explanation here is cock-up. Somebody on the Street View team got sloppy and used some code from another part of the company without asking too many questions about what that code did, over and above what they were going to be using it for; said guy is now probably getting one hell of a bollocking.
Apple and Adobe have been having a rather public tiff about the use of Adobe’s Flash on Apple’s mobile platforms, the phenomenally successful iPhone and iPad platforms. I’m going to have to split my response to this into two logical parts:
1. The Web
Flash is predominantly used as a container for video content, Flash-based games, and the occasional little widget. Almost every other use is a disaster; I’m sure we all have horror stories of terrible Flash-based websites.
Apple’s argument in this space is one I completely agree with: letting one company, with one proprietary implementation, control several important classes of web application is just wrong. Emerging standards like HTML5 video and canvas tags, and support for them in all the major browsers (Chrome/Safari, Firefox, IE9) mean that we have no need to stick to Flash. Even if we were to assume that Flash was high-quality, secure, performant, and stable, which it isn’t, letting it have total control of web video would be an incredibly bad idea. The sooner it dies a miserable death, the better for all of us.
2. For The Writing of Cross-Platform Apps
This one is somewhat more of a grey area.
First off, let’s be honest; Flash doesn’t help you build cross-platform apps. It helps you write apps that run on Adobe’s platform. They want you to write Flash-based apps for the same reason that Microsoft wants you to write Windows apps, or Apple wants you to write iPhone OS apps, or Valve wants people to use the Steamworks APIs: they want you locked to their platform, for their own business reasons. There isn’t any altruism here, no matter how much Adobe wants to play the martyr.
This is why Apple is refusing to let apps which target Adobe’s platform to run on their OS. Adobe are making a power-play to subvert Apple on their own platform, and Apple are rightly telling them to go fuck themselves. It’s not an unreasonable position, even from a user’s perspective. One of the reasons that Windows is a cluster-fuck is that fundamentally Microsoft lost control; they need to keep backwards compatibility with almost every Windows app ever written, even the ones that don’t play by the rules and call undocumented APIs in broken ways. That’s a millstone around their neck, preventing them from ever moving quickly. That situation is good for nobody; it hurts application stability, and it hurts innovation.
On the other hand, Apple are keeping control with an iron fist, in a fairly velvety (albeit thin) glove. Call undocumented APIs, don’t natively target Apple APIs, you get bounced out. On the other hand, it means Apple can keep nimble. They know that because all their app developers are playing by the rules, they can change things rapidly. Change CPU architectures? Boom, most apps will just recompile without needing changes. Stick a third-party toolchain in there, and you get unpredictable effects; every app using that third-party system could stop working. What if Apple want to add new features? If Apple exposes a new API, native apps can start consuming that API straight away. They don’t have to wait for a third-party platform to figure a way to pass through that API, if they ever do. They don’t have to worry about developers only targeting the minimum common feature set.
It’s a Faustian pact. Nobody is denying that. If you don’t like Apple’s strategy, you don’t have to buy an iPhone OS device.
For the moment, I’m happy with the trade-off. When I decide on my next phone, you bet I’m going to look at Android. But I’m happy right now, and I quite want an iPad…
Anyways, if you really want to write cross-platform code, you do it the same way we’ve always done it. Write core code in C++, staying agnostic as possible to the real environment you’re running in. C++ pretty much works everywhere. Hooray for open standards! Also, on another note, I also think that half the time the FSF is full of shit. Or to be less inflammatory, they’re so committed to their ideology that they’re blind to reality. But that’s a story for another day.
I’m about to express an unpopular opinion, so I’m just going to come out and say it: I really want an iPad.
Yes, yes, I know, early adopters always get screwed, it’s locked down, doesn’t multitask, there’s no camera, there’s no Flash, etc. etc.
Sorry, I just don’t care. It’s thin, it’s light, it’s a goddamned multi-touch tablet that’s going to have awesome third-party app support on launch (not only running legacy iPhone apps, but I bet there are going to be dedicated iPad versions of the best apps, e.g. Tweetie) and with a UX that’s pretty much second to none.
The web-browsing experience on it looks phenomenal. I already browse a lot on my iPhone, and being able to do the same on a screen that size? That’s the stuff tech dreams are made of. I’ve been wanting a device like this for over a decade, and now it’s here I’m not going to get sniffy because it doesn’t have a camera. Can you even imagine taking a photo with an iPad? It’d be horrible!
Honestly, I can see something like the iPad quickly becoming my go-to computing device. Need to look something up on Wikipedia? Want to book some train tickets? Quickly checking email? Want to show a friend a YouTube video? You bet you’ll be reaching for an iPad rather than trudging to a desktop or even a laptop computer. It’ll also be great for stuff like iPlayer, Facebook, Twitter… The experience on offer here is already worth the price of entry, no matter what features they’ll put in the second gen.
The one thing that seems like a missed opportunity with the iPad is that even if you get the 3G version, which presumably has all necessary radio-gubbins, it doesn’t support making phone calls or sending SMS messages.
Now, I can almost understand the justification for not supporting phone calls; there’s a real risk of looking somewhat like a 21st Century Trigger-Happy TV sketch, holding a giant iPhone up to your ear.
That problem could be entirely avoided though if it was mandatory to use some kind of hands-free kit to make calls.
The perfect scenario would be Bluetooth; your iPad could sit in your bag, month-long standby life only somewhat curtailed by being connected permanently to a phone network with the Bluetooth radio powered up. All the necessary interaction with the iPad required to make and receive calls could be made wirelessly via a Bluetooth headset. Heck, it would finally validate the existence of the bloody things.
Then I wouldn’t need an iPhone any more; the only time I’d miss it would be those times when I really need portability, like looking at a map while walking about on foot – mostly using iPhone apps while walking is a bad idea anyway (not that’s stopped me walking and tweeting, I might add). This is entirely counteracted by the much better battery life and superior usability afforded by the larger screen.
It seems like such a good idea I’m surprised they haven’t done it.
As is customary amongst our people, I am going to tell you what it is I think about stuff that’s been going on.
On Wednesday, Apple announced, to the surprise of absolutely nobody, that they were going to release a new tablet computer, monikered the iPad.
Gallons of ink and… what the fuck is the collective noun for pixels? I mean, you have a murder of crows, a parliament of rooks, a school of fish, a clutch of eggs… regardless, a lot of pixels have gone into describing every nook and cranny of the thing, so there’s no need to re-hash it; I always find that Engadget does a good job of coverage.
The real question is: is the iPad a Good Thing, or a Bad Thing?
I must confess that my initial thought process was, “Oh, it’s a giant iPod Touch. Who cares?” The iPhone OS is limited in a whole bunch of ways that are annoying if you’re used to desktop computers: there’s no filesystem, no multitasking, you have to get all your applications through the App Store, etc. and I felt that was just too limiting for a device that size. I also had ergonomic concerns, is it good for typing, for instance?
Then I sat down and watched the keynote video, watched the thing in action.
And I just can’t be cynical. I’ve wanted a device like this for probably more than a decade. And it’s better than the dream could ever be.
The iWork apps on there were, oddly, what finally convinced me. If you pair it with a USB keyboard, this becomes a practical work machine. It’s not a toy, it’s not a joke, it’s a perfectly-crafted touch device in a way you could never get by retrofitting multitouch into an existing OS, because every aspect of the experience is geared towards interacting with it with your hands. It’s utterly marvellous.
People say that it’s just a bigger iPod Touch. And it is, they’re not wrong. But then a Blu-Ray is just a DVD with more pixels. A Core 2 Quad is just a Duo with 2 extra cores. Heck, it’s really just a faster 486! The step up in experience that the simple doubling of the dimensions provides for is just going to be an order-of-magnitude better. Saying it’s “just” a bigger iPod Touch is like saying a Microsoft Surface table is just a bigger iPod Touch. The very nature of the form-factor makes it different.
So yeh, I’m very excited to head down to the Apple Store in 2 months and have a go at holding one in my hands. I might even go crazy and buy one, like a big sucker buying a 1st gen product.
There are niggles; it should be able to run at least one app in the background. Honestly, that’s all I need, or want. One background app for something like Spotify, and one foreground app to actually work in. The second thing is, they need to loosen App Store approval guidelines. There’s only one route to get software onto it, so it needs to not suck.
As far as Flash goes, I really don’t care. HTML5 Video and Canvas are going to wash it away, and the lack of support for Flash in the iPhone ecosystem is going to hurt Flash, not anybody else. Adobe looks pretty scared.
Still probably not ever going to get a Mac, though.
Update: Hey Reddit! This post has much nastier things to say about Ubuntu than the one below, so I think you’ll like it more. No, I’m not a Microsoft astroturfer. Wish I was though, I wouldn’t mind the money. Honestly, I want to like Ubuntu / Linux in general. This is why I tried Ubuntu again after it sucking the first time, and why I bought an Eee PC running a Xandros variant without even considering putting XP on it. But you guys don’t make it easy.
As anyone who follows my Twitter feed will know, I’ve recently been trying to install Ubuntu on my desktop.
On the whole it’s not that painful, the LiveCD lets you get a feel for the system, the installation is mostly painless even if you want to dual-boot etc, the interface is clean and easy to use, almost everything you’d ever want is already installed and almost anything else is available from the package manager. It’s great when it works. Really great.
The trouble is, often it doesn’t. For example the wireless card on this machine seems to have issues. Sometimes it won’t connect to a wireless network, sometimes it totally hangs the machine. The solution to this seems to be to dive in head-first into config files and the command-line, rip out the provided open source driver, and whack in a layer that will let me use a Windows driver.
My first attempt to do this just disabled wireless on the machine entirely, which wasn’t a forward step. I was honestly quite lucky to get it back to where I started from.
Software support can also sometimes be iffy. Stuff that should be simple like Adobe Air seemingly requires a trip through the terminal to convince to work. Another rather significant downside is that a lot of applications you’re used to using don’t have versions for Linux. You can use WINE to get Windows applications working, mostly, but it’s not an ideal state of affairs. And you can forget about playing games; support is even more dire than Mac gaming. That is unless you once again want to press WINE into service; frankly though it feels slightly iffy running Spotify, let alone TF2.
So my point here is three-fold:
- Hardware support is patchy.
- Proprietary software can be hard to get working / unavailable.
- If something goes wrong, it requires a lot of scary stuff (command-line, etc.) to fix.
See, I’m sure that if I had a working machine and a few months I’d start to learn the Linux-fu necessary to deal with this, but it’s just a pain if something as essential as Wi-Fi doesn’t just work, or if you can’t play your favourite games.
They’ve got a long way to go with hardware support, and it’s going to be an uphill battle every step of the way. There’s a lot of hardware manufacturers who aren’t going to provide Linux drivers, and there’s a dogmatic craziness in the Linux world that THOU SHALT NOT distribute non-free drivers with your distribution, which means that nobody just provides Windows drivers, or makes it easy to get Windows drivers. It’s totally daft, and it’s not helped by nutjobs like Richard Stallman. I guess you can put me into the camp who doesn’t like the GPL. Give me the BSD license any day.
The software difficulties are as equally hard to overcome; you’d have to deal with the horrible Balkanisation of the Linux distros for one thing so that people would have something simple to compile binaries against. Idealism isn’t going to get people to give away the source code to everything.
However, there’s certainly a market for Ubuntu / Linux systems where you can be sure of the hardware configuration and fix all the problems in advance. This means that something like eeebuntu works really rather well, and is supported rather better than Asus managed to support the Eee themselves. It’s a pleasure to use, and makes me see myself using my Eee a lot more in the future.
Similarly, if all the software you could ever want, literally, is encompassed by the repositories of your chosen distro, then it’s also a very comfortable experience where you can be reasonably sure that everything will just work, which is literally the ideal consumer experience.
So, if you lie within some narrow definition of “consumer” then Ubuntu is going to be perfect for you. If you lie just a little to the edges, it’s going to suck. There’s really no middle ground between “idealised consumer” and “pretty hardcore techie”. I guess that’s why they’re going to carry on working with it. If they can expand that consumer window, this could be heading somewhere.
This blog is licensed under a Creative Commons Attribution-Non-Commercial 2.0 UK: England & Wales License.
© aiusepsi.co.uk 2010