Small interruption. Looks like scaling to 2 servers on Azure to handle extra traffic crashed the original one.
Azure will reset your VMs when you update their configuration. Normally this involves a rolling reset but as you only have one instance this was not possible.
.NET Fiddle adds F#
11–20 of 72 posts
Re: .NET Fiddle adds F#
#12Small interruption. Looks like scaling to 2 servers on Azure to handle extra traffic crashed the original one.
Sorry for interruption. Lesson learned.
Re: .NET Fiddle adds F#
#13Re: .NET Fiddle adds F#
#14I would like to see an interactive loop to fsi. Seems like you could use websockets for this.
Re: .NET Fiddle adds F#
#15Earlier quoted context omitted.
F# is very un-functional in many ways. Immutable variables are the default but mutable variables are made with just the "mutable" keyword. There are also lots of imperative control structures, like while, and for. Those two combined means that imperative algorithims typically have two distinct translations into F#. First you can translate it literally, where F# looks like a slightly more verbose version of Python. Se…
Un-functional might be a bit misleading for an ML-based, default immutable language. Impure might be slightly more accurate. Having seen F# written by C# coders who've just learnt the syntax, and haskell programmers who are having to work in a .net environment, I'd say F# does a fairly good job of supporting both. It does make some trade offs to allow easy interop with the rest of the .net world (it's type system is…
Re: .NET Fiddle adds F#
#16Can anyone comment how F# compares to other functional languages? Just curious.
Re: .NET Fiddle adds F#
#17Re: .NET Fiddle adds F#
#18I would like to see an interactive loop to fsi. Seems like you could use websockets for this.
Re: .NET Fiddle adds F#
#19I found F# to be rather neat. This is a great way to see for yourself.
One place some predict it will emerge is in the Web API arena, and I could totally see that happening.
Re: .NET Fiddle adds F#
#20Like the union types, but not so much the list operations; seems more natural to:
[1;2;3;4] filter isEven sum
vs.
List.filter isEven [1;2;3;4] |> List.sum
in Scala it's: List(1,2,3,4) filter isEven sum
Of course I'm not familiar with F# so don't know all of the WIN within (Type Providers, for example, are very impressive, would love to see that on the Scala side of the fence one day).