News for hackers. Stuff that matters.

A comment on The End of Files: the biggest revolution since the GUI?.

Re:The End of Files: the biggest revolution since the GUI? by V-2 on Tuesday October 22, 2013 @06:47AM (#6590892)
God forbid. For example, whenever I buy an mp3 player, I specifically see that it's one I can use as a regular flash drive and simply drag and drop my mp3 files into a folder.

I don't want to use your iTunes / SuperDuperMusicSynchronizer / Cloaca 9.7 etc., I don't want it to "synchronize and manage my music library", I don't want it to start indexing it, I don't want to learn it.

I know how to manage my files and I only had to learn it ONCE, and it works for my mp3s the same way as for my docs, jpgs etc. It's a universal skill.

[ Parent | on HN ]
Re:The End of Files: the biggest revolution since the GUI? by xmorph on Tuesday October 22, 2013 @07:31AM (#6591078)
+1

I still remember the day when my ipod broke down. Before jumping to the apple store I asked myself if I can't use my old Android phone instead (that I took over from my girlfriend when she got a new shiny iphone).

I plugged it in. It became immediately available as an external drive. I copied my mp3s over. I was done.

Please don't take this away from me...

[ Parent | on HN ]
Re:The End of Files: the biggest revolution since the GUI? by joshka on Tuesday October 22, 2013 @07:56AM (#6591180)
Ever seen mp3fs[1]? Adding a filesystem layer on top of whatever music management software isn't implausible.

[1]: http://khenriks.github.io/mp3fs/

[ Parent | on HN ]
Re:The End of Files: the biggest revolution since the GUI? by V-2 on Tuesday October 22, 2013 @08:09AM (#6591230)
Personally I don't mind extra layers of abstractions at all... as long as they're optional.
[ Parent | on HN ]
Re:The End of Files: the biggest revolution since the GUI? by alkonaut on Tuesday October 22, 2013 @08:23AM (#6591310)
Exactly. So while applications today each create an abstraction (e.g. SQL index) on top of the filesystem, what is really needed to provide the "iOS experience" while keeping normal file systems below, is simply an OS-level index with metadata. I can't see how it can be preferrable to have each application have an inconsistent DB of files and their metadata, versus having the OS/filesystem provide one.

As for the mp3 scenario: for a 1Gb mp3 player its certainly doable to just scan the contents for the files/metadata once in order to show track titles etc. The problem is when the collections of files grow by several orders of magnitude and you need instant lookup of metadata (e.g. a 1Tb photo library, which isn't even especially large these days, my camera takes 25mb photos with hundreds of pieces of metadata that can't be encoded in the filename unlike an mp3 track).

[ Parent | on HN ]