Now this is something REALLY interesting, useful and good to save time and resources. I'd really love to see an answer from Giancarlo about this; in my opinion, it would be one of the greatest features in Nebula. I'd trade this for 10 crosstalk features or server versions.
i7 3770k :: Asus P8H77-V LE :: 16Gb DDR3 @1600MHz :: Geforce GT 520 :: OCZ-Vertex 128Gb :: WD Black Series 1Tb and Green Series 1Tb :: F*******e Liquid56 :: REAPER 64bit and StudioOne 64bit (both latest versions) :: Win 10 64bit
+1000! This would be absolutely amazing, save lots of resources and possibly allow one to run even more instances of Nebula not necessarily needing a 12GB of Ram machine (although it is becoming the standard today anyway). Also wouldn't loading times be faster for programs already loaded in RAM? Giancarlo, is there a way to implement this?
This question regards to a feature far more efficient (theoretically) and important than the incoming Micro Kernels and (theoretically) wouldn't have any audible compromisses as the Micro Kernels. Could someome from the team please answer if alexhayes idea is possible to implement on Nebula or are there current limitations?
Are we any nearer to an official release for server?
I'm currently jbridging which is sort of working but it doesn't seem that solid...sometimes a Neb instance is just not appearing when selected though fortunately if it's the jbridge version the non jbridged will usually open & vice versa.
But would be fantastic to have a stable purpose built system for bridging Neb.
tumburu wrote:This feature should have been on the top of the list. If implemented in Nebula it could almost make the Server unnecessary.
Not knowing all of the ins and outs of how the code works, I would guess that your supposition is incorrect. Even if it saved the memory space, you cannot just double up the processing. While some people with low RAM counts might be helped by this, the majority of us aren't running into a RAM barrier nearly as often as the CPU barrier even in a 32 bit OS environment.
ok guys, I'll be clear This feature is NOT possible, and it's NOT in line with future implementations and requirements. While ram prices are dropping and onboard ram amount is rising, we need to improve the number of functionalities, not decrease or adding obstacles.
 we can save resources among different instances, in localserver and server edition. Anyway it's NOT a prioritary development.