Snap is designed to be more expressive and powerful than Scratch. But I find debugging them is very painful. Changing the name of a variable or block for example, could create “holes” in the calling sites but the system can or cannot report an error and fails silently. Snap is IMO more flaky and the team seems more eager to add features than polish the existing ones or make the system mor robust and stable.
If you appreciate when keyboard interaction gets added to a GUI, then you might think of a graphical language as the opposite, as it essentially removes keyboard interaction from what is normally a text-based system.
I have the same gripe and I think it’s just simply that when you are used to being able to just write code, everything else feels like it’s in the way.
Visual coding is a pain to change and move around quickly. It’s just clutter ultimately - if you know how to actually code.
This supports making your own higher order functions. You absolutely can learn software engineering from this. What you can't do is get syntax errors, which makes teaching a classroom of kids by yourself intractable.
from someone who can remember how they even got into programming:
it's because this is BS and just a toy, it's got no connection to the real world.
from the angle of someone trying to make some toy to teach programming, maybe in their head it's like: oh this is so simple and easy it should work perfectly for teaching
but from my experience, most of my learning came from "whats this?" "how do i make a thing like this?"
this doesn't provide a way to accomplish that or to promote curiosity
I think same applies to basic CS courses teaching bits and bytes, it's not really useful to know what bits and bytes are if you don't understand what they're even used for or why you should know what they are
however, this is just my subjective point of view, maybe it differs for others.
Snap! is highly "connected to the real world"! Have you seen what's actually been build with Snap! and Scratch? The ecosystem is chock full of amazing bridges to all kinds of physical stuff:
- Cameras, microphones, audio, pen plotters, 3D (BeetleBlocks).
Snap! 12.1 features new blocks for recognizing Body Language, Bauhaus-style shape compositions, first-class Processes and international translation updates:
>Digital Fabrication and Maker Movement in Education
>The eCraft2Learn project has researched, designed, piloted and validated an ecosystem based on digital fabrication and making technologies for creating computer-supported artefacts. The project aimed at reinforcing personalised learning and teaching in science, technology, engineering, arts and math (STEAM) education and to assist the development of 21st century skills that promote inclusion and employability for youth in the EU. The eCraft2Learn ecosystem supports both formal and informal learning by providing the appropriate digital fabrication.
The "what's this? how do I make a thing like this?" curiosity is exactly how many people get pulled in -- instead of learning abstract syntax first, they're immediately making something move, blink, sing, or stitch on machines they can see. Blocks are the on-ramp, but the project is the motivation.
Different audience than yours, maybe. But "just a toy walled off from reality" undersells what the community has been doing for decades.
It also teaches real world computer science at a college level yet still accessible to kids, not just a stripped down simplified language for younger kids.
"Snap! is Scheme disguised as Scratch" -Brian Harvey
>I admit that my slogan "Snap! is Scheme disguised as Scratch" would sort of push in the direction of hygienic macros. But historically we built Snap! more with the idea of Logo disguised as Scratch. It was just when we added lambda that we started thinking more in Scheme terms.
I've been spending a lot of time with my nephews working on Scratch and Snap.
They also attend local classes and their teachers switched from Snap to this which is way simpler and stickier with my nephews: https://www.microsoft.com/en-us/makecode
Yeah, my nephew loved scratch but he's endlessly devoted to make code. I got him a little Gameboy thing that can play the games he builds, and he keeps sending me games of his and then mercilessly mocking me for not being good at them :(
A couple years ago I went through Flexbox Froggy with him out of curiosity, and the really interesting thing was that he was able to complete all the levels but only by dictating to me what to write, because his eye hand coordination wasn't yet up to the task of typing. He has a laptop now and he's getting better but his fingers just don't work very quickly and accurately yet. It's such an interesting thing developmentally that the visual coding approach is helpful for.
What device did you get your nephew? When I was looking for one, those listed on the Make Code website were pretty bad and expensive (or unavailable). I would love to find an affordable retro handheld like Miyoo or Anbernic with Make Code support.
For those wondering the difference with scratch, it's on the about page:
> About Snap!
> Snap! (formerly BYOB) is a visual, drag-and-drop programming language. It is an extended reimplementation of Scratch (a project of the Lifelong Kindergarten Group at the MIT Media Lab) that allows you to Build Your Own Blocks. It also features first class[1] lists, first class procedures, and first class continuations[2]. These added capabilities make it suitable for a serious introduction to computer science for high school or college students.
Scratch already allows you to create custom Blocks and features lists. This seems like a perfect example of reinventing the wheel (and fragmenting development communities).
Actually there is a large historical overlap between the two communities -- warm, collaborative, always giving credit where due. Different goals, lots of feedback both ways.
Jens Mönig was on the Scratch Team (invited by Mitch Resnick). BYOB was presented at Scratch@MIT 2010 explicitly to merge ideas back into Scratch, not to fork the community:
Scratch => Snap!: browser rewrite timing influenced by Scratch 2.0 plans; Morphic via John Maloney; CC-licensed costumes/sounds used under license.
Shared people: Jens (Scratch Team => Snap! lead), John Maloney (Scratch/Morphic; GP session with Jens at Scratch2015AMS), Bernat Romagosa (Snap!, MicroBlocks, Snap4Arduino -- Bordeaux, Snap!Cons).
[...] I'm also a huge fan of Snap!, which has all the advantages of Logo (Lisp without parenthesis) and Scratch / eToys / Squeak / App Inventor family of block based visual programming languages, but all the power of Scheme.
If you know Scheme, then it's easy to think about Snap!: it's just Scheme with a visual block syntax, but with some functions renamed to make them easier to learn, plus all the stage and turtle graphics stuff from Scratch, running in a web browser!
I didn't realize until watching in amazement as Jens Mönig used his own creation, that it also has full keyboard support, so you can create and edit programs without using the mouse!
It's much easier to teach Scheme to kids by teaching them Snap!, because the user interface is so much better than a text editor.
I attended Snap!Con2023 in Barcelona recently, and we discussed some interesting possible extensions to Snap:
Grammar defining blocks. Right now you can create your own custom vocabularies of blocks that fit together in particular constrained ways, by writing JavaScript Snap! extensions. Develop a set of blocks for visually defining new grammars and vocabularies of custom parameterizable blocks.
For example, a grammar for representing plants with seeds, roots, stems, leaves, flowers, petals, etc. You can assemble and edit them manually by dragging and dropping from a palette, or write programs that generated and interpret and transform them, and pass them around as data, for example as instructions to the embroidery machine to sew, or logo turtle to draw.
Ken Kahn led a discussion about integrating LLMs like ChatGPT with Snap!. He's the developer of eCraft2Learn for teaching kids AI programming. Ken recently made some cool Snap! extensions for integrating LLMs with the speech synthesis and recognition system, and orchestrating conversations between different characters.
Snap!Con2023: Creative uses of Snap! blocks using large language models like GPT:
But when it comes to LLMs, code generation, and code understanding, JavaScript has two huge insurmountable advantages over Snap! or any other block based visual programming languages:
1) First of all it's extremely well known, by both humans and LLMs.
2) And second of all, there's typically no efficient and faithful way to textually represent block based programs in a way that ChatGPT (or humans) can easily understand and generate.
Of course you could just dump out the XML or JSON save file, but that wastes your token budget, and doesn't work well, because the LLM doesn't inherently understand the syntax and semantics of save files the way it deeply groks JavaScript.
You need to define some equivalent text based language to serialize and deserialize your visual programs, or define some equivalency to an existing language, so you can translate back and forth without loss.
Like Relax/NG has an XML syntax and also a simple concise human readable syntax, both which can express the same things.
But no matter what equivalent language you come up with to serialize your block programs into, it'll never be as well known as JavaScript (unless it IS JavaScript).
I think Snap! could take advantage of its equivalency with Scheme, and you could just parse Scheme into Snap! blocks, and the other way around. And ChatGPT knows scheme pretty well, though it's not as ubiquitous and standard as JavaScript.
Logo would not be as good as Scheme, since it has ambiguities, because you need to know the number of parameters a function uses in order to parse it, since it's essentially Lisp without parens. [...]
A big part of it is that you can, to some degree, learn programming from this. But you absolutely cannot learn software engineering from this.
Visual coding is a pain to change and move around quickly. It’s just clutter ultimately - if you know how to actually code.
it's because this is BS and just a toy, it's got no connection to the real world.
from the angle of someone trying to make some toy to teach programming, maybe in their head it's like: oh this is so simple and easy it should work perfectly for teaching
but from my experience, most of my learning came from "whats this?" "how do i make a thing like this?"
this doesn't provide a way to accomplish that or to promote curiosity
I think same applies to basic CS courses teaching bits and bytes, it's not really useful to know what bits and bytes are if you don't understand what they're even used for or why you should know what they are
however, this is just my subjective point of view, maybe it differs for others.
- Arduino / micro:bit / boards (Snap4Arduino, MicroBlocks, many hardware libraries).
How To Setup Snap4Arduino:
https://www.youtube.com/watch?v=Ltzlzk_zkys&list=PL5OeDsbY1E...
- Robots (Finch, Hummingbird, Lego NXT, drones).
Controlling a Finch Robot in Snap!:
https://www.youtube.com/watch?v=6_0EqIbTlkk
- Sewing Machines (TurtleStitch -- driving embroidery from blocks) -- one of my favorites:
Snap!Con 2021 - Turtlestitch: Stitching in Time and Place:
https://www.youtube.com/watch?v=K6ra5ThxkrE
- Cameras, microphones, audio, pen plotters, 3D (BeetleBlocks).
Snap! 12.1 features new blocks for recognizing Body Language, Bauhaus-style shape compositions, first-class Processes and international translation updates:
https://www.youtube.com/watch?v=ID7wYxzHUAc
- Web APIs and IoT (conference workshops on "program the internet" with Snap!).
Reimagining IoT - Snap! Microblocks:
https://www.youtube.com/watch?v=l_P7MoBG250
ML/AI extensions and digital fabrication, like Ken Kahn's eCraft2Learn project.
https://project.ecraft2learn.eu/
>Digital Fabrication and Maker Movement in Education
>The eCraft2Learn project has researched, designed, piloted and validated an ecosystem based on digital fabrication and making technologies for creating computer-supported artefacts. The project aimed at reinforcing personalised learning and teaching in science, technology, engineering, arts and math (STEAM) education and to assist the development of 21st century skills that promote inclusion and employability for youth in the EU. The eCraft2Learn ecosystem supports both formal and informal learning by providing the appropriate digital fabrication.
The "what's this? how do I make a thing like this?" curiosity is exactly how many people get pulled in -- instead of learning abstract syntax first, they're immediately making something move, blink, sing, or stitch on machines they can see. Blocks are the on-ramp, but the project is the motivation.
Different audience than yours, maybe. But "just a toy walled off from reality" undersells what the community has been doing for decades.
It also teaches real world computer science at a college level yet still accessible to kids, not just a stripped down simplified language for younger kids.
"Snap! is Scheme disguised as Scratch" -Brian Harvey
https://forum.snap.berkeley.edu/t/hygienic-macros/3258/6
>I admit that my slogan "Snap! is Scheme disguised as Scratch" would sort of push in the direction of hygienic macros. But historically we built Snap! more with the idea of Logo disguised as Scratch. It was just when we added lambda that we started thinking more in Scheme terms.
They also attend local classes and their teachers switched from Snap to this which is way simpler and stickier with my nephews: https://www.microsoft.com/en-us/makecode
A couple years ago I went through Flexbox Froggy with him out of curiosity, and the really interesting thing was that he was able to complete all the levels but only by dictating to me what to write, because his eye hand coordination wasn't yet up to the task of typing. He has a laptop now and he's getting better but his fingers just don't work very quickly and accurately yet. It's such an interesting thing developmentally that the visual coding approach is helpful for.
> About Snap!
> Snap! (formerly BYOB) is a visual, drag-and-drop programming language. It is an extended reimplementation of Scratch (a project of the Lifelong Kindergarten Group at the MIT Media Lab) that allows you to Build Your Own Blocks. It also features first class[1] lists, first class procedures, and first class continuations[2]. These added capabilities make it suitable for a serious introduction to computer science for high school or college students.
Jens Mönig was on the Scratch Team (invited by Mitch Resnick). BYOB was presented at Scratch@MIT 2010 explicitly to merge ideas back into Scratch, not to fork the community:
https://scratched.gse.harvard.edu/resources/announcing-byob2...
Berkeley has kept showing up at Scratch conferences (Amsterdam 2015, Bordeaux 2017), and the Scratch forums hosted BYOB/Snap! discussion for years:
https://scratch.mit.edu/discuss/topic/4455/
So "NIH syndrome," "reinventing the wheel," and "fragmenting the community" is pretty much the opposite of how these two actually interact.
Documented cross-pollination:
BYOB => Scratch: custom blocks (Scratch 2.0 took command blocks only, not reporters/lambda). That was an explicit goal:
https://en.scratch-wiki.info/wiki/Snap!
Scratch => Snap!: browser rewrite timing influenced by Scratch 2.0 plans; Morphic via John Maloney; CC-licensed costumes/sounds used under license.
Shared people: Jens (Scratch Team => Snap! lead), John Maloney (Scratch/Morphic; GP session with Jens at Scratch2015AMS), Bernat Romagosa (Snap!, MicroBlocks, Snap4Arduino -- Bordeaux, Snap!Cons).
I'll have to add it to my list to go and check out any new updates/features they have.
I can NOT wait to get my little one into something like this!
[...] I'm also a huge fan of Snap!, which has all the advantages of Logo (Lisp without parenthesis) and Scratch / eToys / Squeak / App Inventor family of block based visual programming languages, but all the power of Scheme.
If you know Scheme, then it's easy to think about Snap!: it's just Scheme with a visual block syntax, but with some functions renamed to make them easier to learn, plus all the stage and turtle graphics stuff from Scratch, running in a web browser!
I didn't realize until watching in amazement as Jens Mönig used his own creation, that it also has full keyboard support, so you can create and edit programs without using the mouse!
It's much easier to teach Scheme to kids by teaching them Snap!, because the user interface is so much better than a text editor.
I attended Snap!Con2023 in Barcelona recently, and we discussed some interesting possible extensions to Snap:
Grammar defining blocks. Right now you can create your own custom vocabularies of blocks that fit together in particular constrained ways, by writing JavaScript Snap! extensions. Develop a set of blocks for visually defining new grammars and vocabularies of custom parameterizable blocks.
For example, a grammar for representing plants with seeds, roots, stems, leaves, flowers, petals, etc. You can assemble and edit them manually by dragging and dropping from a palette, or write programs that generated and interpret and transform them, and pass them around as data, for example as instructions to the embroidery machine to sew, or logo turtle to draw.
Turtlestitch - Coded Embroidery:
https://www.turtlestitch.org/page/about
Ken Kahn led a discussion about integrating LLMs like ChatGPT with Snap!. He's the developer of eCraft2Learn for teaching kids AI programming. Ken recently made some cool Snap! extensions for integrating LLMs with the speech synthesis and recognition system, and orchestrating conversations between different characters.
Snap!Con2023: Creative uses of Snap! blocks using large language models like GPT:
https://www.youtube.com/watch?v=d2rNGsbzkXI
Enabling children and beginning programmers to build AI programs:
https://ecraft2learn.github.io/ai/
But when it comes to LLMs, code generation, and code understanding, JavaScript has two huge insurmountable advantages over Snap! or any other block based visual programming languages:
1) First of all it's extremely well known, by both humans and LLMs.
2) And second of all, there's typically no efficient and faithful way to textually represent block based programs in a way that ChatGPT (or humans) can easily understand and generate.
Of course you could just dump out the XML or JSON save file, but that wastes your token budget, and doesn't work well, because the LLM doesn't inherently understand the syntax and semantics of save files the way it deeply groks JavaScript.
You need to define some equivalent text based language to serialize and deserialize your visual programs, or define some equivalency to an existing language, so you can translate back and forth without loss.
Like Relax/NG has an XML syntax and also a simple concise human readable syntax, both which can express the same things.
But no matter what equivalent language you come up with to serialize your block programs into, it'll never be as well known as JavaScript (unless it IS JavaScript).
I think Snap! could take advantage of its equivalency with Scheme, and you could just parse Scheme into Snap! blocks, and the other way around. And ChatGPT knows scheme pretty well, though it's not as ubiquitous and standard as JavaScript.
Logo would not be as good as Scheme, since it has ambiguities, because you need to know the number of parameters a function uses in order to parse it, since it's essentially Lisp without parens. [...]