Yes, performance comparison depends on specific test, since binding logic (at least the
current one) depends on the number of properties, etc. So, if there are lots of classes
with lots properties the outcome for the comparison may be quite different.
Also having fast start-up time as the goal (e.g. my container starts in 2 sec), parsing
has to be fast and optimized for the first run. There is no time to warm up.
Besides that, another thing that worries me and which has been missing attention is
marshalling. With the rapid development of all the advanced unmarshalling features
marshalling has been totally lost. And if we are revisiting our binding needs I think it
makes sense to keep marshalling in mind. Otherwise, we might be trapped.
View the original post :
Reply to the post :