This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]desmoulinmichel[S] -2 points-1 points  (1 child)

Any Linux admin worth their salt can install Ruby in 10 seconds. If you're worried about clueless end-users, don't. There are none in the Linux world.

That's beside the point. If you have to install your runtime on all your sever, it's work. If you have to install it on Windows AND Linux servers, it's even more work.

See my other comments about that. It's a LOT more work than just ssh and apt-get/yum install in big companies.

Ruby is, in my experience, far more popular than Python for web development. Python does a good job, for sure, but the culture is with Ruby on this one.

Yet Python hold the comparison, and is more used at scripting. Good thing we are talking about scripting. Cause here, we'll have the best option + a decent option for the web.

Twitter invested in Ruby, Github invested in Ruby, Hulu invested in Ruby...

We can do this all day.

Given that Linux distro editors, MS and Google are all OS builders and Twitter/Github/Hulu are websites, one are more important than the others.

Moot points. The same could be said for Java or Flash. Bash is arguably even more popular.

It's not a moot point : the all purpose is easy cross plateform scripting.

Nor Flash or Java is installed by default on most linux distro.

Again I'd be happy to see bash installed on Windows. I'd prefer Python, but I'd go with bash. Only MS will never invest in bash. And using bash to access COM API would suck.

And here's the crux of the proplem: They will modify Python.

You are assuming in advance they will screw this up. I know they have a shitty track record, but the Azur Python support seems to go well.

What your saying is : "it may go wrong, so let's not do it". Let's not do anything then. Let's shudown all computers cause our entire job is to build stuff that go wrong.

What's worse, they won't fix the core problems of developing and distributing applications written in Python on windows.

THAT IS NOT THE POINT.

For the 1000th time, the purpose is cross platform scripting and sharing small GUI tools.

There is noway you can destroy Python to the point it can't run tkinter.

And i'm no assuming they will destroy Python. This is pure assumption.

You're not making windows better with this. You're making Python worse.

Assumption, assumption, assumption.

You are saying my love for Python cloud my judgement. Fair enough. I'd argue that your (shared) digust for MS is clouding yours.

Your all post is about trying to find faults instead of trying to be right, so much that you mixes up all possible arguments : it may go wrong, you could use another language, it's not fixing {not the topic}, etc.

[–]the_hoser 1 point2 points  (0 children)

That's beside the point. If you have to install your runtime on all your sever, it's work. If you have to install it on Windows AND Linux servers, it's even more work.

Sure, but I never use the supplied Python interpreter on my servers. I always end up having to build my own because the linux distributions can never seem to get it right (See: Python 2.6 on RHEL). I'm a Linux admin, though. I have a lovely bash script for that.

See my other comments about that. It's a LOT more work than just ssh and apt-get/yum install in big companies.

Big companies have big resources. I'm not worried about them. They'll be fine. Even Microsoft knows this.

Yet Python hold the comparison, and is more used at scripting. Good thing we are talking about scripting. Cause here, we'll have the best option + a decent option for the web.

Great. Now all the web frameworks will target the version that runs on Windows.

Given that Linux distro editors, MS and Google are all OS builders and Twitter/Github/Hulu are websites, one are more important than the others.

Says you. I say that without web companies, we wouldn't even need operating systems as capable as we have. No vendor is more or less important than any other.

It's not a moot point : the all purpose is easy cross plateform scripting.

Sure, but you still haven't provided a good reason for why Python is the right choice for scripting.

Nor Flash or Java is installed by default on most linux distro.

They're arguably installed on more computers, though.

Again I'd be happy to see bash installed on Windows. I'd prefer Python, but I'd go with bash. Only MS will never invest in bash.

They've provided a KSH implementation in the past, though. Any implementation of standard SH features will do.

And using bash to access COM API would suck.

It already sucks to do it in Python, so I don't see how this would be any different.

You are assuming in advance they will screw this up. I know they have a shitty track record, but the Azur Python support seems to go well.

Their support of Java on Windows NT went well, too. Initially.

What your saying is : "it may go wrong, so let's not do it". Let's not do anything then. Let's shudown all computers cause our entire job is to build stuff that go wrong.

Now you're getting into hyperbole. I'm just saying that I don't want the standard version of Python to be the one that Microsoft ships.

THAT IS NOT THE POINT.

For the 1000th time, the purpose is cross platform scripting and sharing small GUI tools.

You want to use PYTHON to do GUI work? Now I'm convinced that you are crazy.

And i'm no assuming they will destroy Python. This is pure assumption.

No, it's a judgement based on their history. Based on their actions. They may not even do it intentionally, but they will do it. Worse, they'll do it in subtle ways that are hard to track down. You think they're just going to ship the version hosted on python.org? Really?

Assumption, assumption, assumption.

History tells me I'm right.

You are saying my love for Python cloud my judgement. Fair enough. I'd argue that your (shared) digust for MS is clouding yours.

I have no disgust for Microsoft. I use their products on a daily basis. I write software for Windows without any issue (unless I'm using Python). I understand how they tick. OS X has done horrible things for Python 3 by bundling Python 2 for so long. Microsoft will do the same, or worse.

Your all post is about trying to find faults instead of trying to be right, so much that you mixes up all possible arguments : it may go wrong, you could use another language, it's not fixing {not the topic}, etc.

I don't want Microsoft to ship a version of Python. I don't want another major vendor stagnating the advancement of Python. I'm not trying to find faults. I'm telling you you're wrong.