3 ms·
Yep, I agree with that. The problem is we currently have an implementation that behaves as explained above (planned in isolation, evaluated once), and there ar
by pgaddict 11y ago
Yep, I agree with that.
The problem is we currently have an implementation that behaves as explained above (planned in isolation, evaluated once), and there are applications relying on that behaviour. We can't just change that without breaking them.
- CuriousSkeptic 11y agoTrue. At the same time you can't condemn future users to this suboptimal behavior just because a bad desicion in the past. I'm not arguing for just abruptly reverse the design, but that the aim should be to reverse in an orderly manner with suitable deprecations and migration paths in place.