Larry Page on privacy

Google CEO Larry Page on privacy issues:

I'm not trying to minimize the issues. For me, I'm so excited about the possibilities to improve things for people, my worry would be the opposite. We get so worried about these things that we don't get the benefits. I think that's what's happened in health care. We've decided, through regulation largely, that data is so locked up that it can't be used to benefit people very well.

Right now we don't data-mine health care data. If we did we'd probably save 100,000 lives next year. I'm very worried that the media and governments will try to stoke the people's fears and we'll end up in a state where we could benefit a lot of people but we re not able to do that. That's the likely outcome.

The problem is not that people aren't open to the possible benefits from information gleamed from large piles of data. No, the problem is that both governments and companies alike have a history of abusing and/or leaking this data. In other words, the people's skepticism is entirely the industry's own fault.

Introspection, Mr. Page.

Where KDE is going

This article explores where the KDE community currently stands and where it is going. Frameworks, Plasma, KDE e.V., Qt5, KDE Free Qt Foundation, QtAddons - you heard some of these terms and want to know what all the fuss is about? A set of articles on the Dot aims to bring some clarity in the changes and constants of the KDE community in 2014 and further. This is the first article, diving into the technical side of things: Plasma, applications and libraries.

An update on where KDE stands today.

Google unveils Android L, new design language

So, the Google I/O keynote just finished, so I guess it's time to start summarising the most important announcements so we can go on to discuss them to death. Google announced a lot today - and most of it focused on Android. They detailed the next version of Android, dubbed the L release, which brings biggest visual overhaul of the platform since Honeycomb.

Google calls it Material Design, and it covers every aspect from Google - from Android to web. Material Design covers both how the user interface looks and how it behaves - with entirely new animations, dynamic shadows, and Z-depth. It is accompanied by loads of new APIs - both on Android and for the web - to make all these new transitions and Z-depth as easy as possible to code, and to ensure it always runs at 60 FPS (both on Android and on the web). Material Design covers all screen sizes - from round watches to big televisions.

There's a stylised video and a website laden with designer talk, and The Verge has the Android screenshots to show it off. Still images don't do the subtle animations and transitions any justice, but as you can see, if you've used Google Now you already have a very basic idea of where Google is going with this. The transitions, Z-depth, and dynamic shadows counter the lifelessness and coldness that are inherent to modern 'flat' design, making it feel livelier and warmer. It feels like it sits somewhere between the neon garishness of iOS 7/8 and the starkness of Metro.

While the focus was on the visual redesign, Android L will bring more to the table. One personal favourite of mine is a completely redesigned application switcher, which now resembles the card stack already in use by Chrome for Android, and displays Chrome tabs as individual applications. I've always found the current application switcher in Android to be cumbersome, and often very slow and choppy. This one looks very, very smooth on a Nexus 5.

Another huge change for Android is the definitive switch from Dalvik to ART, Android's new runtime. You've been able to use it for a while now, and I'm sure some of you already were, but Android L will run exclusively on ARt. It'll improve performance and all that, but it's also ready for 64bit, and supports ARM, x86, and MIPS. For developers - literally nothing changes. They won't have to change a single line of code to be ART-compatible.

Google showed off more features, such as battery life improvements and better notifications, but these were definitely the most prominent. The Android L SDK and developer images for the Nexus 5 and Nexus 7 (2013) will be available tomorrow, and the final release will take place in autumn. As for when you can get it on your phone - this is Android, so all bets are off, of course. Nexus devices will het it first, custom ROMs will follow shortly after that, and those of you running stock Samsung, HTC, etc. ROMs are at the OEM's mercy. HTC has promised to begin rolling out Android L to the HTC One flagships within 90 days after Google drops the code, but OEMs have broken these kinds of promises before.

Google also shed much more light on Android Wear, but there was little here we didn't already know. The LG and Samsung Android Wear devices will be available in Google Play starting today, but the much more awesome Moto 360 will only become available later this summer. Google also unveiled Android Auto (whatever) and Android TV (I'm sure it will take off this time). While the Moto 360 is quite interesting because of its round display and just how awesome it looks, the rest of these devices and platforms aren't particularly exciting to me. The good thing for developers is that all these platforms have SDKs available starting today, and a single APK can cover all of them.

Moving on to Chrome, Google dropped the inevitable bombshell: Android applications can now run in windows on Chrome OS. On top of that, there will be a lot of integration between Android and Chrome OS to bridge the gap between the two. The latter looks very similar to what Apple is doing with Yosemite and iOS 8, and is a very welcome addition to the Chrome OS platform. In fact, these two additions - especially Android applications on Chrome OS - actually make me interested in trying out Chrome OS.

The last announcement I want to touch upon is the first major announcement during the keynote: Android One. This is a new initiative in which Google creates a reference platform for entry-level devices that smaller OEMs in developing countries can use to build devices and sell them at prices below $100. These devices will ship with stock Android, but carriers can install localised applications. Luckily, though, users will be able to uninstall those. The cherry on top: Google will be solely responsible for updating these devices, meaning they will always be running the latest Android release.

This was a very interesting keynote, and especially the Android stuff consisted of solid, welcome improvements to the platform. I'm very excited about the new design, since we're not just looking at a coat of paint, but also new behaviour and the APIs and developer tools to back it up.

In 2012, Patrick Gibson wrote down a remark by one of his friends: "Google is getting better at design faster than Apple is getting better at web services". Now that we know what iOS 8 and Android L will look like - it sure looks like this remark has come full circle.

The death of the Urdu script

Way back in 2009, I wrote about a few specific cases in which computers led to (subtle) changes in the Dutch language. While the changes highlighted in that article were subtle and not particularly substantial, there are cases around the world where computing threatens much more than a few subtle, barely noticeable features of a language.

This article is a bit too politicised for my taste, but if you set that aside and focus on its linguistic and technological aspects, it's quite, quite fascinating.

Urdu is traditionally written in a Perso-Arabic script called nastaliq, a flowy and ornate and hanging script. But when rendered on the web and on smartphones and the entire gamut of digital devices at our disposal, Urdu is getting depicted in naskh, an angular and rather stodgy script that comes from Arabic. And those that don’t like it can go write in Western letters.

It'd be fantastic if Microsoft, Google, and Apple could include proper support for nastaliq into their products. It's one thing to see Dutch embrace a new method of displaying direct quotes under the influences of computers, but to see an entire form of script threatened is another.

Linux dominates supercomputers as never before

In the latest contest, not only did Linux dominate, but Linux showed that is slowly pushing out all its competitors. In the June 2014 Top 500 supercomputer list, the top open-source operating system set a new high with 485 systems out of the fastest 500 running Linux. In other words 97 percent of the fastest computers in the world are based on Linux.

With numbers like this, it's easy to forget that this project started with the words "just a hobby, won't be big and professional like gnu".

This hobby now dominates almost every field of computing - from mobile to supercomputing.

LG webOS TV emulator

Ever wanted to try LG's webOS for smart televisions, but without buying an LG TV? Fret not, as LG has the answer for you - there's an emulator in the SDK. You can download the SDK from here, and opt to only install the emulator. This is clearly geared towards developers, so there's not a whole lot you can do once you load up the emulator (a VirtualBox image), but for those of you interested in webOS development this is very interesting.

On Google Glass

Announced three weeks ago, the Diane Von Furstenberg accessory set offers five new frames and eight shades designed specifically for ladies. They're available for sale individually (i.e., separate from Glass, for existing Explorers) in the official online Glass store, and they're available with Glass on the luxury fashion site, Net-A-Porter.

I haven't spent a whole many words on Google Glass on OSNews thus far, partly because these things are quite expensive and only available to a select group of Americans.

Since this is as good a time as any to show my cards on Glass: I think Google has been botching, and continues to botch, the publicity around Glass in a spectacular way. They've been positioning it as a consumer product that you wear all the time, through all your daily activities, but I don't think that's where the real value of Glass (and technology like it) will come into its own.

Glass is geeky, and while that's not really a bad thing in my book (no matter what certain looks-obsessed bloggers say), it does limit the device's appeal. They can make it really small and unobtrusive, but that'll raise concerns regarding privacy even more than Glass already does today. On top of that, I simply doubt that most people have any need for Glass in their regular, day-to-day life.

No, I think the real value of Glass lies in an entirely different area Google seems to have been ignoring so far. It's a far less sexy area than the world of designer glasses and paragliders, but one that offers far, far more potential: 'traditional' workplaces. Construction. Road works. Law enforcement. The military. Farmers. Firefighters. Plumbers. Roofers. You name it. People who work with their hands in potentially dangerous environments, who can use the heads-up display for at-a-glance, crucial information while out in the field.

In short, I think Glass could be huge for people who do what I admiringly refer to as "real work" (to differentiate it from my own job, which comes down to sitting behind a desk translating crap). Sadly, Google seems to ignore this area, overflowing with potential, completely, continuing down its path of trying to make Google Glass hip and fashionable. I am much more interested in seeing what Glass can do for the kinds of professions I just mentioned.

Those traditional workers might not be VC-sexy, but I'm convinced they'd benefit a whole lot more from Glass than privileged tech bloggers, supermodels, and translators.

AnandTech’s Microsoft Surface Pro 3 review

The only review of the Surface Pro 3 that matters - as always, from AnandTech. They conclude:

Surface Pro 3 is easily the best design Microsoft has put forward. If you were intrigued by the previous designs, this is the first one that should really tempt you over. I was a fan of the original Surface Pro, and with Surface Pro 3 I think Microsoft has taken the hardware much closer to perfection. At this point the design needs more help on the software side than hardware, which is saying a lot for the Surface Pro hardware team. Personally I'd still rather carry a good notebook and a lightweight tablet, but if you are looking for a single device this is literally the only thing on the market that's worth considering. I don't know how big the professional productivity tablet market is, but it's a space that Microsoft seems to have almost exclusive reign over with its Surface line. With its latest iteration, Microsoft is serving that market better than ever.

Coincidentally, Microsoft is going for the tackle: you can trade in your MacBook Air and get up to $650 from Microsoft. Any takers? Anyone...?

Third early adopter Sailfish release for Nexus 4 released

Carsten Munk, chief research engineer at Jolla, announced the third 'Early Adopter Release' of Sailfish for the Nexus 4. Let me stress that this is very much still a work-in-progress, and your device may explode or kill hummingbirds. This release brings Sailfish for Nexus 4 up to par with version 1.0.7.16 that's current for Jolla phones.

This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see the release notes below. We are excited to get all of you properly included in the early stages of the project. Do note that this SailfishOS image is strictly for personal and non-commercial usage only.

If you have a spare Nexus 4 lying around, this might be a good moment to give Sailfish a try.

Supreme Court doesn’t understand software, and that’s a problem

The problem, at root, is that the courts are confused about the nature of software. The courts have repeatedly said that mathematical algorithms can't be patented. But many judges also seem to believe that some software is worthy of patent protection. The problem is that "software" and "mathematical algorithm" are two terms for the same thing. Until the courts understand that, the laws regarding software patents are going to be incoherent.

If you ever find yourself arguing with someone who supports software patents - just link to this article by Timothy B. Lee. An excellent and concise look at where software patents come from, the inability of courts to understand software, and why the Supreme Court of the United States seems so hesitant to reaffirm its own rulings about the intrinsic inability to patent software. Key passage:

One reason the courts might hesitate to do this is that it would be a big blow to the bottom lines of some of the biggest companies in America. Such a ruling would have invalidated thousands of dubious software patents held by trolls, but it also would have invalidated Amazon.com's infamous 1-click patent, the "data detectors" patent Apple used to sue Samsung, and Google's patent on its search ranking algorithm. Invalidating software patents would have wiped billions of dollars off the balance sheets of some of America's largest technology companies. The Supreme Court generally tries to avoid making waves, and those would have been some very big waves.

And there you have it. Large American technology companies want to have their cake and eat too - they supposedly support patent reform, but only reform that weakens the position of small players (which happens to include non-practicing entities) while strengthening their own positions.

Lee ends with the simile that I have used on numerous occasions in the past - one that perfectly sums up the inherent ridiculousness of patenting software:

The mathematical ideas in software, like the literary ideas in novels, are part of society's common intellectual heritage. Neither should be eligible for patent protection.

Full-motion video on a 1981 IBM PC

I gave a talk in 2007 that explained 8088 Corruption in detail, and in that talk I explained that displaying FMV using CGA in graphics mode would be impossible. This is because CGA graphics mode uses 8x the amount of video memory that 8088 Corruption was handling. Even a simple calculation assuming 24fps video reveals that the amount of data needing to be updated per second (24fps * 16KB = 384KB/s) is outside of the IBM PC's capability: CGA RAM can only be changed at a rate of 240KB/s, and most hard drives of the era operate at roughly 90KB/s. It sure felt impossible, so that's why I said it.

Then I thought about the problem for 7 years.

This is amazing. I also have no idea under which category to file this, but I settled for this one.

The Passport: BlackBerry’s strangest phone ever

BlackBerry is preparing to release what may be its weirdest smartphone ever. This year it's already launched the Z3, and soon that will be joined by the BlackBerry Classic - an obvious throwback to the company's glory days. But there's another product making its way through the pipeline as well, and it's a lot more blocky. BlackBerry is calling its third phone planned for fiscal year 2015 the Passport. We've never seen anything quite like it, and we'll let you decide whether that's a good or bad thing.

You know what? I kind of like this thing. It's crazy, unconventional, and it certainly has charm. I'm very curious if I will ever manage to get to handle one - I have yet to even see a BlackBerry 10 device to begin with, sadly.

The Supreme Court just mildly restricted software patents

The US Supreme Court has made it ever so slightly harder to patent software.

The patent claimed a method of hedging against counter-party risk, which is a fancy word for the risk that you make a deal with someone and later he doesn't uphold his end of the bargain. The Supreme Court unanimously held that you can't patent an abstract concept like this merely by stating that the hedging should be done on a computer. This kind of abstract patent is depressingly common in the software industry, and the CLS ruling will cause lower courts to take a harder look at them.

It's a small victory, but hey, I take whatever I can. Sadly, the SCOTUS also states that "many computer-implemented claims" are still eligible for patent protection, without actually explaining which claims. So, while appending "on a computer" to an obvious abstract concept does not make it patentable, the actual concept of patenting software is still very much allowed.

Even if the SCOTUS had completely abolished software patents, however, we still would have to deal with them for more than a decade - existing software patents would not magically vanish, and would still require lengthy and expensive court cases to be invalidated. Something bullies like Microsoft and Apple can afford easily, while many others cannot.

Sorry for not putting a smile on your face, but reality is reality. Sadly.

Nokia unveils Android launcher

Well, this is interesting. Nokia - and with that I mean the Nokia Microsoft did not buy, but which remained in Finland - has just unveiled its very own Android launcher.

At Nokia we've been thinking about ways to make smartphones easier to use, and there’s one problem we've thought about a lot; how to find stuff right when you need it. Today, people have an average of 48 apps on their phones, and that number is growing. When you add in contacts, web content, and tasks, it's easy to see how tricky our devices have become to use.

Finding the right app or contact - your Ace of Spades - constantly changes depending on where you are, what you're doing, and what time of day it is. We're introducing a pre-beta version of the Z Launcher to help change this.

They're only distributing it outside of the Play Store for now, and only to a limited set of devices, so it'll be hard to get your hands on it - this is clearly a case of testing the waters. Very interesting to see what this will grow into, or where this came from. Is this, perhaps, the remnant of what Nokia really wanted to do with Android?

Next major version of Android to set ART as default

Ever since we first saw ART appear alongside the release of Android 4.4 KitKat, we all knew that it would eventually replace the aging and relatively inefficient Dalvik runtime compiler. Well folks, the time is now upon us, as commits made late last night to the AOSP master branch show Dalvik getting the axe and ART being set as the default.

Should deliver some decent performance improvements. I tried switching to ART months ago but ran into problems with some applications not working properly. Has the situation improved? Are any of you using ART?

Amazon announces Fire Phone

At long last, Amazon.com has entered the mobile phone market, as expected. The impressively spec'ed "Fire Phone" stacks up with a 4.7" Gorilla Glass display, a 2.2Ghz CPU, 2GB of RAM, and a 13 Megapixel camera with f/2.0 aperture, certainly very competitive with today's Android flagships. Amazon has, quite wisely, included a number of hardware and software features and services that set it apart from the competition. The Fire Phone also boasts unlimited cloud storage of photos.

The Fire Phone has stereo speakers and a hardware camera button that help it stand out from the crowd. Prime customers? You all get the motherlode of content, so you'll be testing those speakers with access to a million songs recently made available via Amazon Prime Music. And if you're not a Prime member? Gotcha covered! You get one year of Prime for free (existing Prime users are extended a year).

Amazon has included their now-trademark Mayday Button, which provides 24/7 support. While this may seem unnecessary, take for example iOS 8, where there are literally dozens of new features to potentially confuse a user, or Android, where major version jumps change the entire UI of the phone. A dedicated support mechanism is a novel and likely welcome addition to the smart phone lineup.

A new service called Firefly that, much like Shazam, can not only listen, but "see." Optical recognition can help you identify (and subsequently purchase) books, TV shows, movies, games, music, and products. And the best part? There's an API for third parties to tie into it. This is going to be a very interesting feature.

Dynamic Perspective is billed by Amazon as "A custom-designed sensor system that responds to how you hold, view, and move your phone." It looks pretty amazing, and appears to give you not only standard gyroscopic control, but also a unique Z-axis subject distance, making for some very interesting effects and system responses to twisting, tilting, and peeking. You can read more about this feature and get the SDK on the Fire Phone developer's page.

The Fire Phone is available today for pre-order and is exclusive to AT&T, where it is free with AT&T Next, $199 on contract, or $649 off-contract.

Microsoft is paying bloggers to write about Internet Explorer

Why in the world is Microsoft (through an agency) trying pay bloggers to write about Internet Explorer? Do people still do this? And given my position on paid posts, why would they think I'd be willing to participate?

This is just layers of stupid.

Yes, people still do this. It's always hard to prove, but when you see the same (sometimes word-for-word) pro-Apple, pro-Microsoft, or pro-Google comments show up on multiple sites from different users in a timespan of a few hours or days, you know the coffee ain't pure.

Symbian once held ransom for millions of euros, and Nokia paid

Nokia paid millions of euros to a blackmailer to protect an encryption key of the Symbian phones. The extortion took place around the end of the year 2007.

The National Bureau of Investigation confirms that the case is still unsolved.

This is very interesting. Aside from the obvious illegal nature of it all, it's quite a clever crime, and the perpetrators were never caught. This makes me wonder if something similar could happen to the mobile operating systems of today.