4 ms·
Hopefully this is just a mistake and not a real deprecation. That being said, a little while back when controversy popped up over Chrome's handling of `alert()
by danShumway 5y ago
Hopefully this is just a mistake and not a real deprecation.
That being said, a little while back when controversy popped up over Chrome's handling of `alert()`, there were multiple Google engineers I saw online in various settings talking about how the web developer community needed to take some responsibility to monitor upcoming changes and discussions. I do want to bring up that a good way to encourage that is to have an easy, standardized way to subscribe to these content feeds using any client, using a technology that can be aggregated and curated by 3rd parties, that is easily parseable so that it can be searched and transformed by other programs, and that doesn't require an account to access.
Just a thought for anyone on the Chrome/Google team that is actually interested in improving communication channels with web developers. Maybe don't break @intenttoship?
- dmitriid 5y ago> Just a thought for anyone on the Chrome/Google team that is actually interested in improving communication channels with web developers. No. They are not interested in that. The only communication they are interested in is telling what you should do (including their propaganda vehicle, web.dev). Any disagreement or discussion is forbidden. The most recent example, on CSS modules: https://twitter.com/youyuxi/status/1427406150463537152 https://twitter.com/youyuxi/status/1427406150463537152 See replies by Justin Fagnani Of course, no dissent is allowed: https://twitter.com/youyuxi/status/1427447695942299652 https://twitter.com/youyuxi/status/1427447695942299652 (Evan You is the author of Vue)