Good points, thanks. The existing text definitely doesn’t answer those, so I should have said something in my initial post. I thought I knew where I was going with this, but had trouble figuring out how to say it, which is usually a sign that my thinking is fuzzier than I’d like.
I’m deliberately covering much of the same ground as MDN’s tutorial and other similar things. What I’d like to do differently is to make something more interactive than just a textbook analogue. I don’t (quite) want to make this a programming videogame, but I do want to move toward minimal words and lots of things for the reader to try. I’ll probably cut a bunch of the pointless front matter and try to have you typing in bits of code in the first minute or two.
I’d also like to try making the early examples more interesting by being about modifying or adding to existing code rather than being limited by the things you can write from scratch as a complete beginner. Not just for interesting examples but also to encourage people to start reading a little code even if they can’t understand it fully yet.
Audience: people who make interactive digital art? I come more from the graphical video games side of things (tiny space arcade game, weird little turn-based roguelike cave flyer) but I think text offers more possibilities with less complex code.
I’m planning to base the first set of examples on an extremely simple custom choice-based transcript-style setup (along the lines of Inky’s HTML output). And then having side exercises to adapt your work to Twine/Vorple/etc.
But having watched my brother who’s an artist learn game dev through UE4’s drag-n-drop Blueprints scripting followed by Godot’s Python-like scripting and then Lua scripting in Defold, and talked with several writers and other creative types who were trying to start out in programming, I think there’s room for one more.
A lot of existing things are long-winded on the details of the basic things (variables, branches, loops) but take a long time to go anywhere. I tend to find that, with half-decent explanations, people are like, “yeah, yeah, we get what a variable is” but need more help (and practice) figuring out how to get from concept to program. Sort of the ultimate blank-page syndrome. I’d like to try and help with that.