cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake | IRC logs: and | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
jcea1 has joined #pypy
jcea has quit [Ping timeout: 248 seconds]
jcea1 is now known as jcea
jcea has quit [Ping timeout: 240 seconds]
otisolsen70 has joined #pypy
<fijal> the "Chris Lattner" part makes me sad
<fijal> oh no sorry, I'm confusing people here
<fijal> cool!
<fijal> ot
<fijal> it's not open source though
<cfbolz> yeah
<cfbolz> it's cool that they have a fast system/GPU subset of python
<cfbolz> but how many normal python features you can use will be interesting to see (there aren't even any classes yet)
<fijal> I have been thinking about the topic for quite some time - I *think* it's not that critical
<fijal> but it's critical to be able to call between the two
<fijal> like, main problem of introducing new language is "how do you have libraries" - and if you can call python that's a good enough answer
<fijal> I even tried to start one
<fijal> I completely confused Chris Lattner with the guy who did some flashy JS demos but never followed up with anything
<cfbolz> no, chris has been shipping lots of amazing things (which unfortunately are all written in c++ though ;-) )
<phlebas> it definitely looks very interesting, i wish there was more info on the "100% compatible with Cpython, we just fall back to it"
<phlebas> because we looked into that (using libpython and then falling back to that transparently), but there are so many details starting with how do you pass objects, interpreter state etc
<phlebas> but they seem confident, and it feels like a good way forward, especially the "incrementally moving modules to mojo" part
<phlebas> this quote made me laugh a little "the complexity of the Clang problem appears to be an order of magnitude bigger than implementing a compatible replacement for Python" - not sure if they are underestimating?
<nimaje> in the why-mojo.html it read to me, that they just send all python code to cpython, then the problem "just" becomes interop between python and mojo (well and making sure both runtimes agree on the global state stuff) (just to make sure, to me that doesn't seem that easy, but it reads to me like they think that way, that's why I used '"just"' there)
<phlebas> yeah, the "just" part is the one i'd be interested in. we tried that, and it turns out to be quite hairy to do that without essentially giving up and just running everything on python, but I guess the trick is in drawing the boundaries just right
jcea has joined #pypy
greedom has joined #pypy
otisolsen70 has quit [Ping timeout: 240 seconds]
MiguelX413 has quit [*.net *.split]
MiguelX413 has joined #pypy
otisolsen70 has joined #pypy
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #pypy
otisolsen70 has quit [Quit: Leaving]
Julian has joined #pypy
greedom has quit [Remote host closed the connection]
Julian has quit [Ping timeout: 240 seconds]
Julian has joined #pypy
Julian has quit [Ping timeout: 268 seconds]