<< 14-02-2015 >>

00:03:22*pafmaf quit (Quit: This computer has gone to sleep)
00:04:59*vendethiel joined #nim
00:29:21*vendethiel quit (Ping timeout: 252 seconds)
00:30:30*vendethiel joined #nim
00:37:58*VinceAddons quit (Read error: Connection reset by peer)
00:52:43*brson joined #nim
00:53:25*BlaXpirit quit (Quit: Quit Konversation)
00:54:17*vendethiel quit (Ping timeout: 264 seconds)
00:57:36*brson quit (Client Quit)
01:02:45*Jesin quit (Quit: Leaving)
01:07:01*Jesin joined #nim
01:08:50*n4ird4 joined #nim
01:09:47*Etheco quit (Read error: Connection reset by peer)
01:12:06*fungos quit (Remote host closed the connection)
01:17:59*Etheco joined #nim
01:23:00whitenoiseAraq: i don't have a ton of time, but what opportunities are there for contribution to the project? seems like there's a lot of wheels turning, still.
01:25:02*vendethiel joined #nim
01:25:18whitenoisemy experience includes networking knowhow, at least regarding TCP/IP and routing, etc, which I doubt is of any use. I'm an intermediate sort of developer, and I am primarily an Infrastructure/Linux Engineer that wears a Security Engineer hat for configuration/changes and whitebox pen testing.
01:25:45whitenoiseoh, and I have some years of working for web agencies, so I'm familiar with web concepts, too.
01:26:33whitenoisemy shortcoming is time :)
01:27:00Araqwhitenoise: well we still have over 400 bugs open
01:27:09Araqsome of which are marked "easy"
01:27:16whitenoiseso I could learn Nim whilst bug fixing
01:27:21Araqwhich admittedly ... is er
01:27:34Araqwell I think "that's easy" and it usually turns out it's not
01:27:39whitenoisehaha
01:27:46Araqbut ... it still is a good starting point, I think
01:27:56whitenoisethis is in GitHub issues under nim-lang, I guess?
01:28:04Araqyes
01:28:23Araqstdlib bugs are also a good starting point
01:28:43*n4ird4 left #nim ("WeeChat 1.0.1")
01:28:59AraqI need to sleep, good night and welcome on board!
01:29:07whitenoisenight, Araq and thanks
01:34:30reactormonkwhitenoise, actually it's under Araq/nim
01:43:17dom96whitenoise: https://github.com/Araq/Nim/labels/Easy
01:48:13whitenoisedom96: i looked for Easy + stdlib, and found the ssl stuff
01:48:52*fungos_ joined #nim
01:49:14whitenoiselooks like people have already been touching that, though
01:49:28whitenoiseat any rate, apparently i am now cooking dinner, so coding time is over before it began.
01:51:59*quasinoxen joined #nim
01:57:56*darkf joined #nim
01:59:57whitenoisedom96: as far as contribution process, is it just fork, code, pull request? I see there is a diff output in the GitHub comments, which to me seems not the best way to deliver, but is that the norm?
02:00:38*fungos_ quit (Remote host closed the connection)
02:03:10*fungos_ joined #nim
02:06:30*reem quit (Remote host closed the connection)
02:07:02*reem joined #nim
02:11:17*reem quit (Ping timeout: 246 seconds)
02:12:25*vendethiel quit (Ping timeout: 264 seconds)
02:13:01*reem joined #nim
02:13:51*vendethiel joined #nim
02:14:13*chemist69_ joined #nim
02:17:11*chemist69 quit (Ping timeout: 246 seconds)
02:18:22*reem quit (Remote host closed the connection)
02:23:50*reem joined #nim
02:25:43filwitwhitenoise: fork, code, PR. yep.
02:29:07infinity0Araq: no, i'm not joking
02:29:18infinity0Debian doesn't actually routinely run 40k of autogenerated autoconf scripts
02:29:28infinity0we use dh-autoreconf to regenerate them from configure.ac etc
02:30:04infinity0please at least re-open the issue, you didn't explain why it's invalid
02:30:17infinity0if you don't want to fix it yourself, you can at least leave it open so others can see it's a problem
02:32:53infinity0in general, upstreams that bundle autogenerated code, we delete that and regenerate them from the real sources
02:35:39infinity0https://github.com/nim-lang/csources/issues/12 for others' reference
02:36:41*fungos_ quit (Ping timeout: 256 seconds)
02:37:22*gokr quit (Quit: Leaving.)
02:37:37*jsudlow quit (Quit: Leaving)
02:39:36*filwit quit (Quit: Leaving)
02:40:41*fungos_ joined #nim
02:41:47*jsudlow joined #nim
02:54:01*leonlee quit (Read error: Connection reset by peer)
02:54:18*leonlee joined #nim
02:55:48*vendethiel quit (Ping timeout: 245 seconds)
03:01:46infinity0Araq: so for example, to bootstrap GCC you need an existing C compiler (unknown trust), but then you compile GCC's source code (which is human-reviewable, i.e. verifiable/trustworthy) with it
03:02:40infinity0by contrast, with nim, we must use some external tools (unknown trust, nim not responsible for this) to compile autogenerated source code (unknown trust, nim responsible for this)
03:04:39infinity0this is not an ideal situation, and not something that the builder should be responsible for solving, since the autogenerated code is an intrinsic part of the upstream build process
03:05:27infinity0it's reasonable for builders (e.g. Debian) to be responsible for providing external tools that can be trusted, but that's not the target of my complaint here
03:09:45*reem quit (Remote host closed the connection)
03:13:38reactormonkinfinity0, there's no way to you can get the generated code to be human-readable
03:13:50reactormonknot without any unreasonable effort at least
03:16:30infinity0reactormonk: hmm, could you tell me which parts of the nim source code, generate csources?
03:16:46reactormonkinfinity0, the compiler. look for "rope" instances
03:19:35*reem joined #nim
03:23:21infinity0reactormonk: what about the first version of the nim compiler, that would originally have been written in another language?
03:23:27reactormonkinfinity0, pascal
03:23:54reactormonka subset of it, actually
03:24:19flaviuinfinity0: It's impractical to read the C sources, there's lots of code generation there through iterators, templates, macros.
03:26:43*vendethiel joined #nim
03:27:04flaviuHonestly, I don't see a good solution here. A trusting trust attack is possible, but I'd think that an obfuscated backdoor would be a thousand times easier to implement and therefore would be a more likely target.
03:29:14infinity0by that, you mean a backdoor in the source code? it would be easier to implement, but also harder to hide
03:29:35infinity0i guess nim doesn't try to translate to any higher-level languages, only C
03:29:57flaviuIt also translates to C++
03:30:06flaviuAnd javascript, but IIRC that's buggy.
03:30:34reactormonkinfinity0, even if it would, it's not a source-to-source compiler
03:31:42flaviuIt would be harder to hide, but given that only 2-3 people actually regularly look at the internals of the compiler, it wouldn't be too obvious.
03:32:02flaviuThe Underhanded C contest has shown there are plenty of non-obvious ways to backdoor things.
03:32:56infinity0but that's still more than the 0 people who actually try to figure out what csources actually does
03:33:18infinity0anyway, i appreciate this is a hard problem that probably doesn't seem high priority, i will keep looking into it
03:33:33reactormonkinfinity0, I see your point, but it would require immense resources to tackle it
03:34:00reactormonkinfinity0, so recursive bootstrapping from pascal would be reasonable?
03:34:13flaviuThat sounds like a major PITA
03:34:35infinity0i'd need to think about that. maybe, maybe not, depending on the details of whatever is feasible
03:34:54*nande quit (Remote host closed the connection)
03:35:17infinity0also i can look into how other thigns
03:35:27infinity0er, whoops. how other languages do (or don't do) it
03:37:07flaviuI was just thinking of that.
03:42:53*quasinoxen quit (Ping timeout: 264 seconds)
03:43:19*infinity0_ joined #nim
03:43:19*infinity0_ quit (Changing host)
03:43:19*infinity0_ joined #nim
03:43:19*infinity0 quit (Killed (verne.freenode.net (Nickname regained by services)))
03:43:20*infinity0_ is now known as infinity0
03:45:56*reem quit (Remote host closed the connection)
04:14:34*vendethiel quit (Ping timeout: 250 seconds)
04:17:42*vendethiel joined #nim
04:39:25*vendethiel quit (Ping timeout: 250 seconds)
04:41:37*jferg2010 joined #nim
04:44:05*vendethiel joined #nim
04:46:44*fungos_ quit (Remote host closed the connection)
04:56:30jferg2010def-: I saw the reference to documentation on the GSoC 2015 wiki entry. What's the state of documentation and related tools? Is someone actively working on that?
04:59:49*matiaslina joined #nim
05:04:08reactormonkjferg2010, kinda meh.
05:04:41reactormonkjferg2010, https://github.com/Araq/Nim/labels/Documentation
05:05:52*vendethiel quit (Ping timeout: 240 seconds)
05:09:49jferg2010reactormonk: Thanks for the link. Let me look through the list and see where I might be able to help.
05:16:34Varriountonionhammer: Good news. I've found a way lessen the number of callbacks that need to be created for interacting with the sublime api
05:20:43*vendethiel joined #nim
05:22:09*saml_ quit (Quit: Leaving)
05:26:22*infinity0 quit (Ping timeout: 240 seconds)
05:29:35*infinity0 joined #nim
05:45:42*vendethiel quit (Ping timeout: 245 seconds)
05:51:29*vendethiel joined #nim
06:06:41*wb quit (Ping timeout: 252 seconds)
06:10:13*jferg2010 quit (Quit: Leaving)
06:11:16*matiaslina quit (Quit: Lost terminal)
06:22:58*leonlee quit (Quit: Leaving)
06:23:52*notfowl joined #nim
06:25:02*fowl joined #nim
06:27:36*fowlmouth quit (Ping timeout: 250 seconds)
06:28:19*notfowl quit (Ping timeout: 252 seconds)
06:37:30*reem joined #nim
06:37:43*vendethiel quit (Ping timeout: 250 seconds)
06:43:22*reem quit (Remote host closed the connection)
06:49:24*reem joined #nim
06:52:28*ARCADIVS joined #nim
06:57:06*vendethiel joined #nim
07:08:22*johnsoft quit (Ping timeout: 240 seconds)
07:08:45*johnsoft joined #nim
07:14:25*NimBot joined #nim
07:24:26*phI||Ip_ joined #nim
07:28:06*chemist69_ quit (*.net *.split)
07:28:08*phI||Ip quit (*.net *.split)
07:29:09*EastByte_ is now known as EastByte
07:33:57*gunn joined #nim
07:35:41*gunn_ quit (Ping timeout: 264 seconds)
07:49:44*chemist69_ joined #nim
08:03:27*reem quit (Remote host closed the connection)
08:10:47*reem joined #nim
08:18:42*panzone joined #nim
08:21:21*panzone quit (Client Quit)
08:24:51*reem quit (Remote host closed the connection)
08:31:47*BlaXpirit joined #nim
08:33:16*reem joined #nim
08:39:15*reem quit (Remote host closed the connection)
08:39:50*reem joined #nim
08:45:54*dumdum joined #nim
08:54:48*JinShil joined #nim
09:11:29*JinShil quit (Quit: Konversation terminated!)
09:27:46Araqinfinity0: what is realistic is to review the generated C code. it's not *impossible* to follow with some experience.
09:34:38Araqthat said, I don't see how reviewing GCC's source for backdoors helps with anything when you used an untrusted binary to compile it ...
09:35:16Araqthe point of Thompson's paper was to show that's futile
09:40:13*reem quit (Remote host closed the connection)
09:43:26*Matthias247 joined #nim
09:51:10*reem joined #nim
10:03:00*reem quit (Remote host closed the connection)
10:04:21*dumdum quit (Ping timeout: 256 seconds)
10:05:59*reem joined #nim
10:15:06*VinceAddons joined #nim
10:16:42*dumdum joined #nim
10:16:47*reem quit (Remote host closed the connection)
10:17:51*gokr joined #nim
10:22:49*kuzy000_ joined #nim
10:24:54*JinShil joined #nim
10:30:42*pafmaf joined #nim
10:35:21*gunn quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
10:41:52*gunn joined #nim
11:15:56*johnsoft quit (Ping timeout: 265 seconds)
11:16:21*johnsoft joined #nim
11:39:19*Trustable joined #nim
11:57:36*OnwardEuler joined #nim
12:20:55*dumdum quit (Ping timeout: 256 seconds)
12:28:12*pafmaf quit (Quit: This computer has gone to sleep)
12:39:18*dumdum joined #nim
12:41:29*wb joined #nim
12:53:42infinity0Araq: it helps, because you can use other techniques such as diverse double compilation to deal with the issue of "untrusted external tools", thompson's attack is not actually futile to defend against
12:55:15infinity0however, if the bootstrap source code is itself not reviewable, then making sure you have (effectively) clean building tools, doesn't achieve the overall goal of a clean resulting binary
12:56:35Araqit's as reviewable as GCC's source code ... ;-)
12:56:52Araqit's also less code to review than GCC
12:57:20Araqit's still an exercise in masochism, of course
12:58:47*ARCADIVS quit (Quit: ARCADIVS)
12:59:06*sillesta joined #nim
13:00:44Araqbut masochism is definitely helpful when you care about security in a system consisting of millions of lines of C code (called kernel) which embraces programs communicating via untyped byte streams and string evalutation purposes (called userspace)
13:01:48Araqsecurity in a unix based system is a staircase wit.
13:10:01dom96hello
13:12:29*dumdum quit (Ping timeout: 256 seconds)
13:17:23*reem joined #nim
13:21:55*reem quit (Ping timeout: 252 seconds)
13:43:24gokrhey
13:43:44*dumdum joined #nim
13:47:16*Sornaensis quit (Excess Flood)
13:47:44*Sornaensis joined #nim
13:47:44*Sornaensis quit (Excess Flood)
13:48:37*Sornaensis joined #nim
13:49:12sillestahey
13:59:07*gunn_ joined #nim
14:00:03*gunn quit (Ping timeout: 252 seconds)
14:02:10*BlaXpirit quit (Read error: Connection reset by peer)
14:03:10*BlaXpirit joined #nim
14:10:51*dumdum quit (Ping timeout: 256 seconds)
14:11:13*wb quit (Ping timeout: 264 seconds)
14:26:24*Matthias247 quit (Read error: Connection reset by peer)
14:31:14*zahary1 joined #nim
14:32:41*zahary quit (Ping timeout: 252 seconds)
14:35:28*JinShil quit (Quit: Konversation terminated!)
14:36:23*gunn_ quit (Quit: Textual IRC Client: www.textualapp.com)
14:53:00*NimBot joined #nim
15:02:52*davidhq joined #nim
15:04:57dom96Just deployed some fixes and functionality to the Nim Forum. Biggest addition is the ability to deactivate your account as well as the ability for admins to ban users.
15:05:39*davidhq quit (Client Quit)
15:10:51*dumdum joined #nim
15:18:20*gXen joined #nim
15:18:41gXenrustix will be written in nim.. nice job guys
15:20:56def-gXen: yeah, tried it out already, doesn't seem to be doing much so far except print a full screen of characters
15:25:36*wb joined #nim
15:28:50*gokr quit (Ping timeout: 250 seconds)
15:38:40*gokr joined #nim
15:38:45*filwit joined #nim
15:41:39filwitdom96: hey do you think I should add the "build server" side-nav link back to the website? It was on my original design (in case you forgot what it looked like): http://www.reign-studios.net/philipwitte/nim/
15:42:04filwitdom96: it could just point to the build waterfall the github repo has
15:45:19federico3oh look at that:
15:45:22federico3https://github.com/ckkashyap/rustix/issues/8
15:46:45dom96filwit: Sure. It would be awesome if you could fix layout issues on the forum.
15:47:10dom96like the page numbers overflowing to the next line on the main page
15:47:42filwitdom96: yeah that's something that's been bugging me too. will get to it
15:47:54dom96filwit: http://i.imgur.com/AjNnrn6.png
15:48:00filwitaraq said he want's more space between paragraphs as well
15:48:24*chemist69_ quit (Quit: WeeChat 1.1.1)
15:50:26filwitdom96: it's a bit tricky to fix the numbers from rolling over (since both the numbers and title expand dynamically) but I'm sure I can figure something out. The alternative is to leave the numbers wrapping but have the black box on the right expand correctly (that's easy)
15:51:28dom96filwit: yeah, the latter might be better.
15:51:38dom96I couldn't figure out how to do the latter either though heh
15:52:10filwityou have to use position:relative + top, right, left, bottom :)
15:52:38filwitthat makes it easy to snap all the edges where you need them relative to the parent
15:52:55filwitbut i'll look into fixing the numbers first, cause that would be best, visually IMO
15:54:29filwitbtw dom, nice work on the search and login panel
15:54:34filwitlooks good (fits in well)
15:54:38dom96thanks :)
16:01:01*gXen quit ()
16:03:34whitenoiseah, rustix, nice, imo nim is a way better kernel language than rust
16:03:48whitenoisei was actually pondering that on my way home from work yesterday
16:05:20*HakanD joined #nim
16:07:32filwitdom96: mind if I change the RSS icon to something more iconic? (ie, a single-color black RSS symbol, visually similar to the view/post symbols)
16:07:43dom96filwit: nope, go ahead.
16:10:35*chemist69 joined #nim
16:20:39filwitdom96: there's no need to have two JS files (since one just calls the single function of the other), we should combine them. Keep the 'forum.js' name or 'arrow.js'?
16:21:00dom96forum.js
16:21:02filwitk
16:22:48filwitoooohhhhh... i could make custom smileys :D
16:23:27filwiti'm not sure I understand why you divided up the graphics though.. You link to the Nim logo from the website, but not the background, head, nav, etc... why?
16:23:53filwit(wait, who made those smileys... dont' want to overwrite your work if you made them)
16:24:56filwitalso the JS is duplicated in the CSS folder... hrm
16:24:56*dumdum quit (Read error: Connection reset by peer)
16:25:33*dumdum joined #nim
16:25:39*johnsoft quit (Ping timeout: 245 seconds)
16:25:47*johnsoft joined #nim
16:27:15dom96filwit: what's wrong with the current smileys?
16:29:01filwitnothing
16:29:16filwiti just thought making smileys sounded fun
16:29:39filwitwould be the last thing i did anyways, it's not important
16:30:22filwitdo you have any idea why all the image on the forum seems to load with every refresh?
16:30:36filwiti think some setting on your host system isn't caching right
16:31:20dom96filwit: I haven't implemented any caching
16:31:45dom96filwit: could you remove the borders around the main content in the forum's design?
16:32:14filwitso the body is "full width" like the website?
16:32:36dom96I guess
16:32:51dom96bbl
16:37:16filwitdom96: when you get back, please tell me the host systems you're using for the website & forum so I can look into fixing the cache issue. It's not something you implement, but a server header issue telling the browser to always pull the graphics.
16:38:01filwitI'm not an expert on these things, so I'll need to know what you guys are using to look up how to fix it.
16:39:34*HakanD quit (Quit: Be back later ...)
16:39:44federico3<3 help2man
16:41:06*pafmaf joined #nim
16:49:52*chemist69 quit (Ping timeout: 250 seconds)
16:50:21*HakanD joined #nim
16:53:35*HakanD quit (Client Quit)
16:56:10dom96filwit: This needs to be implemented in jester AFAIK
16:57:01infinity0Araq: do you have a build script for the documentation?
16:57:15federico3infinity0: I'm working on it ATM
16:57:31filwitdom96: okay, makes sense.
16:57:56infinity0it should really be part of the upstream release, though. the structure is unclear, some files import other files so we don't want to build those child files directly
16:58:33federico3infinity0: have you built the last package?
16:58:38infinity0also there are replacements like |nimversion|
16:59:26infinity0federico3: i'm trying out the debian package and the documentation building atm has some flaws
16:59:46infinity0i was hoping upstream has a script for it somewhere, that was neglected to be included in the zip
17:00:10federico3infinity0: ok, it's also not building the nice "theindex.html" page yet, but we are getting there
17:00:34dom96infinity0: how are you guys building it?
17:00:39dom96Are you using ./koch web?
17:00:48infinity0ah, koch isn't part of the nim zip
17:00:56infinity0i guess we could do that
17:01:07infinity0oh wait, yes it is
17:01:09infinity0i see
17:01:28federico3that seems to be building some pages specific to the website as well
17:02:53infinity0that's fine, we can bundle it
17:02:58*darkf quit (Quit: Leaving)
17:04:38def-infinity0: you're working on a debian build for nim?
17:04:49infinity0yes federico3 and i are
17:06:11def-Great, would love to see Nim in Debian
17:14:52infinity0wow, koch clean removes debian/ :/
17:22:07*davidhq joined #nim
17:22:08infinity0is there a way to regenerate nim_icon.o and koch_icon.o?
17:32:09def-infinity0: why do you need them? They're Windows only, right? You can build them with windres
17:32:41def-for linux the .ico files should be fine
17:32:48filwitMiroserf Windres 10
17:33:15def-filwit: the program is actually called windres...
17:33:25filwitoh really? lol
17:33:28def-https://sourceware.org/binutils/docs/binutils/windres.html
17:33:32filwiti thought was just a spelling mistake
17:36:00infinity0ah ok
17:36:13infinity0i guess we can delete them just to be safe
17:36:22def-Sure
17:37:04infinity0it is unnecessary to install the .idx files right? they are just to generate some of the index html files?
17:39:15def-seems so, don't see them being used anywhere
17:40:03*AckZ joined #nim
17:43:22*filwit quit (Quit: Leaving)
17:51:19*chemist69 joined #nim
17:59:43*petrus joined #nim
18:09:28reactormonkinfinity0, I would guess they're used to build the index
18:14:00*irrequietus joined #nim
18:20:01*Demos joined #nim
18:24:06*UberLambda joined #nim
18:32:31*chemist69 quit (Ping timeout: 255 seconds)
18:36:18*petrus quit (Quit: WeeChat 1.1.1)
18:46:26*davidhq quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
19:20:54*davidhq joined #nim
19:23:20*davidhq quit (Max SendQ exceeded)
19:25:43*davidhq joined #nim
19:28:02*davidhq quit (Max SendQ exceeded)
19:55:57*dumdum quit (Ping timeout: 256 seconds)
19:57:18*davidhq joined #nim
20:02:36*davidhq quit (Max SendQ exceeded)
20:24:43*atgnag joined #nim
20:25:13atgnagDoes nim have a good sockets library?
20:26:03Araqyes, I think one can call it "good" by now
20:26:19atgnagAll right.
20:26:30atgnagI think I might create an irc bot then.
20:27:11def-atgnag: from scratch? there's an irc library as well
20:27:24atgnagOh, really? Well, that also helps.
20:27:39atgnagIn stdlib?
20:27:52def-https://github.com/nim-lang/irc and an existing bot it seems: https://github.com/nim-lang/nimbot
20:28:14def-atgnag: it was in the stdlib once, but now moved out. "nimble install irc" should work
20:29:49atgnagAll right. Good to know.
20:30:02*chroem joined #nim
20:31:04chroemAs there any way I can get at the uncompiled C code that gets generated?
20:31:23chroemI want to try converting it to asm.js.
20:31:33*brson joined #nim
20:31:41def-the c code lands in the nimcache directory
20:31:53chroemAlright
20:32:12*Mat4 joined #nim
20:32:18Mat4hi all
20:32:20def-with --compileOnly only the c code is generated, no binary
20:32:22def-hi Mat4
20:32:40chroemCool, thanks.
20:34:57atgnagIt's pretty neat how fast things compile, I must say. I'm not sure it's quite golang speed, but it's really convenient.
20:36:11Mat4indeed, the compilation speed is good compared to other languages which compile to C
20:36:15atgnagAlso, what's babel?
20:36:37def-atgnag: babel is the old name of nimble, Nim's package manager
20:37:36Araqatgnag: we haven't really optimized compile-times yet
20:38:46Mat4Araq: it's definitly not an issue in my opinion
20:39:21AraqMat4: nor is it in my todo/roadmap ;-)
20:40:03Mat4good to know ;-)
20:41:18*brson quit (Quit: leaving)
20:47:26*Boscop__ joined #nim
20:47:41*Etheco- joined #nim
20:50:48*Etheco quit (Ping timeout: 245 seconds)
20:50:48*Boscop_ quit (Ping timeout: 245 seconds)
20:55:21atgnagDoes aporia build against nim-devel?
20:55:57BlaXpiritpretty sure
20:56:07def-atgnag: yes, but you have to use the head: nimble install "aporia@#head"
20:59:13*UberLambda quit (Quit: Leaving the Matrix)
21:04:24VarriountMeep
21:05:22atgnagdef-: Thanks.
21:08:07Araqhttp://forum.nim-lang.org/t/870
21:08:53BlaXpiritamazing
21:10:57Araqwell it was an open secret at this point ... I guess
21:13:27flaviuAraq: I had no idea you and gokr were working together :)
21:14:17def-"open secret"? more like total news to me
21:14:43def-Sounds great, financial backing for Nim
21:14:54Araqmaybe I'll manage to produce a youtube video from the demo
21:15:19flaviuSo now you can do bug fixes full time? ;)
21:16:49Araqwell there certainly are other priorities ;-) but yes, I can spend more time on Nim's core.
21:17:48*chemist69 joined #nim
21:21:35flaviuLooking at Urho3D too, looks very intersting.
21:22:17Varriount*gasp*
21:22:27Araqit uses every C++ feature under the sun ... and for good reasons. but it was really hard to wrap. the result is 250 modules of Nim wrapper code..
21:23:36flaviuIs c-blake also with 3DICC?
21:24:09Araqno.
21:24:18Varriountonionhammer: Ping
21:24:19*flaviu quit (Read error: Connection reset by peer)
21:24:26*flaviu joined #nim
21:29:12vendethielAraq: congrats :)
21:29:39Araqthank you. :-)
21:30:05gokrHey guys
21:30:49Araqgokr: die Katze ist aus dem Sack
21:30:57gokrYeah!
21:31:12gokrI took 3 years of German, so that I can parse fine ;)
21:31:43Mat4congratulation
21:32:54*itsmeront joined #nim
21:36:12gokrSo feel free to ask questions about 3DICC etc
21:38:08VarriountHrm, should we post this on reddit/hacker news/the internets?
21:38:36Mat4good idea in my opinion
21:40:39VarriountMat4: Yes, but it shouldn't be done without consent.
21:40:40gokrThe Urhonimo wrapper is pretty cool to post about. And the very capable C++ wrapping capability in itself is quite cool. And us betting on Nim and hiring Andreas, well, perhaps not that kindof news.
21:41:19gokrIts not a secret, and in fact - us going dark on this is
21:41:33gokrnot for 3DICC reasons. ;)
21:41:46*gokr points at Araq
21:43:11gokrBtw, us from 3DICC is thus me, Araq and itsmeront
21:44:48gokrBut yes, the fact that Andreas now works on/with Nim full time is probably going to be a boost ;)
21:46:04*reem joined #nim
21:47:01Araqgokr: I guess I should also send an email to the ML? I shouldn't be biased.
21:47:58gokrAlso, if people wonder - we at 3DICC have been active in the open source arena for a long time. Our whole system is built purely out of open source technology. So we have no intention whatsoever to try to make Nim "ours". We want it to thrive as it is. The only sofware we will keep under commercial license - is our own product.
21:48:27gokrAraq: Sure, doesn't hurt!
21:49:18Mat4gokr: Of course
21:50:07gokrReleasing the Urhonimo wrapper as MIT is only natural to us. We hope more people use it. And Andreas kept it under "wraps" since he wanted to have it working before showing it ;)
21:51:25*xet7 joined #nim
21:51:55Araqoh and the wrapper is not stable :P we'll improve the API without concerns about backwards compatibility
21:52:07AraqI think.
21:52:23*Araq already has improvements in the pipeline
21:53:13Araqhi xet7 welcome
21:53:36xet7Araq hi, is devel head broken? I got some compile error.
21:53:49Araqwhat error?
21:53:54*pafmaf quit (Quit: This computer has gone to sleep)
21:54:18xet7lib/system.nim(2453, 52) Error: invalid pragma: benign and then FAILURE
21:54:41def-xet7: you're following the bootstrapping instructions?
21:54:52Araqyeah that's unfortunate but 10.2 cannot build 10.3 anymore
21:54:54xet7yes on website
21:55:11xet7how can I get newest version?
21:55:29Araqyou only need to ensure not some old nim binary is used
21:55:40Araqand install from C sources
21:55:57xet7where is instructions for install?
21:56:02def-https://github.com/araq/nim#compiling
21:56:08xet7ok thanks :)
21:56:36VarriountIf only we could rewrite the repo's history all willy-nilly
21:56:50AraqVarriount: why?
21:56:51gokrxet7: In those instructions - don't miss out on the "-b devel" that needs to accompany both clones.
21:56:56Mat4I have these terminal-emulation library (it's basical an emulator for a simple video-display processor I've once developed) which needs SDL 2. Can I assume the Urhonimo wrapper where be a good replacement for it ?
21:57:01gokrxet7: If you want devel that is.
21:57:10VarriountAraq: To introduce changes that allow older versions to compile newer versions
21:57:34Araqwell I can see if I can make it compatible with 10.2 again
21:58:07def-Araq: don't think that's worth the effort when you canjust bootstrap, or is it?
21:59:13Araqwell I dunno. it's bad no previous version can build the next one
22:00:05def-you can make a chain by going a few commit steps at a time and recompiling ;)
22:01:49*Demos quit (Read error: Connection reset by peer)
22:04:09*bjz quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
22:04:42fowlbasic2d and basic3d docs are missing
22:06:35Sembeitalking about 3d ... there's any creative programming libraries like openframeworks for nim ?
22:07:06xet7Ok now I got devel compiled and it works :)
22:07:23fowldo i just add a srcdoc2 field to website.ini?
22:07:28*bjz joined #nim
22:07:55flaviuThis is a while ago and I haven't seen any problems recently, but http://slashdot.org/comments.pl?sid=6771453&cid=48860921
22:08:32gokrI was just about to post that link - please guys, click on it, and then think about it.
22:11:04Araqfowl: and you have do edit ... doc/lib.txt iirc
22:13:42xet7how do I install nimble ?
22:13:53def-https://github.com/nim-lang/nimble#installation
22:14:01xet7thanks def-
22:15:29Mat4ok, probably not
22:16:00flaviuI don't like the idea of having a list of rules, but would temporary +q's be acceptable to the community if discussion turned uncivil?
22:17:03Varriountflaviu: The problem with that is that araq and dom96 are the only ones with op access, and they aren't always around.
22:17:09*atgnag is now known as Schnaube2t
22:17:18*Schnaube2t is now known as Schnaube1t
22:17:19gokrI find it hard to understand why it should be so hard to be civil.
22:17:40*Schnaube1t is now known as atgnag
22:17:53AraqVarriount: what? flaviu and def- are ops too iirc
22:18:04VarriountI'd like to think that I'm fairly civil most of the time..
22:18:05Araqaren't you an op as well?
22:18:17VarriountAraq: Nope. I'm not an admin on the forum either.
22:18:26Araqoh you mean the forum
22:18:35Araqflaviu is talking about this IRC channel
22:18:59flaviuHe isn't op in irc either, apparently.
22:20:00Araqflaviu: temporary +q's are in our guidelines:
22:20:07Araqhttps://github.com/Araq/Nim/wiki/IRC-guidelines
22:20:52flaviuI think that only dom96 can add ops.
22:21:46VarriountAraq: I mean both.
22:22:05VarriountI'm not an op on the irc channel, nor am I an admin on the forum.
22:22:07*chroem quit (Ping timeout: 246 seconds)
22:22:28Araqthat sounds bad, how do you manage to survive? just kidding.
22:22:56BlaXpiritreally seems like Varriount deserves some rights
22:23:32fowllol
22:24:01Araqnot sure if that's the right command my IRC foo is non-existant
22:24:17flaviuAraq: Nope, Varriount will loose his OP if he ever deops.
22:24:28Araqyeah of course
22:24:31flaviuuse /msg ChanServ ACCESS #nim LIST to get a list of ops.
22:25:26Araqflaviu: doesn't work.
22:25:42BlaXpiritflaviu's command just worked for me
22:25:50fowl'access list #nim'
22:26:09flaviuWell, here's the output: https://gist.github.com/flaviut/a74c45dd35170d9790fe
22:27:45fowlthen he cant add ops either
22:27:58Araqyup, too bad
22:28:56AraqI can make him an admin on the forum though. in theory.
22:29:56*kuzy000_ quit (Ping timeout: 246 seconds)
22:30:54flaviudom96: Ping. Please add +O on all the ops, +o on Varriount, and +F on Araq.
22:31:20flaviuActually, I misunderstood +O. Don't add that.
22:34:10Sembeiwe have stats about how is growing nim on user basis ?
22:35:30*Mat4 quit (Quit: Verlassend)
22:35:57*Jesin quit (Ping timeout: 252 seconds)
22:36:03VarriountSembei: Well, there's the channel user count, as well as the number of forum members and mailing list members.
22:36:47Araqand the ever growing list of github watchers/stargazers (is that really a word?)
22:38:24Sembeion gihub counts more contributors
22:39:50Sembeiwatchers can click one time and be inactive
22:40:25Araqok, then we still suck I guess :P
22:40:34Sembeihahahaha
22:45:55dom96I think we've got enough OPs here now.
22:46:10Varriount:<
22:46:47Araqdom96: really? what about some OP that actually does something?
22:47:16dom96Araq: hrm?
22:48:04flaviudom96: You should still add +F to Araq.
22:49:50dom96flaviu: What does that gain him?
22:50:46flaviuFounder status, which I think is like a super-op.
22:51:13dom96Varriount: But ok, i'll give you +o.
22:52:04dom96I expect all OPs to follow this btw: https://github.com/Araq/Nim/wiki/IRC-guidelines
22:52:18dom96Would be awesome if somebody wrote some community rules.
22:52:22dom96Similar to Rust's.
22:52:54dom96So that we can point to them if somebody is being rude.
22:53:28flaviuI'm not a big fan of rules, I feel that everyone here knows what being civil is.
22:53:50def-flaviu: lets call them guidelines instead
22:54:39fowlwe should call them by-laws and we should enact committees to come up with them
22:55:09flaviuheh
22:55:13fowlit should be a very rigorous legislative progress that takes years to accomplish anything
22:55:20dom96Yeah, sure. I should have used the word "guidelines".
22:55:47fowlfuck. im being sarcastic
22:56:26fowlhopefully some anonymous andy wont read that and judge the programming language negatively
22:57:14dom96Araq: What do you think of this? https://news.ycombinator.com/item?id=9050999 Bug or not?
22:58:13Araqpfff such an old hat
22:58:14flaviufowl: Lets be civil. I feel just as uncomfortable as whoever complained felt.
22:59:07Araqdom96: the dangers of compiling to C are widely known. he didn't even go into the real problems here.
23:00:04gokrflaviu: I am with you 100%. But not fully with you on the "everyone here knows what being civil is". Or well, perhaps they know but simply don't abide ;)
23:00:43Triplefoxi recommend for policy, gentle reminders of time spent on a discussion. that helped cool things down the last time i tried it.
23:01:18fowlflaviu, i can't not be sarcastic. its a personality flaw i guess, i can't turn it off
23:02:53flaviufowl: Sarcasm is fine IMO, but calling someone an "anonymous andy" is rude.
23:04:55fowli disagree
23:05:25fowlflaviu, thanks for that link on linear interpolation the other night
23:06:12fowlnot sarcastic, it helped a lot
23:06:23flaviuSure, no problem. That footnote at the bottom is the part I find most interesting.
23:06:51dom96Araq: so not worth a bug report then?
23:07:12flaviudom96: Araq has already replied, see https://news.ycombinator.com/item?id=9051068
23:07:41Araqdom96: yes, open a bug report. we should at least provide a nicer clang configuration out of the box
23:09:01dom96flaviu: cool
23:12:54*vendethiel quit (Ping timeout: 244 seconds)
23:15:05*BlaXpirit quit (Quit: Quit Konversation)
23:15:14*vendethiel joined #nim
23:16:56flaviugokr, dom96: https://github.com/Araq/Nim/wiki/Community-Guidelines-%5BProposal%5D
23:18:10dom96flaviu: would be nice to define some of the terms used there such as trolling, flaming and baiting with links to their definitions.
23:20:56*reem quit (Remote host closed the connection)
23:23:58flaviudom96: I've clarified.
23:24:11*sillesta quit (Ping timeout: 246 seconds)
23:27:17*dashed joined #nim
23:29:02Triplefoxmore suited for conferences, but maybe useful for thoughts on channel policy http://www.ashedryden.com/blog/codes-of-conduct-101-faq
23:30:35fowlwow this urho3d wrapper is interesting
23:31:56fowlimportcpp: "#.GetResource<'*0>(@)"
23:32:25Araqfowl: it's documented in nimc.txt devel version
23:36:06fowlthat is awesome
23:37:59*reem joined #nim
23:39:33onionhammerVarriount whats up
23:41:26gokrfowl: Did you manage to run the example? character.nim?
23:41:49*reem quit (Remote host closed the connection)
23:41:52gokrflaviu: And yes, guidelines look like a good start. A bit short?
23:42:26gokrflaviu: Although I don't favor long winding documents, but given its adapted from Rust - one may wonder why lots of parts were cut out :)
23:42:55onionhammerWow Araq, just saw the news, cool :)
23:43:00fowli didnt try gokr, it looks complicated though
23:43:10gokrfowl: Its not really.
23:43:28flaviugokr: I suppose it's a good idea to copy the full thing from rust
23:43:31gokrBuild Urho3D is easy. It spits out libUrho3D.a
23:43:56flaviualthough I think that giving ops discretion as to how they handle things is a good idea.
23:43:56gokrIts all fully contained also, so builds very nicely without chasing deps.
23:44:07gokrThen you need nim devel.
23:44:20*matkuki joined #nim
23:44:41gokrAnd then to build character.nim - you basically just "nim cpp character" and then copy those dirs so that it finds data.
23:45:37gokrflaviu: I don't say we need to copy. Then it may not carry much weight.
23:45:49fowlgokr, btw you can check the compile mode is not cpp then use {.error.}
23:46:13gokrflaviu: But I can read more carefully and give more constructive... proposals.
23:47:11fowlgokr, since you say in the readme using nim c gives strange errors
23:47:15gokrAlso, Urho3D has many more examples - if you just want to see its capabilities. They are in either C++, AngelScript or Lua. The character example in Urhonimo is adapted from the C++ example.
23:47:27gokrfowl: It was Araq who wrote that ;)
23:48:39fowldefined(cpp) iirc
23:48:49gokrSo beside having a super cool 3D gaming engine (not just graphics) that runs fine on OSX, Linux, Windows, iOS and Android - we also now have a very strong story on C++ wrapping.
23:48:57gokrThat that is a killer feature for Nim I would say.
23:49:04gokr"And that"
23:49:23flaviugokr: Lots of the stuff in that rust COC is about discrimination on "personal characteristics". I've never seen any problems with that in #nim.
23:49:49gokrflaviu: Agree, we can try to limit us a bit.
23:50:22flaviuThe main problem in this channel is flaming, mostly unintentional.
23:50:35fowlits because we're all so hawt
23:50:36Araqfowl: yeah, dunno why I didn't do that
23:51:27gokrSo I must say Andreas ... kinda blew my mind he could wrap Urho3D that well in this short time. Sure, there will be many kinks - but still.
23:51:47gokr"unintentional"?
23:52:01fowlgokr, you have to code a bit differently in cpp mode
23:52:34flaviuWell, people get carried away while arguing. Their goal isn't to waste time.
23:52:40Araqfowl: not really? what do you mean?
23:52:43matkukiIs the "break" statement in this code suppose to break out of both loops: https://bpaste.net/show/111315b3eb8d ?
23:52:44*vendethiel quit (Ping timeout: 252 seconds)
23:53:00fowlfor item in someseq: might not be a good idea anymore, in c you at least knew this was a shallow copy
23:53:36Araqmatkuki: no! but my bet it's because of the magic 'fields' iterator
23:53:49fowlnow it depends on what the copy constructor does
23:54:20matkukiAraq: So I shouldn't do it this way?
23:54:30Araqfowl: if you don't care about efficiency, I don't see the problem really
23:54:46fowlmatkuki, wrap it in a block:
23:54:52Araqmatkuki: report it, the compiler shouldn't even allow it
23:54:52fowlnamed block
23:55:05matkukiWill do.
23:55:08Araq'break' in 'fields' is not supported
23:55:12Araqiirc
23:56:12matkukifowl: Wrap which part in a block?
23:56:26def-Anyone want to look through the GSoC 2015 Organization Application?: https://github.com/Araq/Nim/wiki/GSoC-2015-Organization-Application
23:56:35fowlmatkuki, the inner for loop, this would let you break out of it
23:56:56matkukiThanks, will try it!
23:57:09fowlmatkuki, like block foo: stmt1; stmt2; break foo
23:57:23gokrflaviu: I buy unintentional baiting/trolling. But flaming is simply insulting someone - hardly unintentional.
23:58:31matkukifowl: Yup it works, thanks.