No other graphical OS I’ve ever header of seems to have this “slow disk read” problem. , for those who don’t know what an inode is.

If you have multiple files with the same format in a folder, it’s not like you’re going to have multiple file accesses… you just cache it in memory and display that how many every times you need.

Plus, it’s not like icons are constantly accessed. The goal of keeping the icons in the metadata is to reduce the disk reads needed to display a folder – it also each file to only require one disk read to display.īut is that really a problem? Are disk reads so slow that we need a whole new file format to deal with icons? No other graphical OS I’ve ever header of seems to have this “slow disk read” problem. The real reason to me, reading the article, seems to be: But why do ICON files, out of all the other ones out there, need to be stored in a single inode or in the file metadata? There are a few different ways to get a small icon size. It’s equivalent to saying, “I want to jump off an airplane because I like the feeling of wind blowing on my face.” While you do get what you’re looking for, there are others, less risky ways of achieving that like rolling the windows down on you car, standing in front of a fan, etc. While I saw that statement, it doesn’t make much sense. This allows Haiku to display icons as several sizes while still keeping the files small enough to fit into an inode So many people questioning the reasons behind the approach when the answer was already in the summary:

How to do bridge text in inkscape