Right and wrong in the title are a bit too strong.
But I agree that over time the outside factors changes and some issues become non-issues.
Having to compile your resources into single JS / CSS / image file is good example, as this does not offend anyone's choice of language or framework.
Because internet speeds improved and underlining web technology improved too, you could look at it from completely different point of view and maybe split files up based on functionality so you don't accidentally expose something that should be available for limited users.
Actually I believe now the rad thing is to have CSS that handles only above the fold HTML, and another CSS file for the rest.
The problem is when people use these "best practice" lists not understanding the underlining reasoning and not factoring in their own project use cases, but it's even worse when they start rolling eyes when someone isn't doing it exactly like they do.
The beauty of development is, at least for me, there is no 1 right answer.
Also I've noticed when you are feeling stressed about your tech-stack loosing popularity, just wait 5-10 years, and your technology will be "in" again, and you can be leading expert :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Right and wrong in the title are a bit too strong.
But I agree that over time the outside factors changes and some issues become non-issues.
Having to compile your resources into single JS / CSS / image file is good example, as this does not offend anyone's choice of language or framework.
Because internet speeds improved and underlining web technology improved too, you could look at it from completely different point of view and maybe split files up based on functionality so you don't accidentally expose something that should be available for limited users.
Actually I believe now the rad thing is to have CSS that handles only above the fold HTML, and another CSS file for the rest.
The problem is when people use these "best practice" lists not understanding the underlining reasoning and not factoring in their own project use cases, but it's even worse when they start rolling eyes when someone isn't doing it exactly like they do.
The beauty of development is, at least for me, there is no 1 right answer.
Also I've noticed when you are feeling stressed about your tech-stack loosing popularity, just wait 5-10 years, and your technology will be "in" again, and you can be leading expert :D