3 ms·
That's a great decision. IT departements already acknowledge the fact that java applets are totally insecure and dangerous , and Java or Flash shouldnt run in t
by camus2 13y ago
That's a great decision. IT departements already acknowledge the fact that java applets are totally insecure and dangerous , and Java or Flash shouldnt run in the browser.
You want to program stuffs in the browser ? use javascript and html5 apis.
You want to do socket stuffs in the browser? use a proxy server.
But dont expose your users to exploits by making them install Java.
You want to build future proof solutions ? stop using applets because you cant learn javascript.
- pkolaczk 13y agoWhat if I need top performance? The only real alternatives are JavaFX or moving off the browser completely (native app). Despite many man-years put into optimisation, JavaScript is still nowhere near in performance. Yeah, I know in some lucky microbenchmarks from Google or Mozilla it can be only 2-4x slower than Java and it is pretty impressive but why do many real JavaScript games/programs struggle on modern hardware as if it was an old Pentium II (see: bombermine [1], quake JS demo [2], circuitlab [3]) or Java applet in year 1998? The only thing that make them look acceptable is that hardware is extremely fast these days. [1] about 25 FPS with random hiccups on my Core i7 Quad @ 2.4-3.5 GHz and proprietary NVidia drivers and Google Chrome [2] https://semitwist.com/articles/article/view/quake-shows-javascript-is-slow-not-fast https://semitwist.com/articles/article/view/quake-shows-java... [3] about 100x slower than old Berkeley Spice (early 90s technology), despite much less accurate models and using similar algorithms (sparse LU decomposition + Newton Raphson)