Right? Angular is far from regular HTML. It makes sense to use, when you want people to get started with interactivity in the web... after that, though, playing with "dependency injection" and "transclusion" is just not good for you.

> It makes sense to use, when you want people to get started with interactivity in the web...

I don't think it makes sense even then. The toolset is just way too complex both for teaching, and even for practical use for small projects.

I mean, when people are supposed to learn about things like HTTP, or the idea that server-side programming involves writing programs (the normal, regular kind) that output text - which will later be sent over the wire to the browser. Or even how the control flows through your application. You know, the basic, fundamental stuff - understanding of which is kind of required to do this job well. All the "we'll teach non-programmers coding with current framework du jour" courses and classes I've seen involve typing in magic invocation that generate shit ton of folders and files that nobody tells you what they do or - more importantly - why they're even there, and that's all for a "hello world" app.

I feel that all the current sexy web classes are aiming to produce code monkeys, not programmers. Which might be an effective way to get someone to bullshit their way into the first job - but I doubt it serves the students long term.

Personally, when I'm teaching someone server-side development, I start with simple programs that print stuff to terminal using the regular printf()/whatever calls, and then show them that websites is what you get when you send that text to a browser instead...

Thanks for the response. That's really useful.

I think that Stanford tries to be trendy, since it's located in Silicon Valley and surrounded by startups.

At least it's not Rails anymore /s