**** BEGIN LOGGING AT Fri Jun 13 02:59:59 2014 Jun 13 05:14:56 awafaa: pretty much Jun 13 11:13:59 suihkulokki: thanks for the confirmation, so in your view what langs are high/medium/low priority? Jun 13 11:16:05 awafaa: c,c++,java/go,gchi,erlang,ocaml/everything-else, intentionally leaving out purely interpreted languages that seem to generally Just Work (perl, python, etc). Jun 13 11:16:28 awafaa: And probably missing a lot of random favourites from others. :P Jun 13 11:17:02 infinity: who asked you?! :P Jun 13 11:17:28 infinity: i was thinking more of what's the priority for langs that need porting? Jun 13 11:17:31 awafaa: I figured our relationship was intimate enough that I could interject. I have photos to prove it. Jun 13 11:17:48 infinity: you seen my outfit for the next connect? Jun 13 11:17:59 awafaa: I'm not sure I want to... Jun 13 11:18:35 awafaa: So, with a Canonical hat on, I'd say golang would be a high priority, taking that hat off, a proper ghci port would make a lot of nerds happy. Jun 13 11:18:37 infinity: guess what? you're going to https://plus.google.com/u/0/103092666279088875227/posts/aCtNPvQdHt1 Jun 13 11:18:58 awafaa: a native erlang port wouldn't go amiss, but I've also not (yet) heard people complaining about the performance impact of not having it. Jun 13 11:19:52 awafaa: Dude, if your junk can maintain that contraption in place through an entire evening, more power to you. Jun 13 11:19:58 infinity: so far the only high priority one i have is go Jun 13 11:21:40 awafaa: There are also stragglers, like fpc, that don't have a ton of users but would probably also take someone with the right intersection of skills (pascal and ARM, in fpc's case) an afternoon to fix. Jun 13 11:22:12 awafaa: So, not a priority at all, but perhaps a fun project for someone. Jun 13 11:22:26 awafaa: my personal opinion is that it's quite low - but it would be still good to have someone assigned to working on porting/optimizing more esoteric languages Jun 13 11:23:22 awafaa: Oh, and v8/node! I understand there's an AArch64 port sitting on tip/trunk/head/whatever somewhere, but that's of little use while distros are still shipping an old stable libv8 and node to match. Jun 13 11:23:34 yeah, problem is getting resources to assign to do the work - I have very little to play with so I have to be very picky with what I put it on Jun 13 11:24:03 infinity: you need to take that up with joyent Jun 13 11:24:04 chasing the long tail and all - it should be made sure at least the languages work so nobody doesn't skip buying and armv8 server because they happen to have a legacy freepascal app as part of their system Jun 13 11:24:38 suihkulokki: I doubt anyone would make a purchasing decision based on pascal, to be fair. Jun 13 11:24:54 But nodejs, definitely. And saying "there will be a new upstream release some day with support" doesn't cut it. Jun 13 11:25:12 suihkulokki: I agree, but I have to prioritise - I have the list of things that need work, I just need to prioritise it Jun 13 11:25:37 awafaa: What does joyent have to do with it? Jun 13 11:27:45 infinity: they have an exceptional amount of say in node - they just canned the CLA, but still have a lot to say Jun 13 11:27:52 awafaa: "porting" nodejs to a new arch is trivial. libv8, on the other hand, is painful. And last time I asked about backporting aarch64 support to libv8-3.14 (ie: the version most everyone ships), I was told it was "too much effort", and thus no one cared. Which seems like a pretty lousy thing to tell potential customers. :P Jun 13 11:29:23 And sure, some day there will be a node/v8 combo based on 3.20 or 3.22 or something, but that doesn't help me today. Jun 13 11:30:41 it's in node.js master - * v8: upgrade to 3.24.35.22 Jun 13 11:31:54 suihkulokki: So, maybe I'll see that release before 16.04 ... I'd still love to see a backport to 3.14 for 14.04 Jun 13 11:32:05 But, *shrug*... Jun 13 11:33:10 they don't seem to have release schedule Jun 13 11:33:39 Anyhow, I'm not going to lose any sleep over it. Just a bit disappointing. Jun 13 11:34:02 oddly I'd assume something as hipster and trendy as node being released monthly or so Jun 13 11:34:18 They don't do the hipster release thing. Jun 13 11:34:25 They also maintain stable branches for effin' ever. Jun 13 11:34:39 Which I appreciate, as a stuffy conservative engineer. Jun 13 11:35:11 But their reluctance to cut a new stable out of master is also irksome. :P Jun 13 11:37:43 I think theyll still manage to release faster than awafaa is able to find someone to do the backport of v8 :F Jun 13 11:38:49 almost definitely :/ Jun 13 11:40:58 Perhaps a fair point. Jun 13 11:41:37 awafaa: So, discounting the node/v8 argument, and understanding that you already have people prioritising golang (or, you might do), I'd say that ghci is pretty widely-used and often-ignored. Jun 13 11:42:20 infinity: ocaml is ported Jun 13 11:43:11 infinity: i've been trying to work out what actually uses ghci? and when yoiu guys were porting ghc, why do a half arsed effort? :P Jun 13 11:43:21 hrw: I know, I was listing priorities period, before he narrowed it to discussing unported things. :P Jun 13 11:43:25 ok Jun 13 11:43:41 awafaa: Colin's GHC port isn't native, it's more just a dirty hack. Jun 13 11:43:47 http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2014/04/15 Jun 13 11:44:22 ah, that's not what all the noise said - thanks for the clarification Jun 13 11:48:19 https://ghc.haskell.org/trac/ghc/wiki/Platforms **** ENDING LOGGING AT Sat Jun 14 02:59:58 2014