4 ms·
I think you're both right. It's tricky to know when to make something a default and when to make it a constant. Especially when it comes to users, who cannot al
by 90s_dev 1y ago
I think you're both right. It's tricky to know when to make something a default and when to make it a constant. Especially when it comes to users, who cannot all be pleased.
- johnisgood 1y agoI think it would just kill flexibility, making it the default makes more sense to me, and you should leave it up to the developers using your product, but it is entirely up to you, of course. If I were to turn this into a constant, I would document it at the very least in the git commit message.
- 90s_dev 1y agoI think a fun solution to this, and the one I adopted, is to leave these power features in here as easter eggs, so that devs are rewarded for finding them. At least for me, it gives me a sense of the fun and excitement of learning GUI dev during the 90s. The screen resizing functionality can be found by anyone who digs into the code a little.
- johnisgood 1y agoThat sounds fair to me!