This is the spiritual successor of that. "Webmaker" changed from a single product to "a suite of products" at the time, with this tool getting renamed to "Thimble". That thimble used Code Mirror for its editor, and only allowed you to write a single file. Since webpages aren't single files anymore, and haven't been for a while, we made a choice to try to integrate quite a few technologies (Adobe's Brackets as editor with tons of features, Filer for faking a POSIX filesystem in the browser, etc) into something that is both the same, but also a lot better, and the old Thimble got turned off (after about a year of having both up at the same time) last June.
Did you guys look into VS Code as an option for possible in-browser editors?
We didn't, mostly because VS Code didn't exist yet when we added in Brackets. It got released when we were already beta testing, and was still in extreme beta by the time we officially launched the updated tool in August 2015. It would be interesting to see how many other now-existing solutions might work for the code editor part, but at this point it would disturb quite a few people who now use Thimble in the classroom or at learn-to-code events, so while as a contributor PR it would be fantastic, we don't have the man hours to investigate a completely new code editor component (with its own UI that needs tailoring, filesystem requirements, plugin infrastructure, etc).
It would be nice if somebody could mention what changed on Thimble for this to come up again. (It could be that somebody who didn't know about it before just found it, which is cool too.)
when you sign up you get an email saying "Welcome to Mozilla Webmaker! Thank you for joining us to discover, create and share the Web. I'm looking forward to seeing what you create."
It does seem to use a webmaker.org login
This one lets you do a mobile view.
Which is sort of ironic given mobile Mozilla marketshare is less than IE.
FWIW, I use Firefox on Android, and I'm extremely happy with it.
Except for when clicking on hyperlinks doesn't work until the next update!
You do realize that that bug only was shipped in nightly, and only for 3 days, and never in the beta or release channels?
If low market share was a reason not to do something in browser-land, there would only be one browser. If anything, low market share is exactly when you should try to outdo the established competition =)