4 ms·
They are still using bitmapped graphics under the hood, which explains some of the limitation. The community has shrunk, which means there's no one to take them
by scroot 8y ago
They are still using bitmapped graphics under the hood, which explains some of the limitation. The community has shrunk, which means there's no one to take them to the world of vector. However, Pharo people are implementing a new vector engine called Bloc.
- protomyth 8y agoPharo is pretty much the future. I wonder if WebAssembly and it’s upcoming ecosystem will be useful to take some load on a future Smalltalk? [edit: since I’m getting the posting too fast crap here is another language mentioned in the article KRL by Danny Bobrow and Terry Winograd https://pdfs.semanticscholar.org/033e/cd544c4e71b14a7d3ee0611a300a20b91232.pdf https://pdfs.semanticscholar.org/033e/cd544c4e71b14a7d3ee061... ]
- scroot 8y agoI think about that all the time. Imagine a Smalltalk VM written in WASM. It could load with every site and every site could just be live Smalltalk.
- sumim 8y agoAlthough it's not WASM, perhaps you will prefer http://squeak.js.org/ http://squeak.js.org/ , a Squeak VM written in JavaScript.
- 3rdAccount 8y agoThere's a guy that's written a nice looking Smalltalk in Ruby that works perfectly well in the browser with rails I think.
- coldtea 8y ago>They are still using bitmapped graphics under the hood, which explains some of the limitation. The community has shrunk, which means there's no one to take them to the world of vector. Most (all?) commercial OSes don't use vectors for their GUIs either.