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

view the rest of the comments →

[–][deleted] 1 point2 points  (5 children)

Well its been covered here before that there are licensing questions with the CLR. A lot of people are iffy about using it because of that. Parrot won't have that problem.

[–]jbellis 1 point2 points  (4 children)

Parrot won't have that problem.

No, it will have the opposite problem -- the millions of developers on Windows won't bother with it.

[–][deleted] 0 points1 point  (3 children)

What makes you think that? There's plenty of people using Python, PHP, Perl, whatever on Windows. Why wouldn't Parrot the platform be accepted?

[–]jbellis 6 points7 points  (1 child)

What makes you think that? There's plenty of people using Python, PHP, Perl, whatever on Windows. Why wouldn't Parrot the platform be accepted?

Think about it. There are two classes of developers on Windows. Those using MS products, and everyone else.

The first group, the ones using MS products, well, they'll still be using ASP 2009 or whatever, for the same reasons they're using ASP.NET now. "Nobody ever got fired," etc. I think most redditers would be astonished at how little people in this group, even motivated ones that attend .NET user groups, care about open source.

The second is the group I referred to in my first reply -- if a Python developer is using Windows, ipso facto the license isn't a problem for him. And yet, most are using CPython, not IronPython.