これはどちらかと言うと，Linux の設計思想の話になるのかもしれません．
hand-edit したい時は，hogeファイルを使えば良いのは分かるのですが，fugoファイルをhand-editできるのなら何故hogeファイルとfugoファイルの2つのファイルがあるのでしょうか？ hogeファイルをfoo APIで変更できるようにしたらfugoファイルは必要ないと思うのですが，それができない理由があるのでしょうか？
もしその辺りの経緯が分かるような情報があれば教えて下さい．
Rating
60
Native
Translation / English
- Posted at 27 Feb 2017 at 20:34
If we were to say which one, we'd maybe be talking about the idea for the Linux plan.
When we want to do hand-edit, if we use a hoge file, the good thing is we can understand it, but if we hand-edit a fugo file, how many of the two hoge and fugo files would there be?
If we can change the hoge file through foo API, I think we won't need the fugo file, but is there a reason why that can't be done?
Could you please let me know if there is any information that can clear things up around those details?
issei2029 likes this translation
When we want to do hand-edit, if we use a hoge file, the good thing is we can understand it, but if we hand-edit a fugo file, how many of the two hoge and fugo files would there be?
If we can change the hoge file through foo API, I think we won't need the fugo file, but is there a reason why that can't be done?
Could you please let me know if there is any information that can clear things up around those details?
Rating
44
Translation / English
- Posted at 27 Feb 2017 at 20:12
This might have to do with the design philosophy of Linux.
I understand I should use hoge file when I want to hand-edit, but why are there two files, hoge file and fugo file, in spite that we can hand-edit fugo file? I believe we do not need fugo file if we make hoge file editable by foo API, but is there any reason we cannot do so?
If you have any information which illustrates the background, please let me know.
issei2029 likes this translation
I understand I should use hoge file when I want to hand-edit, but why are there two files, hoge file and fugo file, in spite that we can hand-edit fugo file? I believe we do not need fugo file if we make hoge file editable by foo API, but is there any reason we cannot do so?
If you have any information which illustrates the background, please let me know.
Rating
52
Translation / English
- Posted at 27 Feb 2017 at 20:26
This might be more about the design concept of Linux.
I understand that we just use hoge file when we would like to hand-edit, however why there exist 2 files, which are hoge file and fugo file, while we can hand-edit fugo file? I think we don't need fugo file if we make hoge file modifiable with foo API though is there any reason why we cannot do it?
Please let me know if you have any information on how it works.
issei2029 likes this translation
I understand that we just use hoge file when we would like to hand-edit, however why there exist 2 files, which are hoge file and fugo file, while we can hand-edit fugo file? I think we don't need fugo file if we make hoge file modifiable with foo API though is there any reason why we cannot do it?
Please let me know if you have any information on how it works.
Rating
50
Translation / English
- Posted at 27 Feb 2017 at 20:21
It might be rather than about thought of design for Linux.
I see that it's ok to use hoge file for hand-edit, but why there are two files as hoge file and fugo if it is possible to hand-edit fugo file? I don't think that it need fugo file, if it can be changed hoge file by foo API. Is there any reason that we can't do it?
Could you tell me some information how to demonstrate them, if you know?
issei2029 likes this translation
I see that it's ok to use hoge file for hand-edit, but why there are two files as hoge file and fugo if it is possible to hand-edit fugo file? I don't think that it need fugo file, if it can be changed hoge file by foo API. Is there any reason that we can't do it?
Could you tell me some information how to demonstrate them, if you know?
Rating
50
Translation / English
- Posted at 27 Feb 2017 at 20:31
It might be concerned with the design concept of Linux.
I can understand that when you want to do hand-edit, you should use hoge file. But, if you can do hand-edit fugo file, then why are there two files, hogo file and fugo file? I think fugo file wouldn't be needed if hogo file would be possible to be changed by foo API. Is there some reason why it wouldn't be?
If you have any information about that, please tell me.
issei2029 likes this translation
I can understand that when you want to do hand-edit, you should use hoge file. But, if you can do hand-edit fugo file, then why are there two files, hogo file and fugo file? I think fugo file wouldn't be needed if hogo file would be possible to be changed by foo API. Is there some reason why it wouldn't be?
If you have any information about that, please tell me.
