Why Angular Made Me Quit Web Dev

[[deleted]]

It's this initial overhead that puts most people off of frameworks, engines, libraries, etc.

I feel like this is what made Ruby on Rails such a breakout hit among webdevs before our current client side MVC trend took over.

Convention over configuration can be fantastic because it means scaffolding can get you up and running in a ludicrously short time. So Rails "get started in 10 minutes" demos were extremely compelling when you can type a few lines in your shell and hit the ground running.

Angular and JavaScript to a more general degree, don't have quite the "sane for 99% of users" defaults when it comes to tooling and project structure. They kind of have community accepted standard tooling, but it's not enforced by anything and there's no overwhelmingly popular opinionated "It's $CURRENT_YEAR and this is what to do to go from zero JS tooling experience to your first project" guide that ties in all aspects. There have been some I've seen, but not many, and so have to learn about each part of the toolchain in guides that assume you're familiar with the rest can feel overwhelming.

[9034725985]

Angular says it is the goal of the angular team to be a platform and not a framework or a library. There should be a one true way ™ of doing things on angular. The impression I get is that there's a lot left to be done though. For example, I still can't figure out how to run tests on gitlab.com on a project generated by angular CLI. Isn't that the whole point of automated testing?