My bad.

Keeping up to date is part of your job description as a software developer...

Try running a well-written F# program through Reflector and disassemble it to C#. It won't even come close to being readable. You really don't know what you're missing out on if you think imperative languages are comparable to functional languages just because they're both turing complete. It's apples and oranges.

Parsers. Edit: Domain-specific languages, iterative evaluation (there aren't many practical REPL evaluators in C#), implementing mathematical equations as code -- generally, any kind of structured data translation.

modified on Friday, April 8, 2011 6:14 PM

Way to think for yourself.

Wtf?? Obviously I know F# is a "clone" of OCaml. In fact OCaml code will compile in F#. And no, F# has been around for almost as long as C# in fact. F# was the testbed for the new features in C# 2 and C# 3 (generics and Linq). Lastly, Microsoft has always been involved in language academia. Much of the work on Haskell comes from people at MS Research. A good majority of the people working at MSR have always been using other OSes too. Man, the crazy things people say.

It's far from perfect, but I like it, and I use it for my own personal use. I don't have many opportunities to use it at work. Several reasons I often prefer it over C#: -The REPL loop makes development a lot faster. -Learning it will improve your awareness of composability, immutability, monads, functional purity and other concepts -- and this is easily applied in problem solving and design in C#. -Some of the syntactic sugar like pipes is quite convenient. -Type inference is also convenient, though C# IntelliSense makes this somewhat moot. -Pattern matching and discriminated unions makes certain tasks, like writing parsers, much easier than in C#. -Tail recursion is properly optimized on both x86 and x64, unlike the rest of .NET. -The compiler is slightly more strict than C# in many ways, e.g. unmatched patterns (switch cases) will throw compile-time errors. Even if you don't like F#, if you find yourself asking the question "what's so different about it from C#?", then you should at least look at another functional language like Haskell or ML.

Only if you lack self-control.

I swear leppie, I've been around here for years and I still see you everywhere[^].

Is it just me, or is the task list completely useless aside from the //TODO: stuff? I mean, you can't even reorder your tasks.

Ah. I've hardly had a use for most Marshal calls, exactly for that reason.

I don't think any of the Marshal calls let you point at arbitrary memory addresses, does it? It probably is a tad safer than unsafe. Correct me if I'm wrong.

I remember Sun insisting at conferences several years ago that the unsafe keyword in C# would be its downfall. People are idiots.

Icons are for sissies.

Jason Zander, who was the genius behind the WinFX -> .NET 3.0 debacle[^], was the self-proclaimed single "approver[^]" of all bug fixes in the .NET Framework. He now works on the Visual Studio team. So no, I don't think anything would get fixed.

Actually the person maintaining my code is me -- a serial killer that knows where I live.

Is it just me or is that no less work than using wall sockets? I mean, you need a dock or a "disk" for most devices so far, and the mat only gives you so much room... Also if you're limited on desk space, you might only want to be charging your iPhone in front of you while you want everything else on the floor/by your bed/whatever. With this you can't do that, unless you have more than one mat, which defeats the purpose. I'm more interested in the induction technology that powers devices anywhere within a certain range, not just on a mat. This technology seems too transitional to be practical.

Aye, well said. Thanks. Both my client and I were a little regretful that we the specs were somewhat vague. It worked out in the end, but the price wasn't what either of us had expected. Thanks again.

I got tired of all the negotiation and stuff and settled with a $2000 lump sum. I think I'm going to need some sort of manager if I'm going to stay in this job. Some of us just aren't cut out for demanding money.

I thought they learned their lesson with .NET 3.0[^]. They were talking about .NET becoming fragmented[^] (especially with .NET 3.0) before, so I thought they might have realized they're doing something wrong. They even moved Jason Zander to the VS team[^], which I thought might prevent him from doing any more damage. But noooo. They haven't learned.