P.S. Don't mind the first part above the reply, I'm currently using a mobile
device and I accidentally sent in a draft. :D
16.09.2020 13:11:26 Panagiotis Vasilopoulos <hello@xxxxxxxxxxxxxxx>:
I just went by what seemed the most commonplace format across applications.
We may never know where the user may have used them so far, but having to
look up how a specific MIME
16.09.2020 11:51:17 Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>:
How did you pick that specific style? If we change them we may as well try
to follow the current best practices in MIME types. For example, apparently
the x- prefix is deprecated.
Agreed. I went by what was statistically used in the vast majority of cases,
while carefully avoiding apps that contain "Be", because that would
definitely break some legacy applications that interact with the operating
system that way.
However I'm still unconvinced this is worth changing for existing apps.
You never know where these types could have been used (in user's FileType
associations, in other apps, in launch server jobs, ...) so migrating them
has a rather high risk of breaking things.
If there's a change to be made like that, I would agree with the fact that
there is a high risk involved and that any change like that should be
excessively tested, it's still a matter of fact that the risk wouldn't be as
big with the built-in apps, considering that one can easily do what I did—
use either grep/GitHub or another tool to find MIME types throughout the
source code, and just replace them!
While one could argue that a be_roster pointer could be used to open
applications, most applications (focusing on cross-platform apps), as well as
a decent chunk of Haiku applications, use MIME types to interact with other
applications directly.
I may agree that it's minor, but it's not insignificant, even though it may
look that way because there's a lack of documentation– but if I wanted to
open a Haiku app within my own app, I'd most likely have to look through the
source code of Haiku specifically, in order to achieve what I want to do.
I don't think it should happen that way, really, if consistency is a
desirable goal. I apologize if it appears that I am appealing to emotion way
too much, but I believe it's the equivalent of not naming variables as
defined in the coding style, but the consequence here affects the workflow of
third-party app development in the future, possibly permanently. If not now,
when?
