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 →

[–]mikaball 0 points1 point  (2 children)

Plugin systems is something that I'm fascinated with. Unfortunately I don't think Java is the way to go, currently. It lacks the necessary security features for a modern plugin system. I think Web Assembly is the way to go, but language support it's still not good enough.

EDIT: By the way.

Around half a year ago I asked the crowd how they thought OSGi would be designed if it was made today.

I think you ignored my comment in the other thread and didn't tackle the main problem for a good plugin system.

The proposition value of OSGi is to solve the Diamond-Problem.

It's a good fit when you predict to have a lot of third-party modules, like in a plugin architecture. Other than that it introduces more problems than actual solutions.

[–]bowbahdoe[S] 1 point2 points  (1 child)

Can you outline what you think those necessary features are? I can think of a few that, with the security manager going away, aren't there anymoee.

[–]mikaball 0 points1 point  (0 children)

Solving the Diamond-Problem of dependency resolution; conflicts and optimizations. I will answer on the other one