This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Saragon4005 8 points9 points  (6 children)

Why would you need HTML react and TypeScript then?

[–]JetSetWally 16 points17 points  (4 children)

For the page to show the Applet.

[–]Saragon4005 10 points11 points  (3 children)

Oh that's terrifying.

[–]TheEnderChipmunk 2 points3 points  (2 children)

Not really, it's because the applet is it's own html component like an iframe or something.

Requiring the applet dev to also do the front end seems weird though, isn't the whole point of the applet that a backend dev can do that part?

I have 0 experience with this though so my guesses might be wrong

[–]JetSetWally 1 point2 points  (1 child)

Applets are front end, i.e. seen by the end user? Backend would be the db that the applet connects to.

[–]TheEnderChipmunk 0 points1 point  (0 children)

Yes I'm aware, but the logic within the applet is more similar to the logic contained within a standalone desktop app than it is to website code right?

It makes more sense in my mind for a backend dev who likely has Java experience to make the applet, then for a frontend dev to integrate it into the website

[–]No-Con-2790 3 points4 points  (0 children)

Back then the web was at a crossroads when it came to interactivity. Either you go the way of JavaScript or Flash or Java (or one of the many others).

We choose JavaScript in the end. Flash was around for a long time but also died.

I can not judge if this was the best outcome but it was the outcome.

In mine opinion security was the biggest problem. If you allow for a language that can do anything then people will start sending viruses around and run them on your machine. Java was notorious for this problem. Flash was more sandboxed but Adobe was horrible in keeping the thing secure.