CSC/ECE 517 Fall 2009/wiki1b 11 al: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Static Vs Dynamic Object Oriented Languages from the perspective of Performance= | =Static Vs Dynamic Object Oriented Languages from the perspective of Performance= | ||
==Overview== | ==Overview== | ||
Static languages are known for its conservative[http://en.wikipedia.org/wiki/Type_system] approach to language processing, making most typing decisions at compile time itself thereby allowing the compilers to optimize on the byte code generated and provide better type-error checking. Thus, performance is tweaked in these languages. Dynamic languages, on the other hand, attempt to improve the productivity of the average developer, allowing him more flexibility in terms of type checking and so, delay most typing decisions as much as feasible. Thus they sacrifice slightly on performance, and allow for more expressiveness and freedom. | |||
==Type Systems== | ==Type Systems== | ||
Revision as of 16:07, 21 September 2009
Static Vs Dynamic Object Oriented Languages from the perspective of Performance
Overview
Static languages are known for its conservative[1] approach to language processing, making most typing decisions at compile time itself thereby allowing the compilers to optimize on the byte code generated and provide better type-error checking. Thus, performance is tweaked in these languages. Dynamic languages, on the other hand, attempt to improve the productivity of the average developer, allowing him more flexibility in terms of type checking and so, delay most typing decisions as much as feasible. Thus they sacrifice slightly on performance, and allow for more expressiveness and freedom.