18 ms·
Wow, that's quite a self-referential post! I don't know what Gustavo's role is within Python development, but I really don't think he understands the motivation
by nkurz 16y ago
Wow, that's quite a self-referential post! I don't know what Gustavo's role is within Python development, but I really don't think he understands the motivation of the core developers like Brett.
Here's from Brett's original:
I have a finite amount of time to volunteer in helping
make Python what it is. Having people push upon me that
they either think I am failing because I can't find a
solution to a problem (the "complainers") or that the
solution that I help create is not good even though it
has not been implemented and proven to be a failure (the
"what about this?" folks) just sucks away that much more
time, preventing me from helping make Python better for
YOU. It gets to the point that I sometimes wonder why I
put in so much time and effort when so many people gripe
about the volunteer work that I put in to produce this
thing that is given to the world for free.
And then Gustavo:
I apologize, but I have a very hard time reading this and
not complaining.
...
I know this is just yet another complaint, though. I
honestly cannot fix the problem either, and rather just
talk about it in the hope that someone who’s able to do
it will take care of it.
Disgusting. Could you at least make an effort to convince the developer that they personally would benefit from the massive amount of work you are demanding of them, instead of just trying to bully them into it?
More from Gustavo:
I can’t provide ideas or solutions.. I can’t fix the
problem.. they don’t even care about the problem. Why am
I using this thing at all?
Go a little farther: how does the developer benefit from your use of this software? If you can figure out how to answer this question in the positive, you've probably figured out a much better strategy for convincing others to solve your problems for you. If you can't, perhaps there is some other software that you could buy? If the developers don't care about the 'problem', maybe it's not their problem after all?
- nailer 16y agoI think it's OK to have an opinion on anything you like. You shouldn't expect anyone to fix it for free though. I've never written a VM, and I don't think I'd be very good at it. I've written useful modules other people use, spoken at a Python conference, and have other OSS code in various places. I'm not a succubus, at least I hope I'm not. I don't even mind multithreading in Python, since I use Threads and Queues and they work just fine for my purposes. But I'm sure, other more cooler things would happen if CPython had the same kind of multithreaded coolness that Jython and IronPython have. I don't think it makes me a bad person if I say that.
- jacobolus 16y agoIt makes you an annoying person if you say it without any research, and without even reading any of the decade of accumulated identical discussions, on the mailing list devoted to python development, distracting contributors from actually fruitful discussions and developments.
- tomjen3 16y ago>I've never written a VM, and I don't think I'd be very good at it Don't be so sure, there are a lot of research in this area and it is not black magic.
- aarongough 16y agoI agree! I'm actually in the process of writing my first VM right now, and it's not as hard as you would think...
- mkramlich 16y agoAll projects are easy at the start. See I just open this empty file here and start typing...
- aarongough 16y agoWhoever said I was at the start? The prototype is nearly done, and already working in the meantime.
- mkramlich 16y ago"The prototype is nearly done." you're still pretty early in the project's lifecycle. software projects generally move fastest and have the least difficult challenges early on, as a general rule, in my experience. once you have a lot of users, and legacy dependencies, and have to work right on N platforms, and handle edge cases, and be performant, and the codebase becomes so big you no longer remember all the details, and maybe a few years have passed since you were working on it full-time, etc., then you'll find that velocity and agility decreases.
- JabavuAdams 16y agoDisgusting. Could you at least make an effort to convince the developer that they personally would benefit from the massive amount of work you are demanding of them, instead of just trying to bully them into it? Come on, it's 2010. Multi-core is here to stay. It's disgusting that a general-purpose language like Python has such a horrible default properties on multi-core.
- shadowsun7 16y agonkurz isn't arguing about multi-core (and various benefits thereof). He's arguing about convincing the developer that there are benefits of adding such support, instead of 'just complaining'. On a personal note, I must say here that I've never considered the differences between the two, and I'm taking this to heart.
- rbanffy 16y agoCare to explain what real-world problems you had with the GIL? I am usually the first guy to say the GIL must go, but, quite frankly, I have learned to make Zope+Plone and Django stacks scale without messing with it. If you have a 32-core server and you want to serve, say, a Zope site, just use ZEO (ZEORaid, perhaps) and 31+ ZEO clients behind your Varnish cache. The GIL must go, but the fact the very clever people who have tried to make threading nicer have tried to get rid of it and failed indicates this is not an easy problem. It's not about getting rid of the GIL. It's about getting rid of it without breaking compatibility with the mountain of modules written in C there are - and that experience little or no GIL problems by themselves. And, mind you, we are talking about CPython, the canonical implementation. IIRC, neither Jython nor PyPy have the same kind of multi-core performance problem. I am not sure, but if you write your performance-critical module in RPython and then compile it into C, you won't have many GIL problems either. While the GIL is the biggest problem I can see in CPython, for most usage scenarios, it's not a big one.
- fauigerzigerk 16y agoYes, the question is whether Python intends to support the growing number of usage scenarios for which the GIL is a problem. You could write something like Cassandra or Lucene using a combination of Python and C, but the GIL prevents that.
- ahk 16y agoHere's an analogy I thought up: You go to a shanty town and announce "free apartments for everybody", and the people are excited and help you build the new apartments. When nearly complete, you announce "oops looks like we didn't design for toilets here. Guess you'll all have to go back to the shanty town for all that". I think it's understandable that people would be pissed. Pointing out that you got all that other stuff built isn't really going to cut it.