Introducing closures is definitely not going to improve performance, because all the proposals are compile time translations only. What we are trying to achieve with closures is getting rid of boilerplate code which you dont have to write anyway with the latest IDEs. I agree it makes code more easier to write, but it is not like we cant live without it. Meanwhile the argument against closures is that it makes the language complex. Take C for instance. The widespread adoption is mainly due to its simplicity of syntax. With most of the recent languages adopting an interpreter based approach, why hasnt lisp or smalltalk made a comeback? Because they are complex. Complex to write, complex to maintain and complex to read.
Dynamic languages are definitely not suitable for performance criticial applications, but closures doesnt make it better either. So if you still want to code in closures, we should adopt a dynamic language that already supports it and make it faster. No point in trying to make java complex. |
java.net RSS Feeds
