Archive for the 'Linux' Category

Why you (probably) won't be using Firefox a while from now

Mozilla CEO John Lilly on the number of fast, capable browsers in the market:

“The world is a lot different from a year ago, and we have three brand new browsers and there is a lot more competition and as a result the users are getting a lot more technology…”

“… I think it is uncomfortable, because our rivals have 2-3 times the magnitude of people and resources, and they are relentless.”

The state of the browser market pretty much proves that it’s impossible for an open source project to remain a popular front-end application for too long.

A successful open source project will see one of two trends:

- Commercial entities, each with its own USP will pick, modify and integrate portions of the project into their own products. This is what’s happening with Firefox. (Chrome, according to Google, used ” components from Apple’s WebKit and Mozilla’s Firefox”). Firefox as an open source project is likely to thrive, but its best features and technology will probably find their way into more popular commercially-backed browsers [1].

- It will see widespread adoption, but on back-end IT infrastructure instead of the desktop. Linux and *BSD are examples of this. I guess this is because after a point, the marginal cost of polishing the UI is more than what developers are willing to bear, and that end users demand more. Regardless, the core functionality of such applications is on par with/often superior to commercial alternatives, so a combination of this + low price point makes them an attractive choice for back-end deployment [2].

[1] Android was a commercially-backed open source project (based on Linux kernel 2.6) from the beginning, so I guess we’ll treat it like Chrome.

[2] This isn’t a value judgement on the quality of open source products, or the viability of the open source development model itself. The past couple of decades do seem to have proved, though, that end-user open source applications are tough to build and sustain in their original form.

On reverse-engineering, patents and open source.

Bryan Cantrill, kernel engineer extraordinaire and co-author of Dtrace, blogged his thoughts about reverse-engineering and patents in the context of Linus moving the Linux kernel souce code mgmt system from BitKeeper.

I (like many engineers, I suspect) view reverse engineering as a Natural Right. That is, I believe that we are endowed with certain unalienable Rights, and that among these are Life, Liberty and the pursuit of Understanding how the hell something works (or doesn’t, as is frequently the case). Perhaps perversely to some, it is my strong belief in the right to reverse engineer that leads me to my equally strong belief in the responsibility of government to establish a system of patents: if you use my product, you have the right to take it apart and understand its inner workings, but I have the right to protect my intellectual property by patenting the novel mechanism that represents a non-obvious advance in the state of the art. That is, it should be the protection afforded by patents — and not the obfuscation inherent in a running system — that prevents the rip-off artists. My belief reflects the fact that nearly all applications of reverse engineering do not in any way violate anyone’s intellectual property — and the act itself and alone can never violate intellectual property.

Quite right. Unfortunately, software patents today are ridiculous – there’s an article every week or two on Slashdot about some extremely obvious idea being granted a patent. I think we’ve already reached the point where any piece of decent software inevitably violates some or the other software patent. Software patents have now become a tool for companies to muscle their way into, or keep their stranglehold on, existing markets, using the principle of Mutually Assured Litigation. You use a patented idea of mine that doesn’t make a difference to me, that’s fine – but if it’s any threat at all to my market position, I’ll sure as hell sue you. So we’re now walking through a legal minefield wherever we go. In addition, there isn’t too much use knowing how a particular piece of software (Bitkeeper in this case) works unless you can do anything with it. If, for instance, Tridge did find out how Bitkeeper worked, he wouldn’t have been able to do much with it. It’d only tell him how not to design a new source code management system, since the existing process’ been patented. So although in principle, reverse-engineering ought to be allowed for patented software, from a practical point of view, it really doesn’t mean too much.

BMC does, however, consider that point of view:

I believe strongly in reverse engineering in particular, but it plays an especially critical role in the development of software: in my experience, when developing a layer in the stack of software abstraction, you always need to understand at least one layer below you and you often need to understand at least one layer above you — and reverse engineering is often the primary means to achieve this understanding. More generally, software is usually reverse engineered to work around oversights or blunders, or to simply understand a software system sufficiently well to interoperate with it.

So reverse-engineering for the sake of developing software elsewhere in the software stack, or for the purpose of interoperability, ought to be allowed. It also enables better quality software (in terms of bugs being found, or better interfaces being suggested). Therefore, using the simple principle of “many eyeballs make bug-finding easier” (or equivalent) by Eric S. Raymond, software ought not to be closed-source in any case.

So we’re at a stage where software patents are important (even a necessary evil, perhaps) to preserve competitiveness and encourage participation (indeed, there are many startups whose entire existence depends upon a patent or two!). But we need to draw a line when patents are granted. All too often, one crucial aspect of a patent – novelty and non-obviousness – is simply overlooked. And availability of source (which, actually, obviates the need for reverse engineering) is a necessary (but not sufficient! ;-) precondition for high-quality software.

Beagle capers – help needed.

I’ve been trying to get Beagle up and running on my computer for a while now. There’s so much information on my hard disk, I’d love something like Google Desktop Search for Linux, and Beagle seems to be just what I need – and more.

The following is only for those who’ve had some experience in Beagle-related matters. The rest, come back later… I’ll come up with entries that make sense to you – I promise. Now, scram!

OK – with Beagle, as you know, things aren’t that simple. Beagle requires d-bus, an inotify-enabled kernel (now optional), and mono. I have all of those installed, and working fine:

dbus – version 0.23.4 (the latest one, 0.31, requires gtk+ 2.6, and I’m still running Gnome 2.6).
mono – version 1.0.6 for SUSE 9.2
kernel – an inotify-enabled 2.6.8 kernel.

I launch dbus with
$ eval `dbus-launch –auto-syntax`

Then, beagled
$ beagled –fg –debug

This connects to the dbus session just fine, and begins indexing all of my data. I now launch best, the nice GUI to beagle. That loads fine too.

The problem is when I type in a search query. If I search for “rahul”, for instance, here is what I get:

The query for rahul failed.
The session bus isn’t running. See http://beaglewiki.org/index.php/Installing%20Beagle for information on setting up a session bus.

I have no idea what the problem is now. Why best can’t seem to detect that a session bus is indeed running, fails me. Someone on Ubuntu’s wiki here had the same problem, but a reboot seemed to fix that for him. I’m not that lucky. :-(

Does anyone have a clue?

Notes on digital cameras and Linux.

The first thing I consider when buying any piece of hardware, is whether it’ll play well with Linux. Yeah if you’re a Linux user, you know the feeling. The “extra” research you need to put in. Thankfully, the rather expensive digital camera I bought last week works excellently with the SUSE Linux 9.2 Professional on my Thinkpad.

The first time I plugged it in, it was recognised as /dev/sda1 (where’d that come from?), and mounted under /media/usb-Sony-SonyDSC:0:0:0p1. I’d actually prefer a nice /media/camera or something similar. Anyways, from there on, I could use it like a normal folder – add, view, delete files. The only hitch was that to use the camera multiple times between reboots, you had to unmount it cleanly before disconnecting it – and that involved opening a terminal window and typing “sudo umount /dev/sda1″. Most inconvenient, if you ask me. In the “Computer” window on the GNOME desktop, an entry for “USB Hard Disk” would appear a short while after the camera was plugged in.

GTKam, a nice application for downloading and importing images from your digital camera, refused to recognise the camera. This was a pain – I didn’t want to go through the elaborate ritual of waiting for the camera to be automounted, navigate to a complicated drive path, more layers of folders beneath, and then drag and drop them into a folder in my home directory. No, sir – what I want is to plug in the camera, fire up gtkam, look at a preview of all the pictures in the device, and transfer them to my photos folder with a single click.

I observed that most of the Sony camera models listed in the gphoto database had PTP mode in brackets appended to the model numbers. I wondered if there was a “PTP mode” for my camera. A little poking around in the fat manual revealed that I could, indeed, enable PTP mode. And voila! The camera works fine! it doesn’t show up as /dev/sda1 anymore in the mount listings, and GTKam lists images like a charm! Of course, the camera’s recognised as a DSC-F707V, which it most definitely is NOT (it’s a DSC-W1), but hey – it works, and that’s all that matters! I wonder how things are for Windows users.

In a couple of days, I’ll post about digital photo management software for Linux.

On moving to a new Internet provider.

I moved to a new Internet provider today. These guys provide Internet connectivity via PPP over Ethernet. The same old story repeated itself:

Location: Dingy, cramped cableguy’s office. 6:30 PM.

Me: …so this connection of yours requires a connection tool?

Cocky ISP guy: Oh, yes, very attractive, animated wizard. We’ll only need to insert one driver, this raspppoe.inf. Sampat here (pointing to grubby, skinnny gum-chewing teenager) will guide you through the entire setup process! You don’t need to do a thing…

Me: So this thing is a Windows application? (redundant question, and I had no intention of allowing Sampat fifty feet near my apartment.)

CIG (with a look that said “Where’re you from – Mars?”): Well, yes… but all Windows versions! 95, 98, 2000, XP, NT, even Windows Server 2003! What do you have installed?

Me: SUSE Linux 9.2 Professional.

CIG: Ohh… Linux. (actually: “You #$^$#^&@%, why can’t you be normal?”)

Me: Yeah, but does your service have a web-based authentication interface? Or is there a Java-based client I can use? Then I won’t have a problem.

This conversation was already beginning to push the limits of his technical knowledge.

CIG: Umm… you want to take a look and find out for yourself? (actually: You $#%#$%&^&, why don’t you just go to ^%&^%&%*%$^ hell?)

I looked, and quickly concluded that this was PPP over Ethernet.

Me: OK. I guess I can handle this one. Just give me my user name and password, and I’ll get going. (I already had a LAN connection to the cableguy’s office, which would work.)

CIG: Sure! Cool! If you have any problems, do let me k… umm, on the other hand, seeya!

I could almost feel his hateful gaze burning into my back as I walked out the office. We Linux users are a pain to most normal people anywhere in the world. Sharing files? Oh, wait… I gotta get Samba working. Hey – why can’t you see my Yahoo! Albums invitation? What? You’re using GAIM? What in the dickens is that? Hey – why can’t you see my webcam? GAIM again? You freak! And now the cableguy.

Now to find a nice graphical tool for Fedora Core 2, so my parents don’t have to open up a terminal window and type more text than the email they want to send.

I didn’t remember seeing a graphical tool for any Linux distribution for configuring a pppoe connection. My parents’ computer has Fedora Core 2 installed, my ThinkPad has SUSE Linux 9.2. No amount of search on Google for a graphical front-end to pppoe on FC2 yielded any results. For SUSE, I didn’t even have to search. YAST is the answer to all your problems. YAST can do everything for a hacker except find him/her a date. (And with Nat Friedman et al at work at Novell, it’ll be able to do that as well.) After configuring your PPPoE connection through YAST, KInternet is a nice application that sits in your system tray and offers you nice context menu options like “Dial in” and “Hang up”. Cool! Just what I want!

I’ll be installing SUSE 9.2 Pro on my parents’ computer next weekend for sure! That’ll sever my last link with Red Hat-based computers.

Why IBM won't certify products for x86 Solaris 10

Sun is mad at IBM. Sun’s President and COO Jonathan Schwartz even wrote an angry letter to our CEO Sam Palmisano last Friday. Understandably. This eWeek report from the 17th of January states that IBM’s refused to “test, certify and support its enterprise software applications on Solaris 10 for x86 platforms”. Which is strange, considering that IBM’s fully agreed to do the exact same thing for Solaris 10 on SPARC.

The ostensible reason from IBM is that they don’t anticipate customer demand for Solaris 10 on x86. An IBM spokesperson said that if and when Solaris 10 on x86 reaches “the required level of customer interest”, they’ll “review the matter”.

The argument does sound a little specious. If IBM begins this process of testing and certification only when customer demand does hot up, it might be a case of too late. Especially if other vendors can competing products, all certified. And IBM has time on its hands: Solaris 10 for both platforms will be available only in March, so there’s time for the certification process.

So, being the conspiracy theorists we are, let’s try to analyse the real reason behind IBM’s stubborn refusal. According to most analysts, IBM wants to thwart Solaris on x86 entirely. Solaris is an OS that directly competes with IBM’s AIX and Linux OSes. AIX currently runs only on the POWER platform, but IBM offers Linux on its entire range of Intel-based xSeries servers. With Solaris on x86, IBM loses an opportunity to offer a Linux-and-xSeries bundle, especially with the hype that Sun’s successfully built around Solaris 10. Novell might also figure in the calculations, now that IBM’s pumped in USD 50 million into the company to enable it to buy SUSE. IBM provides Enterprise Linux flavours from Novell and RedHat on its servers.

Also, IBM’d like nothing better than to replace a Solaris-on-x86 configuration with an AIX-on-POWER 5 one, for high-end systems. One pitch it could make to customers is that a complete IBM solution might be cheaper and easier to support than a bits-and-pieces Sun-and-IBM one. Indeed, according to the article, Scott McNealy was told by IBM’s CEO Sam Palmisano that “IBM no longer has to support an environment that includes Sun, even if it is one that is best for the customer.”

IBM has the advantage of being able to offer a wide product range, whereas Sun still remains very much a platform provider. IBM can use its middleware applications muscle to promote its platform further, and vice versa.

Update on Novell's Internal Linux Move

Two days ago, I’d wondered about Novell’s Internal Linux Move, on the sidelines of an article about such an announcement by IBM. In an interview with ZDNet UK, Novell’s MD in the UK told readers to watch out for announcements on that front at Novell’s Brainshare 2004 Convention in March last year.

Today, I hit pay dirt. Here’s an April 2004 interview with Novell’s CIO, Debra Anderson, (interestingly enough, also by ZDNet UK), which focusses almost entirely on this internal migration. Debra admits that a significant motivation for the migration was perception – Novell wanted to be seen as “eating its own dog food” – something that Microsoft is very proud of. Also, the migration strategy seemed to be to first use OpenOffice across the organisation – on Windows – and only later migrate fully to Linux. Novell also won’t be upgrading any Windows desktops they already have:

How is it working out winding up the Microsoft licences you do have – are they making that an easy thing for you to do?

It’s interesting you ask that — we just concluded our licences in March. That was our annual contract with Microsoft and we terminated the Microsoft OS and Office enterprise licence.

That was across the entire organisation?

What that means is that for all the OSes I have, I do not have upgrade rights. Now I still have perpetual use for the set number of Microsoft Office clients I purchased

I also stumbled upon a couple of March 2004 articles from Brainshare 2004 on – where else – ZDNet UK! Here’s an interview with Jack Messman himself ( Novell’s chief executive and chairman, for those not in the know). Jack also was in a particularly bombastic mood, declaring “We don’t need no stinkin’ Windows“! Remember, all of this was at Brainshare 2004, held at Salt Lake City between March 21-25 2004. It’s been over three quarters of a year since then. If Novell had indeed made significant progress on their promises, we’d be hearing from them a lot more than the stony silence we’re getting on this issue.

If IBM and Novell, the current flagbearers for Linux in the Enterprise, have both faltered on their own Linux migrations, they’re going to find it very hard to convince customers to do the same, either on the desktop or in the datacentre. There had better be some soundbites at Brainshare 2005 – March 20-25 2005.

Microsoft makes a big show of inviting customers to their Redmond campus to show off their internal usage of the latest in their product line. Gates devoted a large chunk of an entire chapter in his landmark “Business @ The Speed Of Thought” to this claim. Paul Thurrot, professional apologist for Microsoft, often touches upon this in his reports on his website. (Hey, to be fair, I admire his zealousness, and I recommend his website to all Windows enthusiasts!) It’s time IBM and Novell woke up to the need to not only do the Right Thing, but also to be seen doing so.

SUSE Linux 9.1 Professional on the IBM R50 Thinkpad

Well, I got SUSE 9.1 Pro on my shiny new TP yesterday! Works like a charm!

I had a DVD of this distro from Novell, but since my old PC didn’t have a DVD ROM, I never got a change to have a look at this supposedly cool distro. RedHat/Fedora has been my mainstay since the bad old days of Linux 2.0.

SUSE’s installation is about as easy to use as Fedora’s, but it’s certainly more powerful. The only gripe I have is their handling of multilayered dialogs – where one dialog/preference box leads to another – leavs much room for improvement. The NTFS resizer was a joy to use! IBM’s default partitioning scheme is to use a ~4GB partition (which they call PreDesktop Area) for recovery, and use the rest as ine large C: drive. In addition, when you first boot the TP, Windows converts this FAT32 drive to NTFS. I’m glad SUSE was able to resize this so well; Fedora and the rest MUST have this feature by now!

(I’d do away with Windows XP altogether except for the fact that I’d paid good money for this copy – and IBM doesn’t provide installation CDs! GRRRR!)

The installation is simple for a newbie – if he/she sticks with the (decent) defaults, and is sufficiently flexible for a power user to tweak. I picked almost all of the packages SUSE had to offer. However, the installation itself takes a very long time – 4 GB took 2 hours to install! This is unacceptable, guys!

Once I was done, though, the most adorable little chameleon greeted me at startup! This was a welcome change from the furious cascade of kernel debug messages I was used to in Fedora. Even RHGB – Fedora’s attempt at graphical boot, although professional-looking – isn’t as pretty as this. My first virtual console was in a nice framebuffer.

OK. SUSE makes the best KDE desktop in the world. Period. No arguments about this one. I’ve tried Mandrake, RHEL and Fedora, and no one puts as much into their KDE as SUSE. I’ll put up a screenshot of their default desktop sometime soon. YAST is very nicely integrated into KDE’s Control Centre. SAX2, SUSE’s X configuration tool, rocks. The menus are well arranged, lots of applications, sensible defaults. Two great-looking wallpapers.

Gnome sucks. I hope fervently that things have improved in the 9.2 release and in Novell Linux Desktop. It’s amazing that fonts that look so great in KDE can be so unreadable in Gnome. And don’t accuse me of not tweaking enough – I’m a Gnome lover too, and know a fair bit about using and configuring it. YAST isn’t too well integrated here – and it’s difficult for a user to run a pure-Gnome SUSE desktop , because all of YAST’s modules seem to have been written using the Qt libraries. Oh, well – SUSE did always tout itself as a KDE-centric distro. Wonder how Ximian’s changed that.

SUSE’s notebook support is amazing! I’ve yet to go over this in detail, but suspend/stand-by and hibernate worked like a charm! There’s this YAST module which is a front-end to kpowersave – and it’s the most intuitive way I’ve seen to manage a mobile computer’s power-handling features. I was advised not to try ACPI, and to stick to APMd. I’ve done that. There’s this nice piece on OSNews.com about SUSE 9.2 Pro’s power handling support. Hope to upgrade to 9.2 soon, will try that out. More on this as I explore further.

The R50′s scroll feature doesn’t work yet, but there’s a program by the name of TPScroll which apparently does a good job at fixing that. I’ve dowloaded it, will try it out tonight. More later.

OK – so that’s my first experience with Linux on a Laptop – and, as you’ve probably guessed, it’s been quite appealing!

Say hello to my new IBM ThinkPad!

My IBM Thinkpad R50 has arrived:

Here are the specs:
1.) ATI Mobility Radeon 7500 64MB 128-bit DDR Video Ram Operating at 210 MHz.
2.) 14.1″ TFT Screen
3.) Trackpoint
4.) Touchpad
5.) ThinkLight at the top of the screen illuminates the screen in low light conditions.
6.) System and power status indicators:
Wireless status,
Bluetooth status,
Numeric lock,
Caps lock,
Drive in use,
Power on,
Battery status, and
Standby status.
7.) Function keys for screen brightness, full screen functionality, web browser forward and back buttons, (these are all hard-wired key functions, so their usage is not OS-dependent. However, a nice project called the TPB (ThinkPad Buttons) enables an on-screen display on Linux.
8.) Built-in microphone
9.) Volume increase/decrease/mute buttons.
10.) Centrino Mobile technology – wireless support built-in via”integrated dual diversity antenna built into the display”.
11.) 40 GB HDD
12.) DVD-ROM – no CD/RW! :-(
13.) 2 USB ports
14.) Video-out connector
15.) Agere systems AC’97 Modem
16.) PC card slot – to attach modem, data storage, network, and SCSI connector cards.
17.) Built-in Infrared port.

Right now I’m doing a bit of research regarding the best distribution for install on this new machine.

Since I’ve got a nice licenced copy of Windows XP here, I don’t want to dump this one to install Linux… but the problem is that all 40GB here on my TP has been allocated to one primary partition. So first I need a distro which can resize my Windows partition. I hear SUSE can. I have a nice SUSE 9.1 Professional DVD here which Novell shipped me free of cost sometime back… and I think it’s got Ximian Desktop included (drool!). So that’s my first choice.

If I don’t like SUSE (I doubt that!), I’m going to use their installation program to resize this partition, and install FC3 on top. But I’m tired of RedHat/Fedora and I want a change.
Let’s see how this goes.

Update (January 22nd 2005): I’ve got Novell Linux Desktop 9 on my Thinkpad now; and got rid of Windows XP altogether! Although this is a great distro, I still want to give SUSE Linux 9.2 Professional a try. I’m attempting to dload all the 5 CDs (Five! How bloated can Linux distros get anyways?), and I’ll write about it when I’ve installed the bunch.

Technology For The Sake Of Technology?

I found this thought-provoking article on the Web. It debates what continuous adoption of (often disruptive) technology, without considering the ends which they may help us achieve, is doing to us as a society. The author terms it our “hollowing out as human beings”.

The article’s been written some time ago, because it mentions the Heaven’s Gate Cult Suicide of 1997 as a relatively recent event. It’s scary that this “technology overload”, as it were, had its beginnings at least seven years ago. Imagine how much technology we’re bombarded with today. Why are we, then, almost unaware of this phenomenon? Have we adapted to this, are we now able to keep up with the pace of technological evolution? Or is this like a ticking time bomb – one fine day might we all reach a limit and collectively scream “no more!”?

It’s a topic about which I’ve lately thought about, too. It’s easier for me, involved in the computer technology industry, to realise the implications of what the author’s talking about. Maybe I’m a victim of this “hollowing out” also. Let me explain. I work exclusively on the Linux platorm at home. I’ve been doing so for the past 3 years. Now the Open Source Community churns out software updates at an alarmingly fast rate. This includes the Linux kernel itself, Linux distributions, development tools, productivity software, internet software, and the like. I like to keep my system populated with the latest versions of whatever software I use. These include browsers, email clients, code editors, music players, IMs, and more. I find myself spending a lot of (paid) Internet time simply downloading the source for these updated releases, compiling and installing them, and deleting the older versions. Then I start up the application again, confirm the newer version number, and get a warm and fuzzy feeling inside about “living on the cutting edge”.

But lately I’ve come to question the very purpose of doing this. I spent the last two weeks downloading Fedora Core 2 (a four CD set, now – see this article on OSNews about software bloat). I only get free broadband access on Sundays, so the last few Sundays (and today) have been spent downloading FC2 full-time, which meant that I had to cut down on my browsing. Now I’m thinking – do I really need FC2? What does it offer me over FC1? New software? No. I’ve already updated the programs that I run, so much so that they’re newer than those that FC2 includes. And why am I obsessed with running the latest versions of my applications? Take Gaim, the ubiquitious Instant Messenger for Linux, as an example. Now that I think about it, the only time I actually needed to upgrade was when Microsoft introduced a new standard for communication via its MSN protocol. I don’t even know (or even care) what new features Gaim’s introduced since then. I certainly don’t notice anything new. That goes for almost all the applications that I use. I’m just using up my Internet time and bandwidth with them, I guess. I have friends who are happily running Redhat 8.0 or even 7.3 – over 2 years old.

Of course, what I’m giving you is just the user’s perspective. What the original article talked about was the actual development of technology, from the producer’s point of view rather than the consumers’. In terms of Open Source, though, this kind of “technology for the sake of technology” is acceptable. After all, most developers of such software work on it during their free time (ok, so they actually free up some time for these pursuits, but the logic is the same) – they have a day job that provides for their families. The problem here lies with the users of such software. I’m sure there are scores like me – who upgrade for the sake of upgrading.

One of the oldest adages we learnt was “Necessity is the mother of invention”. I wonder if that’s even valid anymore. It’s more like “Invention begets necessity” these days. A new technology finds itself a use, rather than the other way round. But why does society accept, often blindly, new tools that become available with such frenzied frequency?

I’ll take mobile phones as an exmaple. Mobile phones now are so rich in features, like 32-bit color screens, wireless connectivity, cameras (some with zoom, for God’s sake!), “polyphonic” ring tone capabilities, and on and on – that it makes me wonder how many of these features we really use. In India (OK, in Mumbai, at least), owning the latest and snazziest mobile phone isn’t even a status symbol anymore – everyone’s got the best. But scan the list of features above, and think for a while how many of them are really useful – useful for the basic purpose of a mobile phone, which is communication. Perhaps we’re spending too many resources innovating in the wrong areas. Instead of polyphonic ring tones, how about researching smarter notification techniques; instead of 32-bit color screens how about working on smarter, easier-to-use grayscale interfaces? It’s been pointed out over and over that the one factor that will limit innovation in phone displays is the size of the screen – so how about working to overcome that? The dimensions of photographs taken with a typical mobile phone camera are way too small and awkward to find any practical use. I know there are phones with cameras that allow for full, 800×600 pixels or better resolutions, but they’re outrageously expensive, and that’s because the cost of the camera is far greater than that of the phone.

And what does that last point indicate? Simply that too much innovation obscures the fundamental purpose for developing that technology in the first place.

There’s another side to this argument, though – and it would become another essay in itself – that we do not have any idea of future uses for today’s outlandish research. The vast majority of the public thinks that research into subatomic physics, into deep space astronomy, and into putting mega-pixel digtal cameras into ever-tinier mobile phones (!) is a collosal waste of time and money. Also, research into technologies such as cloning, and high-tech weaponry, is downright dangerous and should be Stopped At Once. These things are viewed as “Technology for the sake of technology”. But we can gaze only so far into the future. We have no way of finding out if today’s research into what appear to be useless/dangerous fields, actually turn out to be the base for some tremendously useful technology, one that solves a major problem, or makes life unimaginably richer. Are we stifling our future by limiting such research? Are we denying a possible better life to our future generations by insisting that today’s innovators solve today’s problems?

That’s one debate that’s far from being settled.