Re: F# fsharp
Brandon Van Every <[email protected]>
| Newsgroups | gmane.games.devel.sweng |
|---|---|
| Message-ID | <[email protected]> |
On Thu, May 27, 2010 at 4:21 PM, Jedd Haberstro <[email protected]> wrote: > If you weren't adequately informed about the topic at hand (whether C# + > Mono is a viable scripting solution due to the availability of a REPL and > loading scripts on the fly) and you knew it, why did you choose to respond > in the first place? That's just asking to be ripped on for trolling, > because, well, it is. Or it could be, that some of you think we're supposed to spend all day RTFM before we say or do anything, and that to fail to do so with 100% accuracy is an unforgivable offense. I've met that kind of programmer plenty of times, and frankly they annoy me, especially since I *do* actually RTFM religiously 90% of the time. By the time I actually post about something, I've read a *lot* of stuff, to bring a discussion to the level that I want it. Because I know that so many techies are going to play the game of shooting people down because someone said one tiny wrong "unforgivable" thing. Sometimes I ask myself why I bother to talk to techies about anything in public forums, because generally they will not be convinced, but I guess I'm not quite completely tired of it. Anyways as I believe I said earlier, I skimmed the webpage offered. I was in a hurry, and it looked like was talking about user interaction in a shell. I wrote as much as the person who offered the link wrote: a few pithy words. As to why I should be responding, you may recall that I started this thread. About F#, not C#. Whether Mono C# actually has an interpreter is a minor detour as far as I'm concerned. > Also, going back to whether .NET languages should even be chosen over Lua, > the dominant scripting solution, there are Lua .NET solutions out there. > It's not like by choosing to support C# (which means you should be able to > CLI theoretically use any .NET language), doesn't mean you're dropping > support for Lua. Instead, you're actually just opening up the options to the > dozens of .NET languages out there (C#, F#, Boo, Nemerle, IronPython, > IronRuby, Io, Lua, Scheme, ect..) "Support everything" is a strategy that some people might go for, but I think there are several things to debate: Between Lua and F#, leaving .NET and CLR interop completely out of it, which language has the better semantics for scripting? F# would seem to let you do more, at the expense of being more obtuse to the uninitiated. Both F# and Lua allow one to create DSLs, which can answer some "dumbing down" problems, such as they are. I'm going to hazard a guess that it would be easier to do arbitrary DSL stuff in F#. Lua will never be a substitute for C++. F# can definitely be a substitute for C#, over time. As one migrates scripted code to compiled code, F# looks like a better strategy. Lua semantics will always be irritating as you try to do the same drill with C++. That's why Squirrel exists. Cheers, Brandon Van Every _______________________________________________ Sweng-Gamedev mailing list [email protected] http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com