#jython IRC Log

Index

IRC Log for 2017-05-30

Timestamps are in GMT/BST.

[1:20] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) Quit (Quit: Leaving.)
[9:27] * Cheaterman (~cheaterma@unaffiliated/cheaterman) Quit (*.net *.split)
[9:27] * teletubbie_ (~T.T@151.ip-158-69-207.net) Quit (*.net *.split)
[9:27] * _Myles (~Myles@the.sexiest.man.alive.just.joined.and.he.is.called.myles.us) Quit (*.net *.split)
[9:27] * offbyone (~offbyone@ec2-52-42-218-253.us-west-2.compute.amazonaws.com) Quit (*.net *.split)
[9:27] * 18VAAPUPB (jamierocks@81.4.107.71) Quit (*.net *.split)
[9:30] * Matsv (~Matsv@i.am.matsv.nl) Quit (Ping timeout: 240 seconds)
[9:32] * Matsv (~Matsv@i.am.matsv.nl) has joined #jython
[9:33] * offbyone (~offbyone@ec2-52-42-218-253.us-west-2.compute.amazonaws.com) has joined #jython
[9:42] * girish946 (~gsjoshi@182.70.64.183) has joined #jython
[9:49] * _MylesC (~Myles@the.sexiest.man.alive.just.joined.and.he.is.called.myles.us) has joined #jython
[9:49] * teletubbie (~T.T@unaffiliated/teletubbie) has joined #jython
[9:49] * Cheaterman (~cheaterma@tms-server.com) has joined #jython
[10:03] * girish946 (~gsjoshi@182.70.64.183) Quit (Ping timeout: 240 seconds)
[10:13] * 18VAAPUPB (jamierocks@81.4.107.71) has joined #jython
[10:16] * srcerer_ (~chatzilla@dns2.klsairexpress.com) Quit (Ping timeout: 246 seconds)
[10:16] * girish946 (~gsjoshi@103.51.153.189) has joined #jython
[11:18] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) has joined #jython
[11:25] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) Quit (Quit: Leaving.)
[12:05] * girish946 (~gsjoshi@103.51.153.189) Quit (Quit: Leaving)
[13:28] <topi`> jimbaker: agreed, pull requests all the way
[13:29] <topi`> jimbaker: I got some questions from the audience, but they seemed to be focused on the performance impact of using jython... even though I *tried* to explain that if there is a perf bottleneck somewhere, just rewrite it in Java and import it
[13:29] <jimbaker> right. fwiw, i don't know how to edit jython.org, because it is own unique setup
[13:29] <jimbaker> made sense a while ago, but we now have better tooling
[13:30] <topi`> I should have explained them that jython allows other programming paradigms than the usual object-oriented one, and you can mix and match styles
[13:31] <jimbaker> re performance - it is a problem that can be solved, but it is not so easy either. using the new type support would make it much more feasible
[13:31] <topi`> and if using functional style, even partially, allows to reduce side effects
[13:31] <jimbaker> so mixing in java is the right answer :)
[13:31] <topi`> import itertools
[13:31] <jimbaker> itertools is a good example, because it is written in java in the jython runtime, for performance.
[13:34] <topi`> IIRC itertools are written in python in CPython
[13:41] <jimbaker> no, it's written in C - https://github.com/python/cpython/blob/master/Modules/itertoolsmodule.c
[13:43] <jimbaker> still worth comparing java vs C. note this is a bit more complex because we have to support these functions so they fully match python semantics
[13:43] <jimbaker> https://github.com/jythontools/jython/blob/master/src/org/python/modules/itertools/permutations.java
[13:44] <jimbaker> and https://github.com/python/cpython/blob/master/Modules/itertoolsmodule.c#L3015
[13:52] * xemdetia (xemdetia@nat/ibm/x-tnnwwhokquqqgeko) has joined #jython
[16:00] * Cheaterman (~cheaterma@tms-server.com) Quit (Changing host)
[16:00] * Cheaterman (~cheaterma@unaffiliated/cheaterman) has joined #jython
[19:19] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) has joined #jython
[19:25] * srcerer (~chatzilla@dns2.klsairexpress.com) has joined #jython
[21:52] * CrypticSquared (~CrypticS_@unaffiliated/crypticsquared) has joined #jython
[22:12] * xemdetia (xemdetia@nat/ibm/x-tnnwwhokquqqgeko) Quit (Ping timeout: 240 seconds)
[22:55] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) Quit (Quit: Leaving.)
[23:20] * stewori (~stefan@ip-95-223-198-21.hsi16.unitymediagroup.de) has joined #jython

Index

These logs were automatically created by JythonLogBot on irc.freenode.net using a slightly modified version of the Java IRC LogBot.