I am still using Visual Studio 2008, and the may F# CTP seems to be working fine with it.

I can't get myself to use Visual Studio 2010, the fuzzy font rendering is just too painful. What on Earth were the Visual Studio guys thinking when they decided to switch to anti-aliased rendering ???

By on 6/7/2009 1:49 AM ()

What on Earth were the Visual Studio guys thinking when they decided to switch to anti-aliased rendering ???

I can certainly share your pain there - it annoys me a big deal as well. So let me explain.

VS didn't really switch to anti-aliasing in particular - it rather switched to WPF (for many good reasons, improved extensibility among them), which does indeed have known problems with rendering of small fonts. It's not anti-aliasing as such that's the problem, it's rather the specific way WPF does it. The good news - if you look at the problem report linked above, and the WPF team reply - is that it's going to get fixed.

By on 6/7/2009 3:55 AM ()

but, F# is far from practical language, to my feeling.

it is only time to learn sth about F#, but it is not practical yet to make some softeare with it. right?

no one will move from C# to F# before F# has similar functionalities (at least, windows forms GUI support, powerful libraries from MS or from third part) to other .net languages.

of course, for the moment, F# can be used to do some short projects like computations.

By on 6/5/2009 5:39 AM ()

People are already build large scale systems in F#, at few companies any. More people will probably move over to it when VS2010 is released.

Yes, they the lack of GUI designers is a small pain point. However, it's quite easy to work around since you can create a GUI in C# and easily link it to your domain logic written in F#.

As you point out F# is very good calculations and writing domain logic. For this F# is a very practical language. This is the part of software that really interests me.

But, yes, if you just want to drag and drop GUI together, stick with C# (or VB.NET)

Rob

By on 6/5/2009 6:13 AM ()

+1.

I've been using Visual Studio 2010 and the June 2009 CTP for a weeks or so now. It's just so much more reactive than the previous CTP and the error list actually works, which is a huge plus.

On the language side there seems to have been a big clean up around conversion of functions to delegates which really smooths things out.

Keep up the good work guys!

Rob

By on 6/5/2009 1:47 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper