Forgot your password?
typodupeerror

Comment: Re: Apple not in my best interests either (Score 1) 164

by kthreadd (#47918505) Attached to: Why Apple Should Open-Source Swift -- But Won't

They stopped using gcc for various reasons, the project was stagnant, ridden by core developers that could not agree on a road map, it forked a few times I believe and it was always not only buggy but years behind modern C++ standards. Not to mention gcc is slow and the code it produces was not really fast or small in the recent years.
No idea how it is faring right now.

You should really take a look at gcc 4.9 because your viewpoint is seriously out of date.

Comment: Re: I disagree (Score 1) 164

by kthreadd (#47915781) Attached to: Why Apple Should Open-Source Swift -- But Won't

What is there to stop people from making their own implementations of compilers for swift?

What we've seen from other languages is that patents can potentially be a problem, but I don't know if that's applicable in this case.

Open sourcing the future design of swift however means apple may lose control of how the language develops and could be a hindrance to it's primary use in developing software for it's OSes.

Apple might loose control if someone else makes a better implementation, and that users switch to it. That would be a good thing and motivate Apple to improve their original implementation which might otherwise stagnate.

If it smells it's chemistry, if it crawls it's biology, if it doesn't work it's physics.

Working...