> Should is interesting because of its subjectiveness. It’s a question that only makes sense to be asked in first person. And you have to know about much more than just design to be able to answer it — you have to understand about business, technology, culture, people. Answering the should question is a skill you only get after many, many years answering questions alike. I wish more front-end designers would consider…
Have been using MS "Dynamics" and wanted to add custom styling as a user. Even small lists/tables have all the off-screen elements destroyed so you can't copy stuff from the page, but also you might have to scroll things into view before they get styled (:has gets broken).
They re-implement tables as a swamp of elements which now lack semantic relationships.
They give the same elements random ids, they're non-deterministic. You can only really style by hierarchy, but for every property they seem to add at least one new element.
Everything about it is slow and cumbersome, and no wonder a simple table has hundreds of elements.
It's so Microsoft, the "don't bake your own widgets" taken to the n-th degree.