4 ms·
I've built a plugin-system back in 2003 or so based on the JVM which can load/re-load bytecode relatively easily. (the concept became popular in the JVM world
by beders 4y ago
I've built a plugin-system back in 2003 or so based on the JVM which can load/re-load bytecode relatively easily.
(the concept became popular in the JVM world and lead to abominations like OSGi)
The problems that arose quickly were:
- Executing order of plugins attaching to the same extension point.
- Third party library dependencies having different versions
- Traceability and debugging
- Thread-safety
OTOH, it gave our custom dev team to develop integrations and extensions that could be deployed and maintained independently of the main product.
So there's definitely a use-case in there, but it requires some coordination regardless.
- bhelx 4y agoWould love to hear more about your experience there. > (the concept became popular in the JVM world and lead to abominations like OSGi) I remember this, though it was a couple years before my time. Although some of the underlying technology has changed those problems you outlined have remained the same. These things are all relevant to our next steps. We've been thinking a lot about what developer experience problems need to be solved.