4 ms·

VSCode is for professional developers... while this may look beautifully simply (because it is) to experienced developers like you and me, it still isn't partic

by ntoll 8y ago

VSCode is for professional developers... while this may look beautifully simply (because it is) to experienced developers like you and me, it still isn't particularly "friendly" for beginners. The point of Mu is to be the first editor you use... it introduces you to the various concepts and capabilities of IDEs in a simple, approachable and coherent way so you quickly graduate to something like VSCode. As I say in my PyCon talk (linked to in another answer), if you're still using Mu as your main editor after becoming proficient in coding, you're doing it wrong (and should graduate). Hope this makes sense.

sandGorgon 8y ago
vscode has a pretty awesome plugin capability. why did you choose to focus on creating an entirely new editor vs creating a very opinionated plugin for vscode ?
- ntoll 8y ago
  Mu is an accident. I was one of the volunteers who contributed to the BBC micro:bit project under the auspices of the Python Software Foundation. I actually wrote the browser based editor and, like a conscientious developer, tested it on teachers. The feedback was pretty resounding: while the browser is convenient the limitations of not being able to connect to the MicroPython REPL, having to download a hex file, copy it to the device and wait in order to run your code was also a stumbling block. It was a rainy Sunday afternoon and I asked myself, "how hard can it be to write a simple editor that was a native application so I could connect to the REPL and automate the flashing of the device?" Fast forward a bit and Mu appeared, teachers used it with the micro:bit and started asking for it to be a "generic" editor for Python (not just micro:bit). The Raspberry Pi foundation's education team also wanted a generic Python editor based on the feedback they'd received from teachers and learners and so they supported me to make the editor modal (i.e. there's now Python3, PyGame, Adafruit and micro:bit modes) with a visual debugger for Python 3 mode. So, be careful what you hack on a Sunday afternoon... I certainly wasn't expecting this to happen. ;-)
  - sandGorgon 8y ago
    more power to you. what you built is awesome !

by ntoll 8y ago

sandGorgon 8y ago

vscode has a pretty awesome plugin capability. why did you choose to focus on creating an entirely new editor vs creating a very opinionated plugin for vscode ?

ntoll 8y ago
Mu is an accident. I was one of the volunteers who contributed to the BBC micro:bit project under the auspices of the Python Software Foundation. I actually wrote the browser based editor and, like a conscientious developer, tested it on teachers. The feedback was pretty resounding: while the browser is convenient the limitations of not being able to connect to the MicroPython REPL, having to download a hex file, copy it to the device and wait in order to run your code was also a stumbling block. It was a rainy Sunday afternoon and I asked myself, "how hard can it be to write a simple editor that was a native application so I could connect to the REPL and automate the flashing of the device?" Fast forward a bit and Mu appeared, teachers used it with the micro:bit and started asking for it to be a "generic" editor for Python (not just micro:bit). The Raspberry Pi foundation's education team also wanted a generic Python editor based on the feedback they'd received from teachers and learners and so they supported me to make the editor modal (i.e. there's now Python3, PyGame, Adafruit and micro:bit modes) with a visual debugger for Python 3 mode. So, be careful what you hack on a Sunday afternoon... I certainly wasn't expecting this to happen. ;-)
- sandGorgon 8y ago
  more power to you. what you built is awesome !