Kamujin

Clickone deployment supports web based deployment, so it running in a temp folder not that different from your web cache. IE, not "installed".

 

Your making a different case then he did though when you switch it to a fulltrust / partial trust issue. He clear states "Winforms is great, but we don't want to do any deployment".

So you need zero deployment for a winforms applications? Ever heard of clickonce?

 

Not that the silverlight version isn't cool, but you have responsiblity to your customer to offer them all the relevant choices. It seems that this was not the case here.

Please don't take me the wrong way. I am excited to see where this is going.

I am particularly curious about how chatty you can get with these agents before latency suffers. I am also curious to know how much memory allocation is going on behind the scenes to services the agents.

If I was overly critical in my first comment, it comes from prior experience where the examples made a language/tool look really simple. Then as soon as you apply it to a real world problem, the kludge, scaffolding, and other gotchas show their head. Haskell being my most recent disappointment.

I don't mean to suggest that this will be the case with Axum. I am simply curious to see something less trivial.

This is completely disappointing.

public static int Add(int x, int y)
{
return x + y;
}

is as concurrency safe as this example.

Show me an example that's hard to do with current tools.

Honestly, this stuff is great, but I always come away with the impression that the developers don't realize how many people these days use more than 1 monitor.

Supporting a multi monitor task bar seems to me to be a relatively easy addition that can offer a great amount of functionality to users. (IE low hanging fruit)

I guess we'll have to wait until Apple adds it to OS X before Microsoft will admit that this feature is useful.


(BTW, I know this feature has been added by 3rd party add-ons like UltraMon for years, but due to API limitations, it tends to be very fragile as an add-on)

Let's just say that your assumptions about me are wrong and leave it at that.

I don't have the brainpower to know who's right on the static typing debate, but as someone who's written a great deal of code in static and dynamic languages for production use, I was shocked at the suggestion that static typing does not aid reliability.

To my thinking, reliability based on code that will error at compile time is far more desirable than code that depends on developer discipline. Not because it makes coding easier, but because it frees my limited mind to be creative about far more interesting problems.