Slashdot Mirror
Inside Microsoft's New F# Language
robyn217 writes "There's a new language being formed in the bowels of Microsoft. Recently I got word that the language F# (pronounced F Sharp) is nearing workable stages at Microsoft Research. So, I went in for a look-see. What I found was an interesting blend of imperative (Java, C#) and functional languages(it's ML-based, too!). It looks pretty enticing to me from a computer science perspective, but I'm not sure it would fly in the professional market. I can see the ease of development that a language loosely based on ML would bring, but I can't see coders switching over in droves since it's a tough learning curve." Our previous story on F#.
Its just fu#ing C# with lots of holes in it.
c# is like a whore with lots of diseases.
Users you can f#ck C# at your own risk.
Microsoft should be really grateful if the market really picks up C#. Instead theyre introducing competition to themselves. Good programmers choose C, C++ or java and stick to it for the rest of their lives. Microsoft stooges however would look up to Microsoft and take whatevers thrown to them, but its the good programmers Microsoft should be going after. They did claim theyve learned alot from Linux's loyal developer community, they obviously lied.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Do you relize that an F# major has 6 sharps.
But, an F# is the same as a Gb (G flat) which has as 6 flats.
Actually F# and Gb are different notes. It is obviously easier for manufacturers of musical instruments to pretend they are the same notes and that is why you'd have to look long and hard for a tradition instrument that treated them as different, but there is no reason for computer based musical systems to treat them as the same tone.
Shut the hell up, Krout, you tofu-gobbling, sherry-swilling queer.
The problem with Haskell is that's it's too pure of a functional language.
I/O and stuff that that is a pain in the ass in Haskell. Pure functional languages go too far, we live in a stateful world no matter what they try to tell you.
The best paradigm is a mix of styles. Imperative, functional, object oriented, they all have their place. Some will point out that LISP can do all that, and it's true. However LISP has a assbackwards syntax that makes it difficult to translate math problems into the language.