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: -

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: 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.