> Correct. This is a strength and a weakness. I was enamored to Smalltalk early on (back in 95 when I learned it in a course) for this very reason. But then the

> Correct. This is a strength and a weakness. I was enamored to Smalltalk early on (back in 95 when I learned it in a course) for this very reason. But then the Internet was happening, the world of computing became a lot more heterogeneous, and the idea of a mostly uniform world of computing mostly faded away I don't think it was the world of computing becoming more heterogeneous, it was more the desire of the industry majors to push their own backward technologies. What prevented Smalltalk from being used as the tool for developing web pages instead of Java, other than Sun wanting Java to proliferate by making it free, and IBM and the other Smalltalk developers messing up Smalltalk? And today we have Oracle threatening Java by insisting that copying of APIs is infringing. What prevented the Smalltalk interface from becoming the browser interface as well as its main development tool? This was the original idea, the original vision the Dynabook vision. Smalltalk developers should develop it along the lines of Smalltalk/X or Smalltalk/MT and build it all the way up and down as well. Trying to fit it into environments which the industry majors are bent on fragmenting and thwarting in order to buy time put their software, multimedia and storage rental models into place simply won't work. > Sun bought out the company which developed one the fastest Smalltalk implementations to put their developers into creating Java? I meant the VM > Developers are moving on to new things. There is Dart of course (if we are talking about developers of smalltalk), and Kay's VPRI which are attempting to develop the next best thing. The Dart developer experience will never match the Smalltalk developer experience and VPRI is also building on the crippled Javascript/HTML/DOM foundations. I can't see why these smart guys don't see that you cannot build on systems which the industry majors are deliberately hobbling in order to buy time to put the rental models into place. They break it and complain that the standards bodies are slowing things down when they and their proxies are the standards bodies. Smalltalk developers need to knuckle down and get their NPAPI/Pepper/NaCl act together. As that is the only way they can succeed with a browser based act.