> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
I don’t understand how to work with the intermediate language in such a back-to-front approach, wouldn’t you need to know in advance what pass to implement next so that the input to the current pass matches the output of your next, unimplemented, pass? To me, it seems like the contract is reversed
Every browser can smooth scroll, please stop doing this in JS, manually.
I turn mine off, then you force it on me, and CTRL+F4 is an immediate reflex.
You should report it to sigplan.org. Complaining about it here won't make any difference.
There's also https://news.ycombinator.com/newsguidelines.html -
> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
(2017)
At the time (387 points, 76 comments) https://news.ycombinator.com/item?id=15153956 https://archive.is/gUVNw
2019 edit (388 points, 78 comments) https://news.ycombinator.com/item?id=20408011
I don’t understand how to work with the intermediate language in such a back-to-front approach, wouldn’t you need to know in advance what pass to implement next so that the input to the current pass matches the output of your next, unimplemented, pass? To me, it seems like the contract is reversed