But really... them's just parlour tricks. You ain't seen the half of
what JS/HTML5 can do.
Eric, what can't we do in Javascript that you can do in Silverlight?
-T
…full screen, and adaptive streaming.
http://www.longtailvideo.com/html5/
But, really guys -- is that all? Silverlight, as many have quipped in
the past, is just a video player? (and only for scenarios where those
two points are relevant)
-T
I was fortunate enough to meet Demis the other day but didn't get a
chance to dive into the "were not worthy" groveling I wanted to, since
we were too busy talking about lunch and music. Go figure. WCF makes
it really really hard to do things right. Like most MS products, it
demos well and performs adequately in simplistic use cases but once
you start trying to perform real work with it, you find that there are
many complications that can't be gotten around.. Well, I'll roll that
statement back a bit and say they can't be "practically" gotten
around. Microsoft has done a much better job of componentization in
their architecture, enabling developers to replace default
implementations with custom solutions. Unfortunately the investment of
time and effort required to get something useful out of WCF is just
not worth it. There are so many ways of doing the same thing with far
less friction that WCF is only reasonable when you're 100% MS and
doing relatively simple things. If you're in a mixed platform
environment you're much better off using a different strategy (which
strategy you employ is totally dependent on the use case... there's no
right answer for that except "probably not WCF").
At least... that's been my practical experience. I'm sure others will
disagree and they are probably correct, based on their practical
experiences. ;)
-T
Unix is designed for services. Mac is designed for drag and drop.
Windows is designed for drop-downs and check boxes. Use Unix if you
can.
You'd probably love ServiceStack.Net running under Mono on Linux..
Pretty sweet setup, really... but all your Linux loving friends will
turn their collective noses up for using .NET instead of Node. ;)
-T
I still like .Net though. =)
Allen
Sent from my Windows Phone
From: Troy Howard
Sent: 2/14/2012 12:22 PM
To: pdxalt...@googlegroups.com
Subject: Re: [pdxalt.net] Troy's NodeJs sample
Justin -- ServiceStack.Net is WCF done correctly... as an open source
project: http://servicestack.net/
I was fortunate enough to meet Demis the other day but didn't get a
chance to dive into the "were not worthy" groveling I wanted to, since
we were too busy talking about lunch and music. Go figure. WCF makes
it really really hard to do things right. Like most MS products, it
demos well and performs adequately in simplistic use cases but once
you start trying to perform real work with it, you find that there are
many complications that can't be gotten around.. Well, I'll roll that
statement back a bit and say they can't be "practically" gotten
around. Microsoft has done a much better job of componentization in
their architecture, enabling developers to replace default
implementations with custom solutions. Unfortunately the investment of
time and effort required to get something useful out of WCF is just
not worth it. There are so many ways of doing the same thing with far
less friction that WCF is only reasonable when you're 100% MS and
doing relatively simple things. If you're in a mixed platform
environment you're much better off using a different strategy (which
strategy you employ is totally dependent on the use case... there's no
right answer for that except "probably not WCF").
At least... that's been my practical experience. I'm sure others will
disagree and they are probably correct, based on their practical
experiences. ;)
-T