HN user

holdenweb

36 karma
Posts0
Comments30
View on HN
No posts found.

I wouldn't say Python is good _at_ vectorization so much as good _with_ it. It's also good with AI, web systems, etc, as a result of its "play well with others" philosophy, which pragmatically accepted from the start that no one language could be best for all purposes.

One of the best improvements to Python's memory model was extending it to allow sensible access to blobs of memory containing regular structures such as vectors and matrices, making it relatively easy to interface with and control already-available, well-tried, highly-optimised algorithms.

Given the many ways of creating virtual environments it's becoming more usual for a program's installation to create a specialist virtual environment just to support that application (pre-commit is. good example of this technique). Perhaps that'a a way ahead?

Well, this has all the signs of well-meaning but inexperienced developers seeing a market opportunity without appreciating the many difficult problems that will have to be solved to produce something that is secure, reliable and interoperable with current development ecosystems.

Rather than abuse them, we might perhaps use them as an example of the Dunning-Kruger effect.

In point of fact two companies were the primary contractors for the redesign of python.org, but since I am no longer in the loop I will commend you to wait for an upcoming PSF blog post that will give the details. Design was indeed a major input to the project.

About Python 3 13 years ago

Fine, so you have found a language you prefer to Python. Go use it. Never mind about PyPy, which gives you compiled execution speeds, never mind about the fact that Python 3 fully supports NumPy, SciPy, matplotlib and much of the infrastructure you claim to need. If threading is your preferred solution to concurrent programming and it's working for you then there's no real problem, is there? I'm sorry Python doesn't work for you, but fortunately there's a rich toolset available of which Python is only a part. It's fine for many tasks, but it's by no means your only option. Isn't open source wonderful?

Well, whoop-de-fucking doo. Do you feel better now?

That's not sexism, it's GENDER DISCRIMINATION. And it's intended to counterbalance the years of bullshit that women have gone through because of the knuckle-draggers and others who aren't really concerned about such issues in charge. People who get a limited grasp on an idea and then try to twist the evidence to incorporate their world view, rather than doing joined-up thinking based on, you know, actual evidence.

I have spent years addressing the lack of all types of diversity in the open source world generally (and the Python community specifically) and I applaud efforts to increase female participation in information technology and open source. It is unconscionable that the gender balance in the open source software world is EVEN WORSE than in IT and the hi-tech world generally. But all you can do is bleat on about your nephew being discriminated against. Can't you see the larger good that this discrimination offers?

Did you also think the reverse discrimination applied to allow more black people to partake of opportunities which they had formerly been unconstitutionally denied was racist? I am aware there are some people who do, and they are peddling exactly the same type of bullshit as this.

I should apologize for the ad hominem use of "like you" and "idiot" in the original of the above description. I have apparently successfully edited the post, but intend to leave this apology here in case the original may be archived somewhere.

The truth is I don't know you, and I don't know anything about you, so it was unfair and unnecessary of me to characterize you in that way with a knee-jerk reaction. Sorry. You have stimulated a debate, and I do not wish to belittle your point of view, mistaken though I believe it to be.

The Code Of Conduct 14 years ago

Thank you. There's a difference between being psychic and being sensitive to the needs of others. We all make mistakes, but if we apologize if it's required and most of all if we don't continue along an unwelcome vector there should be no need for any invocation of a code of conduct.

As someone else has pointed out, its primary purpose is to reassure those who (reasonably or unreasonably) fear harassment that the issue will be taken seriously if it occurs.

The Code Of Conduct 14 years ago

You appear to misunderstand the principle. Behavior is acceptable or not in the context in which it occurs. Trying to make hard rules that specific actions are harassing is a no-hoper from the beginning. Behavior that might be perfectly acceptable with someone I know well could be completely harassing to someone I don't know.

The key issue is that if someone tells you that they consider your behavior offensive or unacceptable then you are expected to back off. To persist is one way of harassing people. Nobody's asking you to be a mind reader, but it does help if you have some empathy towards your fellow humans.

If "cronyism" wants to come out of the closet and admit who he or she is then we might know how much weight to give these unsubstantiated accusations. I have received similar representations privately as PSF chairman, have asked for evidence, and have not received any.

For the record, I have the utmost faith in Jesse's integrity as PyCon chair. I have not bothered to canvass my fellow directors, but I doubt any of them feel any different. The Foundation owes him a huge debt of gratitude for the immense amount of work he continues to put into this role while holding down a full-time job and being an active parent. It is obnoxious in the extreme to slur him in this way.

So let's see "the money trail," and let's have these accusations in the open so we can see that they are, in fact, simply unsubstantiated waffle.

In fact it's not a bad thing that 2.7 is so awesome - that makes it possible for people with large codebases to essentially put off the port to Python 3 for ever. Or maybe to skip Python 3 and port to Python 4 in another twenty years. Both are perfectly acceptable engineering decisions, and we are (or should be) talking engineering here, not religion.

As Jesse Noller has pointed out elsewhere, the transition was never intended to be instantaneous. The Wall of Shame might publicize those packages that are causing pain points, but it offers no prescriptions.

For some value of "supports" that apparently doesn't leave Jacob comfortable that it gets equal developer attention at Heroku. Of course the other language support could be perfect ... I'll prefer to trust the opinions of people I know with no apparent axe to grind.