The exciting thing here is that this runs on Squeak in JavaScript. Squeak is a modern Smalltalk, and now it can obviously be run on top of JavaScript. That's dynamic languages all the way down!
Scratch in the Browser
11–18 of 18 posts
Re: Scratch in the Browser
#12Also see Snap!, a fork of scratch3 (the js-only version, not the squeakvm-in-the-browser versrion from TFA). https://snap.berkeley.edu/ Snap! is made by folks previously involved in Berkeley Logo, and has a lot of "missing pieces" that make organizing programs easier: lambdas, cc, and binding functions to definitions (aka build-your-own-blocks).
Re: Scratch in the Browser
#13 - MakeCode for micro:bit [1]
- MakeCode Arcade[2]
[1] https://makecode.microbit.org
[2] https://arcade.makecode.comRe: Scratch in the Browser
#14For those keen on exploring visual programming with children, I recommend visiting the following websites: - MakeCode for micro:bit [1] - MakeCode Arcade[2] [1] https://makecode.microbit.org [2] https://arcade.makecode.com
Re: Scratch in the Browser
#15Re: Scratch in the Browser
#16For those keen on exploring visual programming with children, I recommend visiting the following websites: - MakeCode for micro:bit [1] - MakeCode Arcade[2] [1] https://makecode.microbit.org [2] https://arcade.makecode.com
May I ask why you prefer MakeCode over (modern) Scratch?
- Hardware Integration: MakeCode shines with its support for various microcontrollers like the BBC micro:bit and Adafruit Circuit Playground. It’s a game-changer for classes focusing on electronics or physical computing.
- Ease of Transition to Text Coding: Unlike Scratch, MakeCode lets you flip between block-based and JavaScript code. It’s a neat feature for students transitioning to text-based languages.
- Curriculum Tailoring: MakeCode often comes with tailored projects and curricula, especially useful when you have specific learning goals around hardware.
- Practical Applications: The ability to create physical devices or interactive projects with MakeCode can be really engaging for students, showing them the real-world impact of their coding.
- Community and Resources: Depending on where you are and what you need, the MakeCode community and resources might just align better with your teaching needs.
That said, it really boils down to what you're trying to achieve. Scratch is still king for introducing the very basics of programming and fostering creativity, especially for younger or less experienced coders.
Re: Scratch in the Browser
#17Earlier quoted context omitted.
To be clear, the current version of Scratch (version 3) is written in Javascript and other web technologies. TFA isn't the current version of Scratch. It's Scratch 1.4—which was written in Smalltalk—running in a browser via Squeak. If you've used modern Scratch, it's interesting to see what has changed (and what hasn't).
Ah, thanks. I must've missed a version or two somewhere along the way.
Re: Scratch in the Browser
#18Earlier quoted context omitted.
May I ask why you prefer MakeCode over (modern) Scratch?
As someone who's dabbled in both MakeCode and Scratch, I think there are a few solid reasons to lean towards MakeCode, especially in an educational context: - Hardware Integration: MakeCode shines with its support for various microcontrollers like the BBC micro:bit and Adafruit Circuit Playground. It’s a game-changer for classes focusing on electronics or physical computing. - Ease of Transition to Text Coding: Unlik…