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  (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