<<26-03-2013>>

00:08:01*q66 quit (Remote host closed the connection)
01:00:21*Trixar_za is now known as Trix[a]r_za
01:17:44*reactormonk quit (Ping timeout: 255 seconds)
08:12:57*reactormonk joined #nimrod
09:25:41*xcombelle joined #nimrod
11:22:54*XAMPP_ quit (Quit: My code has no bug's, just random features)
11:23:13*XAMPP joined #nimrod
11:23:13*XAMPP quit (Changing host)
11:23:13*XAMPP joined #nimrod
12:52:32*q66 joined #nimrod
15:50:22*xcombelle quit (Read error: Connection reset by peer)
17:44:27*q66 quit (Read error: Connection reset by peer)
18:08:25*q66 joined #nimrod
18:11:02dom96hi
18:11:57reactormonkmorning
18:12:26dom96reactormonk: Read our convo about GSoC yesterday?
18:13:37reactormonkdom96, nope, had to restart the IRC
18:13:43reactormonkgimme link to pastie log
18:13:48reactormonkgotta run to lecture... somewhat of.
18:14:30dom96http://build.nimrod-code.org/irclogs/25-03-2013.html
18:15:35reactormonkgood
18:16:02dom96Are you interested?
18:16:26dom96Tell Araq and he will sign up as an "organisation" and then you can work on Nimrod ;)
18:51:29*Araq wonders how he can sign up as an "organization" ...
18:52:56dom96read the FAQ
19:01:35Araqdom96: link?
19:05:47dom96http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs
19:08:16Araqactually I'd like a GSoC about better Nimrod <-> C++ interaction
19:08:27Araqthis could mean swig support for nimrod
19:08:36Araqor improving c2nim to deal with c++
19:09:04dom96You can do that I think
19:10:19dom96So this surfaced on reddit/HN today. I was quite happy to see Nimrod there: http://www.compileonline.com
19:10:27dom96The site seems to be broken already though
19:15:08dom96It doesn't seem to be doing any sandboxing at all
19:18:11Araqplus it only ships with an archaic 0.8.14
19:19:08Araqinteresting though they don't consider the language usable without strutils ... :P
19:19:45dom96The website doesn't seem to do much sandboxing.
19:19:51dom96Unless all the apps run in a VM.
19:20:07Araqthat's what I'd guess
19:20:39Araqwe should remove the jvm with a Nimrod program
19:20:49dom96lol
19:20:54Araqand watch lots of languages die :P
19:21:07dom96Many languages already fail
19:21:20dom96Thanks to Nimrod's few dependencies it works perfectly :D
19:22:00Araqor maybe nobody bothered to destroy the nimrod installation ...
19:22:11dom96lol
19:22:28dom96quick write an app which will make Nimrod auto replicate!
19:24:41fowlcan we update their nimrod? :D
19:25:27Araqhmm
19:25:54dom96lol
19:25:57dom96Good idea!
19:35:33reactormonkdom96, about good
19:44:48dom96what?
19:45:42reactormonkdom96, the GSoC
19:46:11dom96Sorry, I don't follow.
19:52:36reactormonkdom96, read the part, have fun setting that up. Or as I see it, it's Araq having the fun.
19:53:06AraqI'm always having fun here ... :P
19:57:46dom96bbl
20:05:00reactormonkAraq, gimme a wallet ID so I can send your bitoin
20:11:32Araqreactormonk: it feels unfair to get a bitcoin before I fixed that closure bug ...
20:12:28reactormonkAraq, then gimme and I'll send as soon as you're done - that's what I intended anyway ;-)
20:26:39reactormonkAraq, GSoC - https://github.com/Araq/Nimrod/issues/371 would be a project?
20:28:32Araqsure
20:28:38Araqalbeit a rather boring one :P
20:29:48reactormonkwhy so?
20:33:32Araqthe current JS backend targets some very old version of JS that should even be supported by IE 6
20:34:17Araqsupporting asm.js etc. makes it too fancy, we may as well target the NaCl stuff IMHO
20:34:55reactormonkso both?
20:38:51Araqactually I think NaCl is a much better than bolting low level stuff on JS
20:39:14Araqbut I guess asm.js will win
20:39:23reactormonkwhy so?
20:39:41Araqbecause it's worse
20:39:49Araqand worse always wins ;-)
20:41:06reactormonksimpler?
20:44:00Araqsimple has not much to do with it
20:44:59Araqit's about backwards compatibility
20:46:51reactormonkoh
21:16:51*gradha joined #nimrod
21:44:02Araqso ... dom96 ... apparently go doesn't deal with versioning
21:44:38Araqinstead you can import an url
21:44:51Araqwell not really afaik
21:45:21Araqurls are mapped to local filesystem paths
21:45:44Araqand you can update them with "go install url"
21:50:19AraqI must say I like this solution ... no versioning crap that nobody will get right anyway
21:51:05dom96hrm
21:51:07gradhait's like... git submodules... genius!
21:51:12reactormonkAraq, or you could enforce same exported procs via code analysis when minor number is the same ;-)
21:51:48gradhawouldn't that be part of babel?
21:51:57reactormonkgradha, sure
21:52:02gradhamaybe the exported procs could be hashed and that would be part of the version
21:52:22reactormonkbut it should be ok to add new stuff
21:52:23gradhathough adding stuff doesn't necessarily break stuff, yet changes hash
21:52:55gradhaplus you can change the behaviour of a proc without changing its signature and spread chaos anyway
21:53:00dom96What if your app is dependent on semantics of a particular version not just exported procs?
21:53:04reactormonkgradha, sure you can
21:53:09Araqanother idea of mine was to simply hardcode the version number like "import xyz version 0.9"
21:53:32reactormonkdom96, exactly.
21:53:37Araqand then let the linker deal with the resulting code duplication
21:54:00Araqit has means to merge identical procs anyway; C++ templates require it
21:54:45Araqbut then your hd fills up with all versions of a package very quickly .. ;-)
21:55:04gradhaholy cow, I had forgotten how fast the compiler is being used to run it in debug mode
21:55:36Araqgradha: factor 10 ;-)
21:56:05Araqso Nimrod in excessive debug mode is still 2-4x faster than Python :P
21:57:18gradhaI see now why you didn't mind .tmpl files being recompiled
21:58:17dom96hrm, Aporia needs Nimrod Template highlighting.
22:06:40gradhadom96: maybe you can steal https://github.com/zah/nimrod.vim/issues/6 for Aporia
22:09:25dom96You just stole it from me! :P
22:09:37dom96You Vim sinner!
22:09:40gradhawhat, does Aporia do that?
22:10:04dom96no. But I just said that it needs it :P
22:10:33gradhano problem, the idea is pretty obvious, it's the implementation which counts
22:11:28dom96The shebang could be inspected.
22:12:01dom96"shebang" is also one of the funniest terms I know.
22:40:00gradhawhy does jester sometimes fail with "Could not bind socket, retrying in 30 seconds", is it the OS not freeing sockets properly or something?
22:42:15dom96It's a thing that all OS' do. It can be gotten around by setting the SO_REUSEADDR flag, but I still have not gotten around to providing the functionality to do that.
23:50:49*gradha quit (Quit: bbl, have youtube videos to watch)