3 ms·
These tips are well and good, but from my perspective this type of article doesn't address the whole problem. It seems to me that an overwhelming problem is no
by talmand 12y ago
These tips are well and good, but from my perspective this type of article doesn't address the whole problem.
It seems to me that an overwhelming problem is not developers building inefficient web pages, it is designers, producers, and marketers demanding we build inefficient web pages. No matter how hard we try to convince such that their requirements are generally not a good idea, they still keep pushing the same stuff.
We need a series of these type of articles intended for non-developers to explain why this efficiency train of thought is important. To stop this nonsense of "developers trying to impose upon the artistic expression of designers" crap.
Personally, I just would like designers to stop designing web pages as if they were magazine layouts and actually design web pages.
- protonfish 12y agoHonestly you can develop the fastest page ever but all it takes is adding tracking and advertising code and it will bog down to uselessness.
- drinchev 12y agoAlso I think most of the rules might drop out with having in mind the scalability problem. If you do reduce CSS, HTML files to the very limit you might have a hard time later when you try to implement another feature. Same applies for JS which is getting more and more complex. Sure you can easily write a single page with vanilla script and even inline it to the HTML, but if you try to support IE it looks like you need to at least include either a library or a more complex JS code. So anyway all those tips are super overthought. The best ( hardest ) coding practice is taking a professional approach and decide where is the boundary between spaghetti code and performance benefit.