2 ms·
Which is yet another case of fix the problems with the existing stack rather than creating a new one. Yah, you don't get to be a hero, and product arch, etc fo
by StillBored 7y ago
Which is yet another case of fix the problems with the existing stack rather than creating a new one.
Yah, you don't get to be a hero, and product arch, etc for making X work better. I have yet to see a convincing argument that X couldn't have been made more secure by bolting on another opt-in extension. Then once in place, like GL ES, you start deprecating all the features used by basically no-one.
- DCKing 7y agoI don't understand your post, nobody mentioned security in this discussion?
- bigger_cheese 7y agoOne of the big issues is there is a heap of legacy cruft in the existing X Stack which makes trying to fix/enhance X difficult. From what I understand the way it is written not easy to cleanly depreciate certain features like you've suggested. So I can totally see the appeal for a clean break from having to maintain strict backwards compatibility with a stack that has its roots in the 1980's.