The execution flow you describe is similar to JS' event loop and (I think, I'm not very experienced at C#) C#'s async/await functionality. It's a godsend in JS for exactly the reasons you describe.
I haven't written any Dream code so I can't / wasn't speaking to the language design itself, and I got started in php and actually mostly like it for its design and accessibility so I wouldn't be the guy to shit on the language. I'm just aware that the platform is kinda crashy and non performant.
isn't space station 13 infamously cursed when it comes to remakes? There have been numerous attempts over the years (mainly because SS13 is built in a terrible unmaintained closed-source engine with a custom language) but all have failed because SS13 is so mechanically dense.
Ah I see - so your issue is with the proliferation of tiny libraries associated with NPM?
That's not inherently an issue with Javascript. I agree that solving every issue with a library is bad in the same way that solving every issue by copy-pasting from stack overflow is bad, but it's not inherent to the language. I primarily work in Javascript these days and I've never actually seen a project that relies on an excess of micro-libraries. A good teacher will teach students to understand programming logic, not to lean on excessive crutches.
for the vast majority of modern projects, you don't need the performance that manual memory management provides. I would bet that 90%+ of modern software is written in a memory-managed language. If you need to leap from JS to C, it's really not that hard. But trying to learn about stack frame allocation and RAII and cache line optimisation is a lot to take on when you've just learned what a variable is.
The abstractions are what's important, memory layout is an implementation detail. Even when you're writing C or assembly, you're still thinking in terms of data flow and logic, you're just having to do a lot of the work manually. Learning the abstractions without the baggage of the implementation detail will get 90% of people 90% of the way. Once you have that solid foundation, you can go on to learn assembly or C if you need it because it's not that big a leap from a coding mindset to a hardware control mindset. But to go straight from no coding experience to hardware control is going to be more difficult for a new student to wrap their head around.
I don't think the average case for new programmers looking to hack something is to start out building a solar powered aquafarm. It's better to teach the fundamentals first, which are easy enough to pick up from Javascript. Most programming courses start with something easy like Java, Python or Pascal for exactly this reason. Then later if they want to complete a more advanced project, they can pick up low level coding - it's not much of a leap, despite how fawny and melodramatic people get over coding in C/assembly/whatever.
The fact that you say your kid is going to the best private school and yet you can't afford other luxuries (while clearly holidaying regularly) makes me think you may be disconnected from the average person's idea of what a luxury is.
I haven't written any Dream code so I can't / wasn't speaking to the language design itself, and I got started in php and actually mostly like it for its design and accessibility so I wouldn't be the guy to shit on the language. I'm just aware that the platform is kinda crashy and non performant.