This is awesome. Voxer is a Friend-of-Joyent and no.de using Node.js to power their iPhone walkie-talkie app. They put up a HUGE billboard on 101 Northbound just before CandleStick Park. It feels like I run into a new Joyent customer every day. #awesome #voxer #FTW
Steve Jobs vindicated: Google Android is not open
If you needed further proof that Android is not an "open platform", Google just supplied it. On Thursday, the company said that as its select partners release the first tablets based on Android "Honeycomb" – the latest version of its mobile operating system – it will not open source the Honeycomb code.
As first reported by Bloomberg Businessweek, Google will delay the distribution of Honeycomb for the foreseeable future. Asked to confirm the story, Google did.
Google has always billed Android as an open source operating system, but the latest version has always been developed behind closed doors. And even when the new version is open sourced, some pieces of the platform – including the Google Android Marketplace and app like Google Maps – remain proprietary. Google also maintains control over the Android trademark. In the end, this means manufacturers can't build true Android devices unless they play by Google's rules.
When Facebook moved its servers to HipHop for PHP – the code transformer it built to convert PHP into optimized C++ – the company's average CPU usage dropped by 50 per cent. And after six months of additional engineering, the tool was about 1.8 times faster.
Now, after another six months, the company says, it has improved performance another 1.7 times. But this is more than just self-congratulation. The project is open source, and it has been open since Facebook first switched its servers to HipHop in February 2010.
Awesome job. Miss the Six Apart super team!!!
"Crying is useless," said another e-mail. "If we're in hell now, all we can do is crawl up towards heaven."
View more videos at: http://www.nbcbayarea.com.
Just finished another interview on�the Pillow Talk 101�show on Blog Talk Radio! I was so pleased to be asked back. The topic was "Self Pleasure: Getting to Know Yourself," but the conversation covered a bunch of topics, from role playing to the A-spot.
We read�and talked about two of the�"seductions" from�Secret Seductions, too.
Joining us was the fabulous JenniFDB from the 2Chix 1Mic Radio Show.
And this is the day I decided it would be OK to actually BIKE in. I am soaked and cold.
One Year In
Today was my one-year anniversary at Joyent.
I'd worked at MLB for 9 years prior to that, and when I resigned, I literally cried. I loved that job, and my friends there, but I knew that I'd finished what I'd set out to do there, and learned all I could in that position. I needed a new challenge; otherwise I'd spend the next 20 years there, stagnant. In a place where people love the subject matter, on a team where people rarely quit, a bit of a logjam had formed. Sometimes it felt like I was impeding (or competeting with) guys -- some of whom I'd hired from my last gig, guys who'd been my coworkers for a decade. Fortunately, an amazing opportunity came up for me, and I have an amazing wife who encouraged me to make the leap.
The new job, and this past year, have been hard. I tell my parents it's like being back in school. I learn ten things every day, am surrounded by people who're smarter than me, and I'm always up against a delivery deadline. I asked for a new challenge... I certainly got what I asked for.
So, first year review: I don't love everything about California. I don't love everything about working my ass off week-in and week-out. But I do love what I'm helping build at Joyent. I signed up to work with some superstars in the technology arena I'd already been a fan of -- since I started, most most of the rest of the Sun Microsystems dream-team have made the same decision I did, just a few months later.
Tonight, I helped respond to and debug a problem on production systems, running a revolutionary service platform. But what's friggin' awesome is that that platform was written by the guy next to my office, and running on the operating system that we compiled a few weeks ago, that had new features in it that I'd specifically requested. And among the folks using the best introspection tools in the world to analyze the problem were those tools' inventor, along with the guy who literally wrote the book on it.
During the post-mortem, I unwound and chatted with the new crop of co-workers. This time, though it was an online chat, and many of the co-workers were in another country. Still, though, I'm building things again that scare and excite me, and it feels pretty good.
Amazingly, Ryan's post will probably mirror my own, except for all the technical accomplishments. This has certainly been the hardest I have ever worked, and LOVED working. Consulting was hard in that it was many hours, but overall it totally sucked. This job... has been amazing. I have one title, 3 jobs, and a team of 8 that produces as much as a team of 50. Plus what we are doing is so friggin cool and game changing that you have to remind yourself that this ONLY HAPPENS ONCE in a person's lifetime. Stewart and Caterina only created Flickr once. Joshua only created delicio.us once. Mark.... Facebook... once... and so on.
think that Rackspace is trying to control Openstack rather than influence it. A perfect example is the recent change in governance. I responded at the time here.
Basically, Rackspace made governance changes without talking to the development community or the sitting governance board. This is extremely problematic for the health of the project. If Rackspace can make this kind of unilateral move now, what is to stop them from doing it again, if the governance does not suit them. There should be no change in governance without the current governance board approving it. This is necessary for the governance to have any validity. The sad thing here, is that the governing body would have probably approved it with only minor changes. The changes are for the most part good, but the process shows a serious flaw in Rackspace’s thinking.
Rackspace has a choice to make; they can try to control the project and eventually fail, or they choose to influence it and succeed.