-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browserify #21
Comments
The main reason is I am primary backend developer. Who wants to browserify it? |
I guess all legacy web apps with applets, java-based algorithms and encryptions on client side (DKIM, signatures etc). These days its more and more common to see modern JS in the browser and no modern (or no at all) Java runtime. |
Good question! It would at least definitely make an excellent demo. @sidorares funny you should mention encryption, I was dreaming about getting GMSS working from http://www.flexiprovider.de/#PQCProvider |
Browser-based Java seems to be dying, but there are still a good number of pages containing ageing Java applications. Particularly for that have been made for educational purposes, perhaps they could live again as pure .js?
In an era that routinely runs C++ in the modern browser, it seems a pity not to try to keep these old things alive. I'm sure there are a ton of old Java applets that would be too hard (e.g. banking, streaming video), but a lot of these edu demos ought to be entirely doable. |
Without looking too far into the details, it's not clear to me why this implementation should be limited to node. What shims, if any, would be needed to make it browserify compatible? Just adm-zip?
The text was updated successfully, but these errors were encountered: