Jason Knight
1 min readApr 30, 2021

--

Which is part of my problem with it. I've never seen anything I would call "good angular code" any more than I've seen "good jQuery code".

As I often say about jQ, the only things I see built with it fall into one of three categories:

1) stuff that would be less code and easier to maintain with out the framework

2) stuff that HTML and CSS can do without any JavaScript in the first place.

3) Things that have no business on a public facing UI in the first place.

And Angular -- for me at least -- has all the same failings and just heaps in more junk.

I cannot grasp how using two to ten times the code needed, riddled with bad practices, can be "well written" or "well structures". Much less readable, maintainable, or efficient.

I take one look at the code and I want to pimp-slap the developers who made the system itself. From my programming background, the tasks I do, and the problems I solve for clients, it and all frameworks like it are a shit-show fueled by ignorance, lame excuses, and propaganda.

The claims of ease, faster development, etc, etc seeming to be nothing more than bald faced LIES.

I just don't get it. NOTHING people say about them seems to be true.

--

--

Jason Knight
Jason Knight

Written by Jason Knight

Accessibility and Efficiency Consultant, Web Developer, Musician, and just general pain in the arse

No responses yet