|
|
|
|
|
by dvogel
1716 days ago
|
|
That would have been more possible a decade ago when the web browsers were less compatible and sites relied on the lowest common denominator feature set. With the increase in compatibility sites now rely on libraries that each depend on a different 90% of the feature set. Breaking interactions between those dependencies has a cascade effect that leads to really, really, really frustrating experiences today. e.g. a UI that looks perfect and has interaction effects working but a background interaction fails silently. A decade ago compatibility issues were more common but IME they were less frustrating because there was usually a rendering artifact or foreground error that made it clear the author just didn't support your browser. |
|