larryhastings / gilectomy

Gilectomy branch of CPython. Use "gilectomy" branch in git. Read the important, short README below!
Other
527 stars 43 forks source link

Come talk Gilectemy on Talk Python Podcast? #38

Open mikeckennedy opened 7 years ago

mikeckennedy commented 7 years ago

Hi Larry,

I know this is not strictly an issue didn't really belong here but for some reason I'm having a hard time finding your email address or twitter or some other way to contact you directly so here you go.

I think this would make a great topic on my podcast Talk Python To Me. I love to have you on as a guest. What do you say? Interested? We got to talk about other things like Pytho3, the release management process things like that.

Thanks, Michael

Sudo-Kid commented 7 years ago

As a Talk Python To Me listener I ask that you please do this Larry.

stonebig commented 7 years ago

I see no movement on the project since a few months.

Does it mean there is no realistic gilectomy on Cpython, and our only hope is an up-to-date pypy ?

clozinski commented 7 years ago

Gilectomy was our only hope. Yoda: "No...there is another..."

A proven approach. A great business model. Actually I need this for my own servers. Right now ZODB runs ZEO server and each ZEO client in a separate unix process, they could all be in the same unix process. Then I could release blogory in a docker container.

I just do not have the capital to work on it full time. I just completed http://blogory.org/python and need to make some money. But if a company like DropBox or Goldman Sachs were kind enough to hire two developers through me , I would be able to hire a full time developer here in Poland to work on the project. If I place 4 people, I could hire two developers. That would e enough to be done in 3-6 months.

Forgive me if proprietary concerns prevent me from answering specific questions about my approach. I need to be careful, there are some very smart people on this list. The good thing is that there is no risk to you in accepting my offer.

I head off on vacation in a few minutes and will be off-line until December 30th.

First of all it is a huge need. As far as I can tell Python is doing poorly because it does not support simultaneous mult-threading. And the bar is not that high. Linode offers me a 20 core server. Even each thread is 1/5 the speed of cPython, the app is still 5 times faster. What is the magic here?