4 ms·
Smalltalk had a moment at the transition from green screen to PC's, fumbled the everything is a string internet, and never showed-up for the multicore + GPU par
by igouy 3y ago
Smalltalk had a moment at the transition from green screen to PC's, fumbled the everything is a string internet, and never showed-up for the multicore + GPU party.
Meanwhile the nasty statically type checked languages lowered the pain level with non-nullable and type inference for local vars.
- cess11 3y agoPretty sure Pharo has had GPU-support for a long time, and there's RoarVM for "manycore" applications in Smalltalk.
- igouy 3y ago> Pharo has had GPU-support for a long time For highly parallel general-purpose computations? Tell us more! https://chapel-lang.org/docs/technotes/gpu.html https://chapel-lang.org/docs/technotes/gpu.html As-already stated in this discussion RoarVM "hasn't been touched in over 10 years". This discussion is about the Pharo 12 release and supposedly RoarVM is "compatible with Squeak 4.1 and Pharo 1.2 ". https://github.com/smarr/RoarVM https://github.com/smarr/RoarVM
- cess11 3y agoKinda weird to move the goal posts like this.
- igouy 2y agoThe goal posts started at "the multicore + GPU party." For example: "Optimizing Machine Learning Performance at Netsuite with GraalVM and NVIDIA GPUs" https://medium.com/graalvm/optimizing-machine-learning-performance-at-netsuite-with-graalvm-and-nvidia-gpus-d0d40f0b0cf1 https://medium.com/graalvm/optimizing-machine-learning-perfo...
- ginko 3y agoHow else is GPU-support for a programming language to be understood other than that you can write GPU shaders/kernels in it?