@tt_clown: I’m wondering if I should include “refactoring a lot” in the update information. It’s not important information for the user, but it’s important because the content has changed a lot.
@nishio: Instead of shying away from this kind of thing and saying “We’re not adding any features that users can see…”, you can say “We’re well prepared to add future features and fix bugs! We’ve done everything we can to make it easier to add features and fix bugs in the future! and the user says, “Wow, I can’t wait to see what the future holds! I can’t wait to see what the future holds! I hope the world will become a place where people can say “Wow, I’m looking forward to the future!
@nishio: recently “Version 2 of a piece of software came out, but the functionality had not increased, so some Some users laughed and continued to use version 1 because it had no more features. I remember hearing that the OS update stopped version 1 from working, and the users who had laughed at it were screaming. @nishio: I think it’s a bit obvious that the support priority for “problems that occur with the latest OS if you continue to use an older version when a newer version is available” is low. I think it’s obvious that support for “problems that occur with the latest OS when you continue to use an older version when a newer version is released” has a low priority, but it’s surprisingly unknown to the world, so I think we should be proactive in communicating this to the public.
This page is auto-translated from /nishio/リファクタリングは将来の機能追加の準備 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.