Design Principles Behind Smalltalk (1981)

Re:Design Principles Behind Smalltalk (1981) by jolmg on Sunday August 26, 2018 @11:52PM (#17849336)

Thanks for the reply. This is all very interesting.

> Eclipse has its own Java compiler that does incremental compilation on file save.

Unfortunately, this seems to be the other kind of incremental compilation, different from Smalltalk's or Lisp's. As far as I can see, it simply results in faster compilation, and not in run-time program modification.

[ Parent | on HN ]

Re:Design Principles Behind Smalltalk (1981) by pjmlp on Monday August 27, 2018 @02:29AM (#17849783)

Run-time program modification is possible, to a certain extent, when debugging or using libraries like JRebel, which I mentioned.

Again I am not saying you can do everything that Smalltalk allows for, after all it enjoys the flexibility of a dynamic language, just that those environments (.NET and Java) are the closest to the overall experience, from the point of view of someone that used Smalltalk/V back in its golden days.

The dynamism of those IDEs can be traced back to what Xerox PARC was doing on their Mesa/Cedar developer's environment.

http://toastytech.com/guis/cedar.html

https://archive.org/details/bitsavers_xeroxparcteCedarProgra...

These ideas influenced the IDE experience of other statically typed languages.

[ Parent | on HN ]