16:52:00jeosolthis was good discussion overall, some good points. may be no need to explain my choice of CL
16:53:49jeosolphenoble: do you ML stuff with python yet?
17:01:15phenoblejeosol: funny of you to ask, I'm planning on working on my machine-learning skills, and given the available tools and resources out there, Python will indeed be my choice for that.
17:01:52phenoblejeosol: but I am about to have a look at Racket for Scientific Programming soon, too.
17:02:36phenoblejeosol: ...just got to finally finish works on my every-growing (but also every-improving) emacs configuration in elisp :)
19:44:30beginner_supremeI mean vlime, it's like slime but for vim. Similar to the slimv project except slimv is written in python, while vlime is a mix of CL and C
19:44:37Josh_2Why would you learn vim to use vlime?
19:50:36beginner_supremeSo far I've been using a regular editor without the repl server connection.
19:50:53beginner_supremeAnd using macros to reduce the need for repetition
19:50:59phenoblebeginner_supreme: you should try spacemacs (an emacs distribution) with evil (a vim emulation). Both together do away with what many would consider, Emacs' unintuitive keybindings.
19:51:07_deathI would say this approach misses out very important aspects of Lisp
19:55:29phenoblebut it's worth it - consider it an investment that'll net returns many years on
19:55:37_deathI don't know if the curve is that steep... especially if you're going to learn Lisp anyway
19:55:49oleo http://dpaste.com/1T2EEKY my startup file for default branch mcclim-master
19:55:53Josh_2I can't say I'm an expert in Emacs, and it wasn't difficult to pick up
19:56:04oleo http://dpaste.com/2RH15GA my startup file for branch mcclim-freetype2
19:57:49beginner_supremeThanks for the suggestions and the conversation!
19:57:51phenoble_death, beginner_supreme: The steepness might also depend on how satisfied you are with the default configurations of vim and emacs. I know that I wasn't, so,... 2 years later I'm on freenode in #lisp.
19:58:28oleoi'm not sure why an explicit upgrade of asdf after loading quicklisp makes so much problems
19:59:01oleobut this way quicklisp can decide if it wants to upgrade stuff from the asdf in common-lisp/source/asdf
19:59:58beginner_supremeAnyways, thanks for the great conversation everyone, till next time [possibly with other nicknames, don't feel like registering yet]
20:04:50aethImagine if beginner_supreme registered and continued using that name for decades, while becoming one of the biggest experts in Lisp.
22:07:05aethI wonder if a normally AOT Lisp could JIT FFI to increase CFFI performance. Apparently JIT CFFI function calls have lower overhead than equivalent C function calls. https://news.ycombinator.com/item?id=17171252
22:39:45ZigPawbut the difference is probably insignificant (like few cycles). If you need to gain so few cycles, you are probably better off inlining the function (and it might be done by JIT I think). But I'm not an expert.
23:27:17LdBetholeo (IRC): there is a ncurses IDE largely based on climacs, https://github.com/cxxxr/lem
23:28:48p_laeth: quite probably the "optimization" involved is already done by most lisps :)
23:29:18p_l(tl;dr one level of indirection less due to not using relocation/PLT and instead dynamically loading addresses into known space)
23:42:16aethIt would be interesting to benchmark. SBCL was not included in any of these benchmarks for some reason even though that's what everyone's interested in.