4 ms·
> Python 3 is happening. Deal with it. Moving a large codebase to v3 is expensive for almost no benefits? Some parts of the community already moves on to Go, e
by frik 12y ago
> Python 3 is happening. Deal with it.
Moving a large codebase to v3 is expensive for almost no benefits? Some parts of the community already moves on to Go, etc. Many third party libraries are v2 only and unmaintained. Many languages that broke backwards compatibility ultimately failed (their community moved on) or split their community. Examples: Modula 2/3/Oberon4, Perl 4/5/6, Lua 5.1(LuaJIT)/5.2, Visual Basic 6/.Net, QBasic/Visual Basic 1, VBA/VBA.Net, J++/J.Net/C#, etc.
Fibers and coroutines are key features of certain language and API's for decades. WinAPI16 had already Fibers (MS Word), Lua's coroutines, Go's goroutines, etc.
- pjmlp 12y agoModula-2 and Modula-3 don't have the same authors, even if the name implies otherwise. Also Oberon had a different purpose than Modula-2.
- frik 12y agoWhat's your point? It's what I meant with split the community. And I meant Oberon 2 (not 4 which doesn't exist) - two different Oberon 2 versions exist. My point was introducing incompatible language changes that splits the community usually isn't that good, in the long run.
- pjmlp 12y agoThose languages are not related other than sharing the Mesa and Cedar language design ideas. In Oberon's case, you have actually Oberon, Oberon-2, Component Pascal, Active Oberon, Zonnon and Oberon-07. It is not the same as the next version of a given language, rather different approaches how to design memory safe languages for systems programming.
- bayesianhorse 12y agoIf you think you don't need to port, then don't port. If you don't like Python, don't use Python.