3 ms·
The absolute lack of professionalism among most web developers—many of whom are essentially glorified framework developers, barely understanding what they’re do
by kome 2y ago
The absolute lack of professionalism among most web developers—many of whom are essentially glorified framework developers, barely understanding what they’re doing—is what led us here. This, combined with a complete disregard for web standards and the W3C (dismissed as too consensual, too European, and too slow of an approach), created the perfect shit-storm.
Google insists on pushing its own "standards". And other browser vendors are criticized for being slow to conform to these non-standards. The result? A web cluttered with pointless animations, devoid of cross-browser compatibility, and drowning in superficial bells and whistles.
And the irony? It’s boring. Every website looks the same.
If you’re not testing across browsers and engines (including non-Chromium ones), you’re not building for the web. You’re shipping Chrome-specific extensions that happen to use HTTP. You are not a developer, you are a plumber, and an incompetent one. Good plumbers are so damn rare.
- rbower 2y agoCost/benefit. If 95% of your users are on Chrome, that's where the business wants you to spend most of your development effort. It's the same issue with game dev. Most games don't support Linux natively because the small user base doesn't justify the time sink for developers. Not saying I like it, but I'm not surprised at the current state of the ecosystem. All developers should understand basic web standards, particularly accessibility.