Comments on: Past and Future libraries

By: wumpwoast

wumpwoast — Tue, 24 Jun 2008 23:07:17 +0000

I’m going to get Abuse netplay working, and maybe conceive of a 2D interpolation technique such that I can update server-state 3 times per second rather than every 15 (once per frame).

That means 300ms ping would be acceptable versus the 66ms that’s currently desirable. Think I can get it done this year?

By: tommd

tommd — Thu, 19 Jun 2008 22:25:30 +0000

Ivan:
Sounds neat, will you be putting your work on hackage or perhaps a respository at code.haskell.org?

Gwern:
Yes, I ran into that. I’m not sure if I want to implement an overlay/distributed P2P network or an ad hoc network (as in, MANET). I’ll have to read the associated IETF internet draft to get a feel for how this p2p is setup, should be fun!

By: Ivan Miljenovic

Ivan Miljenovic — Thu, 19 Jun 2008 15:28:52 +0000

.cabal parser: For my honours project in maths this year, I’m actually doing a project which will involve graph-theoretic analysis of Haskell code and modules, quite possibly using the .cabal file to determine what modules to examine. Not sure how much visualisation will be done though.

By: gwern

gwern — Thu, 19 Jun 2008 02:37:43 +0000

Re: future stuff:

.cabal parser: I would just go the pure Haskell route. The GUI stuff is probably handled already by a library like diagrams, and once you’ve parsed the .cabal (the hardest part IMO, the part GraphViz wouldn’t help with), would manipulating the graphs be all that difficult?

P2P: You really need to check out Barracuda and its supporting libraries.