(this is page 21 of 121)





Latest

Liz Gannes over at Gigaom has a coined new term for what Google is doing now that it is back in the $3-15MM acquisition game for former Googlers that have left the nest: "acquiring," a mixture of acquiring and hiring. In the case of companies that have received external funding, this is a fast way to poison the well (after all no fund, no matter what the size, has its needle moved by such low dollar exits) so it's pretty clear that it is a bad thing for the ecosystem. In the case of bootstrapped companies however, I can't tell if this is a good thing or a bad thing.

It is a good thing because the founders of these projects walk away with two really important things: some cash in the bank and the confidence that they can build something that is valuable to someone— valuable enough that the mighty Google is willing to pay an especially outsized hiring bonus for it.

It is a bad thing because it creates the feeling that shooting for feature on products is a viable (and relatively safer) way to achieve success. This is an illusion for two reasons: first, future real investors and employees are savvy enough to see these types of exits for what they are. And second it allows entrepreneurs to focus on incremental "pickoffs" from the guessable product roadmaps of mainstream products instead of completely disruptive ideas.

Another way to put it: I've met with a few folks in the Boston ecosystem recently who are trying to get this "Think Big" meme jumpstarted with entrepreneurs and investors. And sadly, these "acquhires" seem to be taking us all in exactly the opposite direction.

Comments Permalink

Chris Dixon had a provocative post on how young engineers choosing to join big companies like Google is bad for the startup ecosystem, a common sentiment among the folks that I have been meeting over the last few weeks here in the rekindled Boston startup scene.

But I'm not sure it is right for one simple reason: for the most part, young founders tend to breed stupid startup ideas. Not because they are themselves stupid, but because they lack the proper execution context.

And while there is a lot of merit to apprenticing at established (funded) startups, I'm not sure that most of these provide adequate execution context either.

So if context truly is king, what does the proper execution context look like? Ideally, the right context exposes one to a whole host of business problems that need solutions because the current ones are being provided by big dumb companies that have grown fat and complacent of the profits produced by innovations whose progenitors are long gone. This is even better when the problems can be solved through new innovation that is itself only possible as technology is shifting.

Let me take a local example: here in Boston we have an existing cluster around storage, anchored by one of the biggest, dumbest tech companies I've ever seen: EMC. If I were betting on disruptive startups, I'd much rather take the folks who have spent time selling billions of dollars worth of storage into big companies, government contracts, and just about everyone else. Certainly more so than the folks that have spent burned cycles trying to copy Dropbox or Carbonite because that is the context they understand.

One of my heroes, Alan Kay, said that the right perspective is worth 80 IQ points. In my experience, execution context is not dissimilar.

Comments Permalink

For a while I loved Twitter. Not because it was realtime. Not because it was easier than blogging. And not because it was cool.

Mostly because it was a quick way to get a feel for the things that were going on in the lives of folks one level beyond those who I interacted with every day. In having invented a new format (140 characters) and brought into mainstream the asymmetric follow relationship, Twitter brought into the world something really interesting.

But then the marketing people got on it. Or if they were already on it, they got super aggressive about polluting the Twitterverse. Link velocity increased by orders of magnitude, and what started out the types of interesting articles that you might share on Delicious, quickly became links to people's companies, blogs, or special "deals" (thin affiliate scams).

Sure, you could always curate the list of your followers and keep only that 0.01% of folks who had not started using Twitter as a new form of direct marketing. But as Twitter climbed to a billion updates per month something happened to the way in which everyone uses the medium such that even folks who were funny or insightful one third of the time spent the other two thirds plugging their blogs or the new startup they'd just gotten involved with.

And this, it seems to me, is how a new medium gets "typed" by its early adopters. So that now, no matter how many people get on Twitter (and I suspect it won't be many more), it will forever remain the place where the marketing people should have STFU.

Which is why I am excited about Google Buzz. Though in many ways it seems like a copy of the most social/sharing parts of Twitter/Facebook/Friendfeed, I think its got a few key differences that may help it move adoption-wise beyond what these services pioneered. Chief among these attributes are the easy integration with existing communication patterns (Gmail), and the ability to create fine-grained groups and direct the stream of updates at say, just "family" or "college roommates" or whatever.

This last one is important and will be critical to Buzz's eventual success. During the first phase of the Internet, a lot of products struggled and crashed on the reef of privacy controls, and it wasn't until the 2004-2005 era of "default to public" that a lot of the same services started catching on in a meaningful way. The "default to public" era culminated with Facebook's claim that people needed to abandon the notion of privacy online and just get used to being public. For most of the non-tweeting, non-Silicon Valley crowd, this statement is about as alien as claiming that people needed to abandon breathing and get used to hypoxia.

If this right, and the Buzz team gets all of the small affordances right (no small feat despite an impressive 1.0 effort), this blend of email and status updates (in a controlled way) may create a new format— one which which I hope will not again be typed a new kind of weird direct marketing vehicle.

Here's hoping...

Comments Permalink

Flash has polluted the web

One of the great things to come out of Apple's snub of Flash during the iPad launch has been the discussion around whether Flash is really needed for a first-class web browsing experience. In reading the various opinions, I came across a brilliant Safari plug-in, ClickToFlash, which shims the Flash player so that you have to explicitly approve any Flash widgets that are loaded on pages. The plug-in provides a whitelist so that certain domains will always load Flash (say Pandora and Hulu) widgets. Apparently there are also versions of this same general idea for Firefox and Chrome.

I've been using ClickToFlash for 4 days and there is no going back for me. Apple's claim that the Mac crashes most because of Flash seems well supported by the fact that I can now have 20-25 tabs open regularly without Safari hogging all of my machine's resources. It's awesome.

What is most nefarious about Flash is not all of the explicit video embeds that people use, but the fact that it has snuck into display advertising. If you install any of these plug-ins, you'll quickly realize how many of the standard IAB ad sizes are now actually being powered by Flash widgets— which do nothing but pulse in annoying ways— and perhaps more significantly— suck down system resources.

Just say no to Flash.

Comments Permalink

I wanted to wait a week to put down my preliminary thoughts on the iPad both because of the crazy outpouring of people venting some very real emotion on all sides of the debate, and because I've learned that when it comes to Apple and Steve Jobs, it often pays to let the reality distortion field fade a bit.

I am not a fan of netbooks— as I've written before, they are nothing but cheap laptops. Thus I was sort of excited to see Apple try to reinvent the category with the iPad. After a week of reading reviews though, I'm sad to say that this seems like a fairly incremental product— taking the best parts of the closed ecosystem of the iPhone/iPod touch and hitting the 4x magnify button on the form factor. It'll be a fun and possibly lucrative product— and in the end I could see Apple selling 1/3 to 1/2 as many of these as they have iPod touches (which is about 40MM to date). But here is where they fell short:

1. New formats: the Kindle sucks not because of its screen or hospital ID but because despite the connection to the Amazon web service and the persistent data connection, it fails to be as good as a paper book and doesn't reinvent any of the parts of the book that could use some social/cloud juice. From what I could see, Apple is doing nothing better here (at least with version 1). They haven't defined a new format that would allow publishers to take advantage of video and audio and they didn't do anything to make the experience of finding, reading, and sharing books any more social. Could be that the publishers weren't hip to it, but if anyone could crack that particular cartel, I thought Apple could.

2. Ergonomics: Ned wrote this one up, and frankly, I can't believe the Reality Distortion Field has kept other people from noticing that the idea of a non-tactile keyboard without a place to rest one's palms renders this a piss poor input device. This is ironic as Apple was the first company to do the palm rest design for laptops with the Powerbook 100/140/170 series that was even shown during the keynote.

3. Closed ecosystem: I'm less worried about this one than the people who feel that Apple is starting us on the road to being like the bio-sacks that pass as humans in the movie Walle, because it does seem as though the combination of HTML5 and the A4 CPU will make webapps really sing on this machine, but it would have been nice to have given people some sort of mechanism for side-loading applications (even as "untrusted" like Android and S60 do). Again, this is ironic coming from the company that had its first hit product (the Apple ][) succeed because some crazy hackers in Boston wrote a killer app and distributed it with little involvement from Apple. That said, I do think if the iPad becomes ubiquitous enough, Apple will have to open up (or be subject to aggressive jailbreaking as the FUD around "messing with the carrier settings") doesn't exist for this type of device.

Finally, perhaps the biggest disappointment for me is that because of 1-3 the iPad seems to be primarily a content consumption device, a sort of modern-day version of the portable TVs that Sony and others started selling in the 1980s. That may be what the market wants, but I find it hard to muster the same level of excitement as I would have had for a more general computing type of device. In the case of the latter, creativity really is the upper limit on what can be done. With a closed, content consuming device, we'll end up where we are with the iPhone: with small widgets that all basically do the similar types of information retrieval and display. If this is the new world of personal computing, it looks a little boring.

Comments Permalink