[xpto123]

that says it all: the most framework specific part of the article are the links in the end to other articles.

Its good to have feedback from the community, but I wish some of these posts would get down to the specifics, we would all benefit much more. Something like: "I tried to this (details) in Angular and it was difficult, tried to do it again with this other framework and it was much easier".

[itomatik]

the author actually has a series of "Angular Bad" articles on his blog which are more or less specific:

http://www.fse.guru/angular-bad-parts-part-1

http://www.fse.guru/angular-bad-parts-part-2

http://www.fse.guru/angular-bad-parts-part-3

http://www.fse.guru/angular-bad-parts-part-4

http://www.fse.guru/angular-bad-parts-part-5

http://www.fse.guru/angular-bad-parts-part-6

[kfnn]

To me it's not specific enough. In the first part the author claims that

>'Dependency injection lacks some functionality you will need sometime.'

But fails to reveal which functionality he has in mind.

He later claims that 'inheritance is an antipattern' and posts a link to google search results as 'proof'.

Not worth reading, in my opinion.

[atmosx]

> that says it all: the most framework specific part of the article are the links in the end to other articles.

Having to click a link to reach the information you need, isn't a big deal IMHO. It's the content that should be discussed. Personally, I don't see anything wrong with posting links to prior (or other) blog posts.