4 ms·
We've tried "document modes" before, and it was terrible. And it's even worse for JS and CSS. > Is it really worth breaking all legacy websites? In any organi
by _getify 12y ago
We've tried "document modes" before, and it was terrible. And it's even worse for JS and CSS.
> Is it really worth breaking all legacy websites?
In any organization, this question gets asked of their product's technical debt, many times over, and gets many "no" answers, until finally there's too much, and their "technical bankruptcy" is unavoidable. They suffer the (temporary) pains to deal with some or all of that debt, and get back on track.
I'm just wishing we could treat our industry that way. I think we're "there" at that point of decision. I just want to tip us over the edge into admitting it.
- Siecje 12y agoPeople use legacy solutions because they work. If tutorials started with while you are developing set your browser to developer mode which only allow HTML5 tags to be used. Web developers copy code, that is one of the reasons the web is so great. But if they copy code and it works they will move on without realizing that they are using deprecated tags.
- _getify 12y agoYes, "how we get into this mess" is incredibly complicated and yet far too much a "pit of failure" for developers. But that doesn't mean we have to just accept it'll never change. I take a sense of pride and ownership in the web, and I have big hopes for its future. That means I have to want to try to make it better, not just keep it afloat. I just hope I can inspire others to do the same.