4 ms·
I like how "I don't use it" converts so easily into "no one uses it". I'm afraid people do use it; of course the banks and so on (who probably can migrate to b
by jtheory 13y ago
I like how "I don't use it" converts so easily into "no one uses it".
I'm afraid people do use it; of course the banks and so on (who probably can migrate to better solutions fairly easily); personally, I have a site that's pretty active this time of year, with music theory training applets which can capture MIDI and microphone input in-browser.
I could spend a year to rebuild what I can in JavaScript and HTML5 (there's nothing out there besides Java that'll give me MIDI input, of course), if I had a year to burn, which I don't.
Should I shut down the site entirely (and block thousands of users) because there are security issues appearing in OLD versions of Java, that many browsers don't even let you run anymore? Or should I just encourage browsers to keep refining their control over when applets can run -- so applets can be (again) simple to run by people who actually want them?
I'm leaning towards the latter.
- lucian1900 13y agoAn unmaintained sandbox is worse than no sandbox at all because it gives a false sense of security. The few who have to use it can keep using the old version and it being deprecated would put pressure on the websites that still use it to stop doing so.