mmavnn
Joined 17 years ago
Karma
950
Submissions
125
Member since
Jan 2
[ my public key: https://keybase.io/mavnn; my proof: https://keybase.io/mavnn/sigs/XP1doWi5y1DWLOq5tHikbVnSpyiuVDn8PGjBG8W7hUw ]
View on Hacker NewsRecent submissions
Comment · 7 years ago
It also has syntax for structural typing where needed.
Comment · 11 years ago
I must admit, I'm not desperate enough for new readers to hamstring my own publishing to my existing readers - so summary RSS feed is out for me.
I'd consider delaying RSS publication but that's actually very awkward as it's an Octopress website (i.e. created and pushed as a set of static pages, including things like the rss feed).
Comment · 11 years ago
Known Octopress issue, apparently: http://hackingoff.com/blog/octopress-default-seo-flaws/
Thanks, patio11
Comment · 11 years ago
Interesting; that's autogenerated by Octopress (or Jakyll). I'd never noticed it's missing the '/'.
Comment · 11 years ago
I have yes, no mention of any issues from the tools (it even claims to like the sitemap).
Comment · 12 years ago
Packages generally work fine, although if they rely on native binaries they often require a bit of tweaking to point at the Linux .so rather than the windows .dll. That's uncommon in the .net world though.
The ecosystem is huge; http://nuget.org hosts the main .net package collection, and it fairly comprehension. Also, to be fair to MS the standard library is pretty "batteries included"; it just doesn't always have what I would consider the nicest APIs.
Comment · 12 years ago
As mentioned above, fsx files can be executed with the correct #! if fsharpi is installed.
Comment · 12 years ago
I'd probably look into Paket (a nuget aware package/source dependency manager) for that. Sorry for the short answer, New Years celebrations beckon!
Comment · 12 years ago
The F# community seem to be most active via twitter, Google+ and (slightly bizarrely) StackOverflow chat in my experience. /r/fsharp is pretty small, although I've always found it friendly.
Comment · 12 years ago
It is mainly Windows, but as stated in a few other answers people are using Mono in production. How long ago did you look around? I have to admit that it's only really become fully practical (in my mind) in the last 6 months or so.
Comment · 12 years ago
It should be possible to plug the F# binding backend into sublime; it expects to run as a separate process and have buffer states passed back and forth as JSON. I don't know much about sublime plugins, but I believe that they're Python based and should be able to handle that reasonably elegantly.
Comment · 12 years ago
As in a self executing file? Not the standard deploy story, but is in theory possible on Mono with a combination of F# compiler options to compile in all dependencies, and mono's "ahead of time (AOT)" build.
It does mean that you lose a number of traditional clr advantages such as JITting - and I have to admit that I haven't tried this route myself. Almost all of the clr code I've written has been server side.
Comment · 12 years ago
The lack of good instructions is definitely one!
(Edit: although http://fsharp.org/use/linux/ covers the absolute basics pretty well)
Up until recently, packaging was a bit of an issue, but recently the official Mono repositories have started being much more up to date again, and now include recent versions of F# as well: http://www.mono-project.com/download/#download-lin
Getting vim support is still a case of cloning the project from github https://github.com/fsharp/fsharpbinding and running make in the vim directory - Vim 7.4+, make, python and a couple of other vim plugins required.
After that, things can start getting pretty nice. For (my only public) example, https://github.com/mavnn/Advent2014 shows how you can use fsx scripts and paket (a package manager compatible with nuget.org and taking source dependencies from github) to create a nice little project without needing to get into any of the Visual Studio project file nastiness. Of course, if you need to work on an existing project, the Vim bindings know about how to handle that too - but actually editing project files is still a pain.
One word of caution: there's currently a bug in the packaging for rpm: I'd go with Debian/Ubuntu packages at the moment. And as a final option, building from source is slow but has become pretty reliable over the last year or so.