These are chat archives for akkadotnet/akka.net

30th
Jan 2015
Bartosz Sypytkowski
@Horusiath
Jan 30 2015 16:10
Since Akka.NET F# API wiki page is strongly outdated could we use README content after the next release?
also, I've pushed my Akka.Persistence branch to upstream
Roger Johansson
@rogeralsing
Jan 30 2015 16:43
Awesome! Absolutely Im in the process of changing the site generator to handle local repo docs. Will fix after that
Avo M
@avoxm
Jan 30 2015 17:49
@Aaronontheweb thanks will have look at it
Avo M
@avoxm
Jan 30 2015 18:01
Ok, I'l port the Guard class from Helios to Akka under Akka.Util
Aaron Stannard
@Aaronontheweb
Jan 30 2015 18:21
@mmisztal1980 I think it's cool that they released Orleans
anything to start getting .NET developers thinking about distributed systems and the actor model is a force for good
the Orleans development model is weird though - every time I talk to someone who's tried using it I find out some awkward new thing it does that I didn't know before
so I think it's good for developers to have a choice in their tools for things as heavy-duty as distributed actor systems :sparkles:
@avoxm thanks Avo! I appreciate it.
@rogeralsing are we going to publish the GhostDoc / NDoc stuff online at some point? Kind of like how Scala does for the API reference?
I'd like to use that type of versions API reference docs deep linking when I'm writing blog posts about specific Akka.NET features
versioned*
Roger Johansson
@rogeralsing
Jan 30 2015 18:26
I think we should. Not sure what the best tool is for generating the pages though, most seems old and not up to date
Aaron Stannard
@Aaronontheweb
Jan 30 2015 18:27
it'd be cool if there was a tool that could generate versioned Jekyll pages based on the XML-DOC comments for each git-tag in the central repo
i.e. it could automatically generate the doc pages for all versions of Akka.NET that have ever existed
Roger Johansson
@rogeralsing
Jan 30 2015 18:27
That would be awesome!
Aaron Stannard
@Aaronontheweb
Jan 30 2015 18:28
in fact, that's one of those things that seems so obvious it makes me wonder if that already exists lol
you'd have to think that every big Java project on Github has this sort of problem, right?
Roger Johansson
@rogeralsing
Jan 30 2015 18:29
Our current site generator runs on nodejs (my hack) couldnt stand the buggy tools for Jekyll
Aaron Stannard
@Aaronontheweb
Jan 30 2015 18:29
so you're one of those hipster Node.JS developers now eh? :shipit:
just kidding - Node is cool
Roger Johansson
@rogeralsing
Jan 30 2015 18:30
Yepp :)
Its a mini port of Jekyll , semi compatible. Love the npm eco system
Took a few h to get generation, liquid tag support , markdown, etc up and running
Aaron Stannard
@Aaronontheweb
Jan 30 2015 18:32
I love NPM too - when I was evaluating Cassandra / MongoDB / Riak as alternatives for migrating off of RavenDB for MarkedUp I found it was super easy to do rapid prototypes in Node. All of the drivers are pretty current
and it's easy to write your own quick and dirty streaming service for moving lots of data from one place to another
Aaron Stannard
@Aaronontheweb
Jan 30 2015 22:07
thanks for the PR, @avoxm - that will help me and @smalldave with a bunch of the assertions we need to make for the multinode tests