Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The C#, it turns out, is the same as a Java but with a finer stock of liqueurs. The recipe for C#.NET however, is proprietary and no one can quite explain why one in a thousand makes you ill, or why the bottom of the glass seems to fall out sometimes.


"...explain why one in a thousand makes you ill, or why the bottom of the glass seems to fall out sometimes..."

Sounds more like current JavaScript and HTML/CSS. Unless you "drink" it using special kind of "glassware" like JQuery and BootStrap.


In which way C# and .NET is proprietary?

WCF, WindowsForms, EntityFramework are proprietary. But nobody in sane mind will use them.


I am proficient in all three of those technologies.

I was about to object... but yeah, you're pretty much spot-on. I still say that, except for the omgwtfbbq databinding stuff, Winforms was a fine technology for its time. It's just that its time is past and MS doesn't ever update anything, they just abandon-and-replace with something horribly baroque.

EF is my definition for "so close, and yet so far".

I have no idea what the heck happened with WCF though. Seriously, I can't even find the kernel of good ideas that got corrupted in the process of implementation like I can with those other two.


WinForms - in fact is OK. It's just old.

WCF and EF - "oh noes". My eyes are bleeding with just one look at this.

Microsoft can make something simple and brilliant as TPL, but on other side we have such overengineered behemots as WCF and EF.


WebAPI and SignalR (backed by Microsoft) replace WCF for most of unreliable stuff. The rest should be using message queues anyways.


And what's the Java? An Old Fashioned, made with coffee bitters.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: