Hi nicolas >>>> It's of course cough-able because this complexity then spread into m4 > macros for configure scripts and other such niceties. > > Sure, > - when the VM is not able to handle outside world zoo because a lack > of manpower, and because the outside world changed too fast while we > were sleeping happy in our mickey world,
I like the image :) > - or if we want more than least common denominator between several > underlying platforms, > then yes, it might be better to adopt your strategy, because we can > get more manpower at image level than at VM level... > > However, it's a kind of pact with the devil: we get the power at the > price of introducing the #ifdef hell in the image. > Sure, with a good object model, we might think that it will be easier > to handle such complexity. > But then we're just ignoring the efforts of hordes of programmers > maintaining this shit, and redo all in image. > I'm not sure that it will be sustainable... > Unless of course we focus on a single platform. No necessarily, we have object, encapsulation so we should be able to manage modularity the ifdef plague. After all this is all the idea behind "Transform type check to polymorphism" :) > > Your work is very important, because at least, it will enable powerful > single platform extensions. > But as you see, I just wonder how it would help us to continue > providing ubiquity...
