PallarelCoedr

The stream is the consistency (locking) boundary. Your first step it to get your model aligned with such boundaries. For example, your amazon shopping basket is independent of my basket. Then you chose your concurrency model - append to a stream with an expected version (pessimistic) or just append anyway (no expected version). Your amazon basket may be the later, your amazon payment and shipping checkout may be the former.

Locking across streams is an anti-pattern / smell. It can be done (as can anything) but it usually points to a modelling problem. Example: cancelling an amazon order is a _request_ that is in a race with the fulfillment system (boundary); it may or may not be successful.

Embrace eventual consistency. A good deal of collaborative domains (things involving human decisions) are naturally eventually consistent. Meat computers appear to be particularly good at resolving conflicts and compensating.

Forget about older ASP.NET and WCF on mono. The core of ASP.NET (System.Web assembly) doesn't feature in next version of ASP.NET. WCF hasn't seen any effective development in years.

The new stuff (ASP.NET vnext) will be highly mono compatible and like the current OWIN stuff, entirely decoupled from IIS.

It does, but internal abstractions have been rewritten. Webforms view engine won't be ported I reckon.

This reads like a standard list of a cocooned MS developer. With ServiceStack, NancyFX, NHibernate, Dapper, OrmLite, etc out there could you have just been making some bad choices?

And anyone who knew web, knew Silverlight didn't have a future from the very beginning.

OWIN will give some of what you are looking for.

Three here: quora, w3schools and expertsexchange

Related to the launch of the Pirate Browser perhaps?

.NET folks don't particularly like him either.

Can I use a browser other than IE on it?

Too much space wasted across the top too. Looks promising though.

They probably didn't want them to stay around permanently, just long enough to complete knowledge transfer.