Slashdot Mirror

As tablets and computer-phones flood the market, the headlines read: "The Personal Computer is Dying." But they are only half true: an artifact of the PC is dying, but the essence of the PC revolution is closer to realization than ever before, while also being closer to loss than ever before.

Certainly one way to define the Personal Computer stems from the era of the IBM PC: a gray box with a monitor, mouse, and keyboard (or a laptop). But the idea of the Personal Computer dates back quite a while — back to Alan Kay's Dynabook, the Lisp Machine, etc.

The Apple Knowledge Navigator provided a vision of personal computing far more dynamic than that dull gray box. Although still a pale comparison, tablet and phone platforms are beginning to look awfully similar.

The essence of those pre-PC Personal Computers was that of the user controlling the device. You control the data, you control the software; the Personal Computer is a uniquely personal artifact that the user adapts to his own working style. One consequence of this is that creating is as easy (perhaps easier) as consuming content. Another nice side effect is that your data remains private by virtue of local storage.

In many ways, then, a tablet or phone comes significantly closer to a personal computer than that dull gray box under your desk. For example, on Android, the screen ceases to be a place to throw icons and becomes a rich canvas of widgets. Additionally, my phone fits into my pocket and is always there. Ubiquitous cellular coverage gives me access to my data from most anywhere. The touchscreen and interface conventions make direct manipulation shine in a way you just can't get from a screen two feet away on a desk.

And, those are just superficial improvements over the desktop. Albeit tied to proprietary services, Google's voice search and Siri are inching closer to the dream of personal Intelligent Agents reminding us all that our mothers called us earlier today and want us to pick up the birthday cake for the surprise party With a few taps I can search basically all of my data, not to mention the collective knowledge of mankind.

But the software running on these devices has a dark side. Want to access your music collection the go? You have to get it from Google Play. Want to have lightweight instant messaging? You have to use GTalk. Or take ebook readers (certainly personal devices): that book you just downloaded to your Kindle is DRMed and stuck there! That intelligent agent? Apple records everything you bark at her and can take her away at a moment's notice.

Furthermore, the software on these devices is geared almost exclusively toward content consumption. You can listen to music all day long, but don't try multi-track recording. That ebook reader is great for reading, but you can't scratch notes in the margins of any of your books or sit down with one and scrawl out your latest manuscript. Clearly, some of this is from the youth of these new systems, but it is distressing to see them geared first toward consumption (the Newton, for example, was geared from the start as a device for creation).

The "cloud" as implemented by Amazon, Google, Apple, et al. is a distinct threat to the personal computer. Loss of control over our own data is perhaps the worst part of the cloud. We're easily seduced by genuinely useful features like access to our contacts and music from any device without having to manually sync anything. It's certainly more convenient to purchase a digital movie on Amazon Prime than to hunt down a DVD, and Netflix is definitely nicer for most people than cable television. But when you buy a movie on Amazon, you don't really own it.

Underlying many of these cloud services (especially media-related ones) is Digital Restrictions Management. Whether it be the files themselves or the protocol used to transmit data, DRM is used to control what you can do with your data, restricting even what programs you can use to interact with seemingly neutral files. Worse, networked DRM services can and have led to lost data when it is no longer profitable for the company to run the verification servers.

The only copying that DRM discourages effectively is the sneakernet. And, given that the sneakernet has existed since recordable media has existed, it doesn't seem like the sneakernet is really much of a threat to creative business. I might lend a friend a CD (or even let her copy a few files), but just as I don't unwrap that CD and torrent it through The Pirate Bay, I'm not going to download a movie from Amazon and do the same. There's really no incentive to do so, for most people — most people pirate because that's what you have to do to get the media you want, not because you have a compulsive desire to share things with your closest 10,000 friends.

In order to prevent what is effectively sharing between actual friends, pushers of DRM-infected data want us to completely cede control of our own data!

And they have made people accept it: Steam, Netflix, and Amazon Prime are wildly popular. All of those services are great ideas, but all of them treat you as if you were a criminal.

Worse yet, the spread of Software-as-a-Service is returning us to the bad old days: that powerful PC in your pocket is quickly becoming no more than a glorified terminal. The open peer-to-peer network is being subverted from an enabler of collaboration never before seen into yet another scheme to tether users to proprietary, centralized services. And, as SaaS expands, privacy recedes. No longer is it implicit that your documents are yours alone; now you write and store things using Google Docs and have no expectation of privacy (legally), despite expecting privacy. Amazon knows what you read; Netflix knows what you watch; Google knows what you visit.

Control over the programs you run, and more importantly can write, is key to a personal computer being personal. And it seems absurd that that right might be taken away, but behold: the iPhone and soon Mac Store are these mythical walled gardens. You have to subvert your device to gain real control! And the natural path for Apple is to restrict Macs similarly to iOS devices.

And so we are all-too-near an Orwellian nightmare where vendors dictate what we can do with and how we can use our own data.

But what about the hardware itself? It could be argued that a device isn't really personal for some set of people if they can't change all of the software. Here too we see some promise, and some pitfalls.

The shift to tablet and phone hardware has meant a shift from x86 machines running PC BIOS to thousands of ARM boards, each with its own peculiar way of being programmed. Things you take for granted on x86, like being able to even boot, require custom code. And let's not even begin talking about all of the DSPs and co-processors. Vendors aren't always forthcoming with documentation for their boards, and, even worse, those that do port Linux to their hardware often blatantly violate the GPL and do not distribute kernel sources. This restricts the utility of perfectly fine hardware: often to the detriment of the user and to the benefit of the manufacturer.

Anyone who finds they can't upgrade to the latest version of Android because their vendor won't support it, and the community cannot support it because of non-free drivers, knows what losing control over their hardware is like (RIP HTC Dream).

It might seem like a minor setback ("I guess I have to buy a new phone"), but the lack of specifications or support marginalizes alternative operating systems. There's Meego, Tizen, Open webOS, Firefox OS, SHR, etc., but experimenting with them on your device is a non-starter. Imagine if the x86 were so closed (something we may not have to only imagine much longer): it is doubtful that GNU/Linux or the multitude "alternative" OSes would exist (Atheos, Haiku, L4Linux, even the Hurd). Ever more closed hardware is putting us into a position where two or three companies will dictate everything about the computing experience going forward, with no room for freethinking tinkerers to revolutionize how we interact with our devices.

We are staring at a bleak future, and living in a bleak present in some ways. But there is hope for the battle to be won by the Personal Computer instead of the Terminal.

The Internet is not yet merely glorified cable television. Hypertext, email, instant messaging, trivial file transfer, etc. have revolutionized how mankind communicates (understatement of the decade). Once upon a time the dream was that everyone would be a first-class netizen: your IP was publicly routeable and with a bit of know-how you had a server. Instead, thanks to grossly asymmetric pipes and heavy NATing, it is rare for any individual to run their own servers. Instead we turn to Google, Amazon, et al and cede control over our data.

But now broadband connections are spreading fast (I've gone from 100Kbit/s to 2Mbit/s upstream in three years just with basic service), IPv6 is really here, and software is being written to challenge the centralized "cloud" model being pushed on us from above.

We've had a few victories already: SMTP is still in use, XMPP is the dominant chat protocol (and IRC refuses to die), RSS/Atom aggregation decentralizes news, and the core network protocols are developed in the open.

But Google still controls Android, and myriad services control your data. Part of this is because they have easy client and server interfaces; sure you could run gallery2 and Wordpress on your own server, but I can just snap a photo on my phone and it's up on Facebook 40 seconds later (well, if their app worked, it would be).

Luckily, there are people working on making easy to use "cloud" services. In particular, ownCloud. ownCloud provides a framework for hosting and syncing data between your devices and sharing data with others. The important part is not so much the central server, but the clients they are writing. Eventually, it should be possible to e.g. replace the Google contact/mail/calendar sync and Google Drive, while adding these features to the desktop. Integration in KDE is already underway.

Imagine, instead of being tied to Google you could move the central server to the hosting provider of your wish (or pack up your data and move it to greener pastures if you're not running your own). And, perhaps more subtle (but the real liberation): Your data would be freely movable between all operating systems (interesting that you have to go through hoops to sync your GMail contacts with anything else, and Abandon All Hope Ye who wants to share between an Apple device and anything else). Additionally, the server is designed to respect your privacy (you can e.g. only store encrypted data server-side).

On the hardware side, projects like Firefox OS are very important: having a "mobile" Free Software OS developed in the open might be essential when the dominant open platforms are developed monolithically by corporations with no interest in protecting user control of data.

And then for developing the next generation of devices, folks like Rhombus Tech are pushing for the development of interchangeable CPU boards for embedded devices, and the FSF is expanding their focus to include open hardware.

There are two serious threats that would undermine any resistance: IPv4 exhaustion and draconian content policing. The former issue is technical and likely to solve itself: in the long run multi-level NAT would be too costly, switching hardware will be replaced as it is obsoleted, etc. The latter is political and represents the most serious threat of all. If we cannot communicate freely and the pipes are owned by the very organizations whose business interests will be harmed... we've already seen how brazen the current IP regime can be, and it will take vigilance on the part of many to prevent them from having their way.

Where will we be in ten years? If Google, Amazon, Apple, and Old Media get their way, in a new dark age of computing. Certainly, you'll have a fancy tablet and access to infinite entertainment. But you will own nothing. Sharing data will be controlled by a chosen few entities, the programs you can run or write will be limited in the name of security, and privacy will be dead.

History shows that personal computing survived despite Apple and Microsoft in the 80s and 90s. So, I'm hopeful that other forces will win: the forces of Free Culture and Free Software. If they succeed (or are at least not crushed), the future is much brighter: most content will be available DRM-free, users will control their computing environments, and the egalitarian promise of the Internet will be realized (in no small part thanks to IPv6).

First time accepted submitter yuriyg_ua writes "[The] semantic line interface may combine features of both command line and graphical interface, which would allow even more complex applications than we have seen before." The idea is that the layer underlying user interfaces should define the semantic relations between data enabling the UI to provide better contextual information. Kind of a modern version of the CLIM presentation system.

lamaditx writes "There is a good chance that you have heard about "Web 2.0" — the buzz-word coined by Tim O'Reilly in 2005. You will find several reviews of books about this topic on Slashdot. These cover mainly technical aspects of implementation whereas this book introduces the strategical thinking behind the whole Web 2.0 movement... Web 2.0 is so much more than the technology.' The table of contents is available from O'Reilly, together with a chapter preview. The book does not come with any extras but includes the usual free 45 days access to the book on Safari. When reading a book I usually flip through it quickly to get an impression for it, in this case there are three things which I noted right away." Keep reading for the rest of Adrian's review. Web 2.0: A Strategy Guide author Amy Shuen and Simon St. Laurent (editor) pages 266 publisher O'Reilly Media , Inc. rating 10 reviewer Adrian Lambeck ISBN 978-0-596-52996-3 summary Business thinking and strategies behind successful Web 2.0 implementations First, I was drawn by the the foreword by Tim O'Reilly. Since I have read his article about Web 2.0 back then I came to the conclusion that the strategy guide is a kind of successor. The next think I was looking at is information about the author. Amy Shuen concentrates on business models and teaches entrepreneurship, strategy, and venture finance on major business schools around the world. Amy is currently a Professor of Management Practice at the "China Europe International Business School" (CEIBS).

Secondly I noticed that there are a lot of footnotes on every page which reference other publications that fit the current topic. This is perfect if you want to drill into the details about a specific issue or lack some background knowledge.

The last thing I notice are the really big "End Notes" which spread across 40 pages and the bibliography which consists of 22 pages. This means that around a quarter of the book is additional information. I am pretty sure this fact is due to the academic roots of Amy Shuen and I think it is appropriate for this kind of guide. Actually this is what I expect from a guide — it should guide me through the topic and summarize the overall picture.

After flipping through the book I started reading it — and couldn't stop. I had to travel to Munich the other day — I boarded the plane with nothing else but the book and my boarding pass. I received the book on Thursday and finished reading it on Saturday.

Reading this book is fun for several reasons. I hate authors that put graphics into their books and don't provide you with additional information. That is not the case in this book, all the graphics are easily read (the only exception is a picture on page 5). Most graphics, functions, and screenshots are self explanatory. From my own experience I know it is not easy to find the right mixture between too much detail and too little.

Another important point are the numerous case studies in every chapter. Of course they do not include all information and details but they emphasize the theoretical point and provide you with a good feeling about the business case. Reading these kind of "historical" stories also adds some life to the book. Even though I have written a paper about Google's Page Rank algorithm and therefore a rough understanding of it, I learned many details about the competition between Google and GoTo (later known as Overture) that I did not know. It also teaches you that the effortless looking success of a company like Google involved tough times in the past. Running the Web 2.0 track is not always that easy as it looks like.

Talking about the big names: This book is interesting for anybody involved in a Web 2.0 (or escaping Web 1.0 ;-) ) environment no matter if you are working in a big, small, or start-up company. Amy stresses this point several times as she points out "Your business probably isn't Facebook, LinkedIn, or even something that looks much like them".

So how are you be able to transfer the knowledge you gained from the book to your own Web 2.0 concept? Amy to the rescue. Each chapter ends with a "Lessons Learned" section to summarize the most important points. After that she provides you with a section "Questions to Ask" which cover strategic and tactical issues with these tools at hand. The last chapter will also support you to "apply Web 2.0 strategic thinking to your business". Maybe you are writing a business plan or a project proposal to get your idea started. The last chapter will help.

In the end I would like to talk about the rating I am assigning to this book. I rated it as 10 which means it is "excellent" or one might call it a "classic work". I have not talked much about the content of the book because I did not want to provide you with a plain summary. I expect this book to become one of the "must-read" in business as well as technical classes since more and more business models will evolve in a Web 2.0 environment. Another reason is the well explained and easy to read writing style. Technical terminology is kept to a minimum thus not requiring a lot of prior knowledge.

Adrian Lambeck is a master student in "Information and Media Technologies" in Germany and thinks about starting his own (Web 2.0 ?) business.

You can purchase Web 2.0: A Strategy Guide from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Carsten Zerbst writes "The new Homepage off Tcl/Tk, the famous scripting language is now running at ScripticsThis new company lead by John Ousterhood is founded to take over the core developpment of Tcl from the Sunscript Division. The Website should be a standard repository for Tcl and the Plugin as well for the many extensions available. Tcl/Tk is one off the oldest success story of open software and a development model driven by the a central organistion assisted by many users. "