Despite being M$ I gather that .Net or C# is quite good, there are
a lot of such developers in my office but I think you might find more
open source devs on the mintlist ;-)
Whaever the technology, a central system that can quickly build the rpm
and report errors would be a great advantage.
It keeps coming back to the virtual memory issue in trying to maintain
and build on an extensive set of libs.
I have suggested we try to find a "quick" solution that makes a small
step in that direction to try to eliminate this obstacle.
I did once suggest loaded but non-shared libs but I don't have enough
knowledge of mint internals to know if it could work.
It would be a little slower to load than static linked apps but no
worse in memory usage and after all just how many apps would the
average user run simultaneously that will be using the same libs ?
If I had 3 apps, 1st uses libs A and B, 2nd uses B and C, and the
3rd just C
Then each would load it's own copy of the libs so there would be
A, B, B, C and C in memory. Each app can call it's own copy just
like static linked versions.
I haven't been able to find if this has ever been tried.
http://compilers.iecc.com/comparch/article/02-06-017
What was Apple's solution in the M68k era ?
What did the Amiga do ?
Regards,
Peter