I am generally against pulling plugins into the core of any software project unless there is a seriously compelling reason
me too...i generaly agree to this notation...
however i feel this is a compelling reason( its very subjective )
i can see the reason of putting so much effort in fixing performance issues for scene-rendering but i dont see a reason for
neglecting resource loading performance...
OgreMain is already a beast of a lib
sorry my bad - i didn't mean changing or touching any source code( i would be crazy to suggest that...

)
what i meant is to add the plugin to ogre's repository as a build-in plugins and to the cmake script + add it to ogreApi docs + enable it by default for SampleBrowser( ogre facelift )
I prefer the Ogre team to worry about core Ogre problems, which are directly related to rendering and scene management.
me too...i generaly agree to this notation...
how ever the code already exist and have been tested hundreds of time( never had a problem... ) so it should'nt take much effort( push merge button and perhaps some cmake magic ) and will yield a huge performance boost on this part of ogre.
waiting for resource to load is so much 1998 - it can be a real turn-off either in tech evaluation( irrlicht vs ogre etc... ), and a huge pain in the development process ( unless you're aware of this plugin, which mostly you don't... )
Also I doubt many people's applications end up like the sample browser
me too...i generaly agree to this notation...
however...some project do...
and any way its a long long long long way to the finish line( the part where application
end up )
dont know the situation on mobile - but i can only assume it is even worse...
so i still protect my stand on this issue...however i must say that i generaly agree with you
