Microsoft's Brian Goldfarb, Silverlight Team, demonstrated a jaw dropping implementation of Facebook's recently announced API changes.Goldfarb was presenting at a Facebook Demo day, Cnet news attended and recorded the session (see below). The applications demonstrated were built within 72hrs and Goldfarb confirmed Microsoft will be releasing them shortly. The applications demo'd blow away Facebook's original interface and demonstrate exactly how developers can build some visually rich applications for services like Facebook.
Microsoft and Facebook have been working together since 2007 via the Facebook Developer Toolkit – a first of its kind open source solution to help developers integrate into and build applications for Facebook users. Microsoft and Facebook are certainly forming close business relationships and I would expect the two companies to announce further integration around the Facebook chat to Windows Live Messenger area later this year.
For more information on "Faboolouse" and "Photo Cloud", which are demonstrated below, check out the Silverlight team site.
Moonlight... well... Microsoft doesn't exactly support Linux.
Damn you signalpirate
but yea it makes sense, MS wants to appeal to the widest audience possible
There are just sooo many comments posted like this, which would only make sense if the article was about the technology itself. This is about an example web application, not Silverlight itself.
Silverlight has supported Firefox since the first alphas.
Yes I know that but why wasn't this Microsoft employee using IE.
Yes I know that but why wasn't this Microsoft employee using IE.
(beware the following is a joke
Probably because he found out that Firefox works better.
Anyway, Silverlight is already looking nice so far, but it's still sorely lacking a 64-bit version, just like Flash.
If MS is smart enough to bring out a 64 bit version, they could gain an advantage there.
Anyway, Silverlight is already looking nice so far, but it's still sorely lacking a 64-bit version, just like Flash.
If MS is smart enough to bring out a 64 bit version, they could gain an advantage there.
I'm pretty sure it's because of the extensions, I'd totally move to IE/Opera if it wasn't for them.
Yes. A lot.
Let's say you built a cross-platform application that you want to demo. Do you demo it on a platform that everyone knows it works on, or do you use the platform that not everyone knows it can run on?
I think the new layout is great...it brings a hell of a lot more information right to the homepage than previous iterations.
what they showed looks way better than what it is now. seems like the only reason you dont want to use it is because you hate microsoft lol. if someone else did this same exact thing you would be all over it
Microsoft owns a stake in FaceBook.
Delete your account then, since Microsoft already owns part of Facebook.
This looks very promising, I like how Microsoft are headed now with the internet.
because i don't think it is possible to load such amount of photos in less that 3 seconds.
If it finds new branches from friends of friends or public galleries, then it may go off and cache them too.
cant wait to try it
My question is: was this guy (who wrote the demo) part of the team who wrote the SDK? If so, then what they really should be saying is that it took someone who's been working on this stuff for roughly two years 72 hours to put the demo together...
If you want to impress me, prove to me that someone who doesn't already have 2 years worth of experience with the SDK can write that in 72 hours.
That's a rather dishonest way of trying to impress people, is all I'm saying...
From there, if you want to, you can guesstimate how long a noob would take to learn. Learning is a one-off investment. It makes no sense to judge how fast one can develop using the SDK by using a noob since being a noob is a temporary thing and everyone has different rates of learning which would be affected by how good the documentation is, quality of tutorials and quality of support.
...then if the time to put it together is a moot point, why bring it up at all?
From there, if you want to, you can guesstimate how long a noob would take to learn. Learning is a one-off investment. It makes no sense to judge how fast one can develop using the SDK by using a noob since being a noob is a temporary thing and everyone has different rates of learning which would be affected by how good the documentation is, quality of tutorials and quality of support.
You misread me. I'm not attacking Microsoft here as a whole or trying to hold them to different standards. In fact, I've been called a Microsoft cheerleader on more than one occasion.
Besides--and I'm not sure if that's what you're trying to say--the learning curve is not meaningless if you're trying to sway people into commiting to your dev tools. Sure, it's a one-off investment as you put it, but such investments can still be measured and compared.
To top it all off, it makes me rather uncomfortable when MS switches from v1 to v2 to v3 in what, less than 2 years? On one hand--great, the platform is being evolving--but on the other, it's difficult to justify using something when it's such a fast moving target.
So 72hrs are a possible developing time for those two apps.
Waste of bytes.
Why?
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.