It hit me tonight that all that time I spent learning the .NET framework starting way back in 2002 was mostly wasted. As much as I love the C# language and have come to appreciate F# (can’t say the same for WPF & WCF), it just hit me tonight that with Windows 8 and the Metro style of applications – in addition to Node.js being ported to Windows – that all I’ll need to know is two languages. On Windows 8, to build user applications, I’ll only need to know C++ and JavaScript.
That’s weird.
Recent reading:
Windows 8’s Metro UI Isn’t Very Good Without Touch, But That Doesn’t Really Matter
4 Responses for "All that time wasted learning the .NET framework"
I wouldn’t call that time “wasted”, especially if you’re using CF on the server side. With CF’s ability to integrate jAR and DLL resources there’s a huge benefit in being able to offload the heavy lifting onto external modules
All the M$ technologies are bad investments for me. M$ are more likely replace its own technologies like .NET => MFC, WPF => WindowsForm/WebForm, HTML5 => Silverlight, …
They just not have any commitments at all, developers get ‘betrayed’ all the time.
I never touched the Microsoft world, but heard that F# was basically ML targeted to .NET (since Microsoft hired away so many programming language researchers from academia a decade ago); did you ever use Standard ML or OCaml?
Nope, never used those, Franklin. To be honest, my enjoyment of JavaScript and C# led me to F#. I figured I could utilize the .NET framework that I am so familiar with in a functional language like JavaScript.
Leave a reply