Web Standards vs Non-Standard Practices

Developers should learn and use Web Standards to build websites and applications that are accessible, performant, and compatible with all modern browsers and devices, which is crucial for reaching a broad audience and complying with legal requirements like the Americans with Disabilities Act (ADA) meets developers might learn about non-standard practices to understand legacy systems, troubleshoot issues in unconventional codebases, or adapt to constraints like tight deadlines or limited resources. Here's our take.

Web Standards

Nice Pick

Developers should learn and use Web Standards to build websites and applications that are accessible, performant, and compatible with all modern browsers and devices, which is crucial for reaching a broad audience and complying with legal requirements like the Americans with Disabilities Act (ADA)

Pros

• For example, using semantic HTML and CSS Grid ensures proper structure and layout, while following JavaScript ES6+ standards enables cross-browser functionality
• Related to: html, css

Cons

• Specific tradeoffs depend on your use case

Non-Standard Practices

Developers might learn about non-standard practices to understand legacy systems, troubleshoot issues in unconventional codebases, or adapt to constraints like tight deadlines or limited resources

Pros

• They are relevant when working with proprietary systems, integrating disparate technologies, or in environments where standard solutions are impractical
• Related to: technical-debt, code-maintainability

Cons

• Specific tradeoffs depend on your use case

The Verdict

These tools serve different purposes. Web Standards is a concept while Non-Standard Practices is a methodology. We picked Web Standards based on overall popularity, but your choice depends on what you're building.

The Bottom Line

Web Standards wins

Based on overall popularity. Web Standards is more widely used, but Non-Standard Practices excels in its own space.