4 ms·

..., but why must everything be in JavaScript and in the web browser? In this case, the point is to make that archived data readily accessible. An internet ar

by caf 10y ago

..., but why must everything be in JavaScript and in the web browser? In this case, the point is to make that archived data readily accessible. An internet archive where you need to track down and install the right native application to view each record is a bit like those rarefied museum collections locked away in the vast basements of large academic departments, accessible only to those few scholars who are familiar with the hoops they need to jump through to be allowed in. I don't think the idea is that if you had, say, a large collection of MOD files you enjoy, that you should throw away your native tracker and use the browser with a JS tracker instead. Rather, the idea is that if there's a discussion somewhere of the early 90s Amiga demoscene you can post a link to a particular MOD file and know that everyone will be able to play it straight from there.

db48x 10y ago
Agreed. An archive where the data is preserved but you have to really work to view things is good, but one where you can just browse is better. Since we don't have to worry about accidental damage caused by people who are just browsing, and people who are just browsing don't limit the ability of a researcher to use other tools, we can both. Another good example is MIDI. As a browser of MIDI files I just want to hear them play. If I'm researching them, then I'll want to take the time to figure out what hardware and software synthesizers people were actually using when they composed them and listened to them. Neither use-case impinges on the other, so there's no reason at all to avoid implementing an in-browser MIDI player. Or an in-browser media player that can play nearly everything, in this case. On the other hand, downloading a 4gb dvd image full of mpeg2 streams is pretty wasteful of bandwidth; if it weren't for the menus and whatnot it'd be better to transcode it to something modern for playback.

by caf 10y ago

db48x 10y ago

Agreed. An archive where the data is preserved but you have to really work to view things is good, but one where you can just browse is better. Since we don't have to worry about accidental damage caused by people who are just browsing, and people who are just browsing don't limit the ability of a researcher to use other tools, we can both. Another good example is MIDI. As a browser of MIDI files I just want to hear them play. If I'm researching them, then I'll want to take the time to figure out what hardware and software synthesizers people were actually using when they composed them and listened to them. Neither use-case impinges on the other, so there's no reason at all to avoid implementing an in-browser MIDI player. Or an in-browser media player that can play nearly everything, in this case. On the other hand, downloading a 4gb dvd image full of mpeg2 streams is pretty wasteful of bandwidth; if it weren't for the menus and whatnot it'd be better to transcode it to something modern for playback.