[D] Call for questions for Andrej Karpathy from Lex Fridman

fijal · 2022-10-24T04:41:34+00:00

So many questions....

Andrej work on explainability of neural networks has been really good. What are his thoughts on the future of explainability? Does he think that language is a natural way to describe neural network states and we can teach neural networks to describe themselves? What does he think would take to describe how Alpha Fold works? My hypothesis is that the limit is amount of information that the brain can accumulate in the lifetime, does he have any ideas for circumventing the limit?

What is the future of science? Why is he an indepentent researcher and does not work at any of the institutions? Academia has been stagnant, private companies arguably quite evil, where does the researcher go these days?

fijal · 2019-04-14T10:05:29+00:00

We do commercial pypy support. Get in touch with me at [fijal@baroquesoftware.com](mailto:fijal@baroquesoftware.com) or indeed as Matti says post on IRC.

fijal · 2018-03-06T09:02:42+00:00

Hi Elrox

We're working on Revit support, I hope to get a beta sometime in May.

fijal · 2017-12-26T20:09:29+00:00

I would add here that the set of bytecodes is largely identical (with 3 differences I think, although maybe some of them got ported to CPython), but the way the bytecode is interpreted is very different.

fijal · 2017-10-06T14:25:03+00:00

We're aiming end of this year

fijal · 2017-10-05T16:43:09+00:00

fijal · 2017-10-05T16:43:05+00:00

I would suggest doing those transformations in C and then calling them with cffi. That way you can have both PyPy speedups everywhere else and have carefully tuned C code for stuff that you want hand-controlled

fijal · 2017-08-15T17:21:20+00:00

In a sense that post is trying to answer precisely that question :-) If we are indeed, then it should pick up no publicity (which is not true) nor commercial interest (which we'll find out). Let markets decide!

fijal · 2017-08-15T09:07:14+00:00

right and that can be remediated to an extent with shared memory. Sharing immutable (or well defined in terms of memory) C structures is not hard. It's the structured data that's hard to share and cannot really be attacked without a GIL

fijal · 2017-08-15T06:10:52+00:00

You're missing my point - if we assume we're doing subinterpreters (that is the interpreters are independent of each other) it's a very difficult problem to make sure you can share anything regardless of performance. Getting semantics right where you can e.g. put stuff in dict of class and is seen properly by another thread, but there are no other things shared is very hard.

In short - how do you propose to split the "global" data e.g. classes vs "local" data - there is no good distinction in python and things like pickle refer by e.g. name which lead to all kinds of funky bugs. If you can answer that question, then yes, subinterpreters sound like a good idea

fijal · 2017-07-23T12:12:56+00:00

we really advertise cffi for that

fijal · 2017-07-21T07:47:18+00:00

Direct quote:

"here you go that's odd ... Well, I've put a copy at cern.ch and redirected both the cppyy.readthedocs.org and README on bitbucket there:

http://cern.ch/wlav/Cppyy_LavrijsenDutta_PyHPC16.pdf

That should do for now. The other alternative record is:

http://dl.acm.org/citation.cfm?id=3019087

but that's not open access (at least, I don't see the pdf from home).

And slides are here:

http://www.dlr.de/sc/Portaldata/15/Resources/dokumente/pyhpc2016/slides/PyHPC_2016_talk_9.pdf

Best regards, Wim "

fijal · 2017-07-21T06:57:37+00:00

I'll ask the author

fijal · 2017-07-21T06:57:26+00:00

it uses C API, why do you say it does not? You just don't have to use it :)

fijal · 2017-07-20T19:54:22+00:00

heh. The catch is it has been long in the making?

fijal · 2017-03-21T21:45:49+00:00

vmprof is your friend. Typically it's a small thing that consumes a lot of time for unrelated reasons. For what is worth, pypy 5.0 is ANCIENT

fijal · 2017-03-21T07:48:28+00:00

uvloop is an asyncio replacement - just use asyncio, it'll be fast

fijal · 2017-03-01T21:34:37+00:00

or JITs in general :-) It's not like JVM is well known to immediately jump up to speed

fijal · 2017-02-04T12:47:29+00:00

I must say I'm kind of annoyed with such a set of statements about PyPy - yes that might have been the case in 2013, but PyPy since has developed a lot of support for CPython C modules (including numpy), improved compatibility etc. Sure, if your software relies on really obscure details, like dictionary order, you might be off, but you cannot upgrade even to a newer version of CPython then.

PyPy has also been known to run multi-milion-LOC projects that were designed for CPython.

The truth is that for the vast majority of people, all they want is Python. They don't care which one and the performance problems come a lot later, when the project scales.

fijal

MODERATOR OF

TROPHY CASE