/srv/irclogs.ubuntu.com/2014/06/13/#ubuntu-arm.txt

=== heathkid|2 is now known as heathkid
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
suihkulokkiawafaa: pretty much05:14
=== chihchun is now known as chihchun_afk
=== doko_ is now known as doko
awafaasuihkulokki: thanks for the confirmation, so in your view what langs are high/medium/low priority?11:13
infinityawafaa: c,c++,java/go,gchi,erlang,ocaml/everything-else, intentionally leaving out purely interpreted languages that seem to generally Just Work (perl, python, etc).11:16
infinityawafaa: And probably missing a lot of random favourites from others. :P11:16
awafaainfinity: who asked you?! :P11:17
awafaainfinity: i was thinking more of what's the priority for langs that need porting?11:17
infinityawafaa: I figured our relationship was intimate enough that I could interject.  I have photos to prove it.11:17
awafaainfinity: you seen my outfit for the next connect?11:17
infinityawafaa: I'm not sure I want to...11:17
infinityawafaa: 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.11:18
awafaainfinity: guess what? you're going to https://plus.google.com/u/0/103092666279088875227/posts/aCtNPvQdHt111:18
infinityawafaa: 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.11:18
infinityawafaa: Dude, if your junk can maintain that contraption in place through an entire evening, more power to you.11:19
awafaainfinity: so far the only high priority one i have is go11:19
infinityawafaa: 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.11:21
infinityawafaa: So, not a priority at all, but perhaps a fun project for someone.11:22
suihkulokkiawafaa: 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 languages11:22
infinityawafaa: 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.11:23
awafaayeah, 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 on11:23
awafaainfinity: you need to take that up with joyent11:24
suihkulokkichasing 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 system11:24
infinitysuihkulokki: I doubt anyone would make a purchasing decision based on pascal, to be fair.11:24
infinityBut nodejs, definitely.  And saying "there will be a new upstream release some day with support" doesn't cut it.11:24
awafaasuihkulokki: I agree, but I have to prioritise - I have the list of things that need work, I just need to prioritise it11:25
infinityawafaa: What does joyent have to do with it?11:25
awafaainfinity: they have an exceptional amount of say in node - they just canned the CLA, but still have a lot to say11:27
infinityawafaa: "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. :P11:27
infinityAnd 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.11:29
suihkulokkiit's in node.js master - * v8: upgrade to 3.24.35.2211:30
infinitysuihkulokki: So, maybe I'll see that release before 16.04 ... I'd still love to see a backport to 3.14 for 14.0411:31
infinityBut, *shrug*...11:32
suihkulokkithey don't seem to have release schedule11:33
infinityAnyhow, I'm not going to lose any sleep over it.  Just a bit disappointing.11:33
suihkulokkioddly I'd assume something as hipster and trendy as node being released monthly or so11:34
infinityThey don't do the hipster release thing.11:34
infinityThey also maintain stable branches for effin' ever.11:34
infinityWhich I appreciate, as a stuffy conservative engineer.11:34
infinityBut their reluctance to cut a new stable out of master is also irksome. :P11:35
suihkulokkiI think theyll still manage to release faster than awafaa is able to find someone to do the backport of v8 :F11:37
awafaaalmost definitely :/11:38
infinityPerhaps a fair point.11:40
infinityawafaa: 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.11:41
hrwinfinity: ocaml is ported11:42
awafaainfinity: i've been trying to work out what actually uses ghci? and when yoiu guys were porting ghc, why do a half arsed effort? :P11:43
infinityhrw: I know, I was listing priorities period, before he narrowed it to discussing unported things. :P11:43
hrwok11:43
infinityawafaa: Colin's GHC port isn't native, it's more just a dirty hack.11:43
infinityhttp://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2014/04/1511:43
awafaaah, that's not what all the noise said - thanks for the clarification11:44
suihkulokkihttps://ghc.haskell.org/trac/ghc/wiki/Platforms11:48
=== dk is now known as Guest61140
=== chuck__ is now known as zul
=== mhaberler_ is now known as mhaberler

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!