Python 3k
Via Slashdot:
An interesting discussion about concurrency in Python. I must say, I have to agree. If you design a new language at the moment, you have to ask yourself some questions:
- What does my language do for people using no concurrency at all. Are they hindered by the concurrency support (e.g. slower code execution) ?
- Does my language help people make code for systems with 2-4 cores? How well does it cope with current systems?
- Finally: What about proposed systems with up to 80 cores? Clusters and grids? Webs of embedded devices?
Imho if you break backward compatibility, do it once and do it right. At least provide the tools for future advances in that area. Keeping the GIL is definitive the wrong approach, even if it’s hard to avoid with the current codebase.