(this is page 108 of 121)





Latest

This was an interesting find on John Battelle's blog about the different amounts spent on R&D by companies like Microsoft, IBM, Google, and Apple. It's not the first time I've seen something like this where companies that get the lion's share of regular people's oohs and ahhs spend disproportionately little on R&D. In fact I remember when Steve came back to Apple and started hacking costs, one of the first things that went were a lot of these R&D project which caused some Wall Street Journal reporter to write a piece about how this was going to be short-term smart/ long-term stupid. Mind you this was before Apple did Wi-Fi, the iPod, the iTMS, video editing for everyone, or just about any of the incredible things they've done since then.

John argues that the data, being from Microsoft, is self-serving and under-reports Google's spend, but I think that there is something else going on here.Spending cash on R&D when there are no huge leaps to be made but instead incremental hops mostly punctuated by the commercialization of technology seems to be sort of a waste, and worse still, a distraction. The latter comes from the fact that the product groups at these big behemoths (MSFT, IBM) seem to be relieved of the responsibility of truly innovating because someone from the "R&D department" is supposed to be doing it. Maybe I am limited in my understanding of how much future-tense R&D shops can deliver, but when the engineering teams can come up with clever hacks like these, and when it's not clear what the last major R&D innovation Microsoft or IBM commercialized successfully, something certainly seems broken.

Then again, I've also just seen this new Photosynth project from Microsoft that seems really interesting and worth exploring further. That said, there is always an example afoot of how these new-fangled technologies can go awry as did the speech recognition in Vista just last week.

Comments Permalink

I'd be worried if I had any Microsoft stock, and not because Bill G. is retiring, but because the visionary he's left in charge has got this to say about the future strategy of the company.

Now, you know it's got to be a bad strategy for one reason: this speech could have been given 5 years ago (it probably was, at Groove) and it would still have been as platitude-filled and un-actionable back then as it is today. Sure, we're going to connect all devices together with the Internet, and sure we're going to move all of our data to services that synchronize it, back it up, and move it intelligently on our behalf. And to boot, we're going to "optimize" our lives by harnessing the collective intelligence of our group behavior. Rinse, repeat, rinse repeat.

I don't want to pick on one of Boston's own renown tech-heads because everyone I know in common with him claims that he is both really nice and really sharp, and because he's been building software for longer than I've been alive, but I am floored that we can't get something a little more original out of the world's biggest software company, especially one with such an incredible asset.

If I were Ozzie I would have tried to lay out a strategy that leverages the still-dominant PC client footprint in two ways: 1. to build the best peer-2-peer platform for compute intensive apps out there (including gaming, telepresence, group authoring, etc.), something he knows a lot about, and 2. to build the best web-authoring client tool out there (to replace Office) that uses all of the existing back-end services that have in effect already won, as its native document format. Microsoft can still make great client apps, especially now that all of the rest of the world of great client talent has moved on to AJAXy things, and it strikes me that if they don't wake up and recognize this, Adobe is going to eat their lunch. Finally, if I had any more cycles were I Microsoft after chasing #1 and #2, I would focus on making the mobile Windows OS actually usable, or at least competitive with the totally abandoned Palm OS in the Treos that still walks circles around it, but only because the phone is probably the thing that will most quickly erode the PC as the dominant client.

It is true that given how things are going now, the long term doesn't look good for client software, but many things may change. And if they do, it would be a shame to see Microsoft ill-prepared and spread too thin to take advantage of it.

Comments Permalink

Having just canceled my trip to OSCON due to work stuff, my consolation prize last night was getting to go to Boston Web Inno 7, a local networking event organized in the spirit of Silicon Valley gatherings for local folks working on cool new web technologies to present to the audience. There were three companies presenting (Ned covers it here so I don't have to). Here I'll just stick to two observations, both of which make me feel like we're about to start partying like it's 1998 again.

Tabblo: Boston Web Inno 7  height=

The first observation is a small one: it appears that the Web 2.0 design theme is here to stay. Pastels, big sans-serif fonts, and big chunky divs rounded at one edge were used, over-used, and then used some more across all three of the sites. Ned also commented that the sites were all very polished design-wise and they were, but I can't help but feel like we're all going to wake up real soon and have that acid-washed jeans moment where we realize that display-size headers in lime green weren't really all that cool and that not all top-nav has to be done as Amazon tabs.

The second observation was actually made by John (another one of the Tabbloites who was there): we seem to be in a recapitulation phase where all of the dot-com boom ideas are being recast in pastels and launched in the context of "social networks." I worry about this one for real because for a lot of these ideas, there are structural things that don't seem to have changed about behavior, complexity, and general usefulness.

One of the guys was asked this very question and his response was basically "there are more people online now" but this seems to me to be a weak rationalization at best. New opportunities are created by changes in technology or markets that are dramatic enough for new entrants to come in with a completely new approach and in the case of a lot of the new ventures today, people forget a very important fact: most of the things that didn't work due to scale in 1998 are unlikely to work again now, but if they do, any newcomer is going to have to fight a series of entrenched incumbents that simply didn't exist back during the first round.

If it were me, I would spend some time looking for true structural changes that create opportunity spaces where the current web incumbents can't go and focus there first. In a future post I may try to write about the Tabblo funding story, and about how we went through this very process.

In the meanwhile, I'd go read up on this.

Comments Permalink

Work for me search engine!

It's pretty clear now that looking for product information on the web is a Killer App that has no equal with general users (except for possibly email). Which is why I am astounded that we still don't have the equivalent of a Froogle for product reviews. Sure, there was Epinions back in the day and there are also a number of new Web 2.0 comparison shopping sites that claim they are going to extend their reach into reviews, but none of these quite work because they don't live inside of my search engine.

I just finished writing up a review of a pair of Mion Current outdoor sandals that I got (despite not being able to turn up any reviews on them in Google), and I'm fairly sure that because I wanted to include pictures and therefore used Tabblo, I'm not going to see this review popping to the top of any search engine anytime soon.

Here is all that I would like:

Google, instead of doing all of these Microsoft office-killing apps (some of which I like), create a separate entry point into "reviews" and give me a search engine for reviews. Crawl Amazon, crawl the blogs, crawl anything you want- hell you are already doing that- but just make sure to present me with an interface that lets me sort through reviews really quickly, to rate them, and if you're feeling Web 2.0 to add to them if the feeling moves me.

There is hardly a day that goes by that I don't find myself typing "XXX review" only to have to sort out a bunch of junk I don't care about from the general Google search. Solving this problem can't be any harder than Google News which seems to be working pretty well these days.

And no, I don't want to use some standalone site- frankly I don't think any startup would be able to get enough scale (hype around "vertical search engines" notwithstanding) to cover anything and everything. And I certainly don't want to have to go run multiple searches: i.e., Google, Amazon, Technorati, just to get decent coverage. I just want the most comprehensive list of reviews you can give me.

C'mon, Google, how cool would "Google Reviews" be? And if not you, then maybe Yahoo, the "social search" company can jump on this one.

Comments Permalink

Why custom browsers suck

Chris Mesinna (who I don't know but who I gather spent some time at social browser company Flock) had a thought-provoking piece on content-creation tools for the web and the future of rich browsers. I suspect Flock folks are none too pleased that he disses their efforts but I was much more interested in his conclusion that there might really be a future in innovative rich Internet applications built with Webkit which is Apple's equivalent of Microsoft's 8 year-old embedable IE browser control. Using it, a developer can write a rich client application that functions largely like a web-browser but with hooks into the OS for key actions that browsers have traditionally sucked at.

I am all for making better tools for content creators, but this seems like a risky approach to take mostly because of the fact that I don't think it's a tenable strategy to expect a regular user to take an 18.2MB download of a custom web-browser in this day and age (I am in fact trying to write this blog post on the OSX machine in the time that it takes me to download Flock and might just make it). Plus even if the Flocks of the world were to get past the download hurdle, people just don't want more clients– if RSS readers couldn't make it as standalone applications in large numbers given how much value they add over all of the web-based experiences I have seen for consuming RSS, I seriously doubt that custom browsers will.

However 10 years into this web thing, it's not too much to ask that the existing browser vendors address a couple of critical things, namely better upload, rich text editing, and some sort of canvas for drawing (that actually works). That would be a great start, and notice that it doesn't include fancy things like offline use or drag-and-drop across applications. Given their client-side thick-headedness I very much doubt that Microsoft will address this, but I have great hopes that at least some of these issues will be tackled by the forthcoming Firefox 2.0 release.

And when that happens, if Apple has any sense whatsoever, they'll get WebKit in shape to support these things as well. In a future post I am going to write about all of the "dirty little Safari secrets" that we've learned about while developing Tabblo (there really are a couple of gems especially around performance that no one seems either aware of or willing to blog about). And if they Apple doesn't get its act together, well then we'll just continue to be glad to see all of those Mac users at conferences running the Fox on OSX despite its heinous widgets and it's fat footprint.

In the meanwhile, I'm not ready to give up on how far we've come in just about a year's time with interactivity in the browser and the kludge of technologies now known as AJAX. The Javascript libraries are getting quite good (you might even call them platformy) and there are a whole bunch of people coming at the problem from interactive design, engineering, QA, and a whole host of other perspectives which really do help to make a platform.

[As an aside, custom browsers as development tools are a great thing. I've used this trick in the past, and from Greasemonkey fittingly enough, the new Webkit Javascript debugger, there is a whole ton of sense in being able to instrument the browser when you're trying to make it to fancy tricks for users.]

Comments Permalink