```json
{
    "title": "Joost: A change to the program",
    "url": "https://performancezen.com/2008/09/05/joost-a-change-to-the-program/",
    "datePublished": "2008-09-05",
    "dateModified": "2008-09-05",
    "language": "en-US",
    "description": "In April 2007, I tried out the Joost desktop client.  [More on Joost here and here] I was underwhlemed by the performance, and the fact that the application completely…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Joost: A change to the program

In April 2007, I [tried out the Joost desktop client.](http://newestindustry.org/2007/04/05/joost-suckscpu-and-bandwidth/)  [More on Joost [here](http://www.crunchbase.com/company/joost)and [here](http://www.joost.com/)]
I was underwhlemed by the performance, and the fact that the application completely maxxed out my dual core CPU, my 2G of RAM, and my high-speed home broadband. I do remember thinking at the time that it seemed weird to have a Desktop Client in the first place. Well, as [Om Malik](http://gigaom.com/about-om/) [reports](http://gigaom.com/2008/09/05/joost-to-kill-desktop-client/) this morning, it seems that I was not alone.
After this week's hoopla over [Chrome](http://google.com/chrome), moving in the direction of the browser seems like a wise thing to do. But I definitely hear far more buzz over [Hulu](http://www.hulu.com/) than I do for Joost on the intertubes.
Update
[Michael Arrington](http://www.linkedin.com/in/michaelarrington) and [TechCrunch](http://www.techcrunch.com//) weigh into [the discussion](http://www.techcrunch.com/2008/09/05/breaking-joost-turns-to-the-web-for-help/).