why flush instead smalltalk?
ruby apropos , mostly change flush rails, nonetheless feels now struggling by the adolescence. there lot similarities between flush smalltalk -- covenant that. notwithstanding carrying some-more surprising syntax, smalltalk (if more) object-oriented beauty ruby.
from i have read, smalltalk seems have flush kick on:
- maturity (developed 1970's)
- stability
- commercial support
- (understands structure code, only calm diffing)
- several
- cross-platform support
- the
it seems flush only reinventing wheel. so, since don't flush developers smalltalk? what does flush have smalltalk doesn't?
for record: i'm flush man small trust smalltalk, nonetheless i'm starting awe why.
edit: i cruise ease-of-scripting emanate addressed . i know it, allows smalltalk unchanging aged calm files, longer need smalltalk ide. following with:
gst smalltalk_file
Comments
Post a Comment