Java applet – was it wrong today?

I have some extraordinary computing code that needs to be applied to the data downloaded into the browser Dom and obtained from user interaction I don't want to expose this code I want to know:

Write a web service and communicate with the browser through websocket or http The tradeoff is the speed of interaction (from smooth to poor), and the transportation cost is higher Write a java applet (signature hidden code) that encapsulates the internal logic of the page to allow JavaScript to interact with Java APIs I've seen elsewhere that Java and JS engines may crash in some cases But since I'm just calculating, it's a matter of right and wrong Perhaps, on a multi-core machine, I can use more threads to decompose my work. > Write in JavaScript But JavaScript is hard to test, and it's all in public

Q & A, such as usability of Java applets in the web and several others, are also frustrated

My question is: Java applets are dead technology Now there is no Q & a even on this topic! In addition, Java may not always be bundled with all browsers (desktop, tablet or mobile)?

Is there a better way to complete the same hidden code, using client CPU / ram to minimize data traffic

The web page is on JavaScript / HTML5 / CSS The server has only JSON / XML The data packet is 10-20kb and is updated frequently Computing is expensive and client specific, so I really want to use the client to do this

Thank you.

Solution

I think the biggest disadvantage of the applet is that it assumes that you have a JRE installed on the client Is this really a feasible hypothesis?

Another 5 points:) you mentioned 'open your eyes java script'. You should understand that the only real way to protect computing code is to put computing on the server I mean, even if you have a compiled binary code, Java compilation is easy for skilled attackers to understand The confusion you mentioned (its confusion, not signing jars) makes it a little harder, but it's still not impossible

My only concern is that if you have many clients running computing at the same time and put the computing burden on your server, you may eventually crash

Just my idea, I hope it will help you choose the best direction here