Part of the problem I have found with most windows SDKs it that even though they are laid out in nice separated layers in order to get things to actually work you need to hot wire between so many layers that in the end your wound up tighter then a lump of coal trying to be a diamond.
Unfortunately Mac OS X wasn't around then and most other Unixes were unfriendly to the point of being sadistic. Personally I would have preferred if instead of releasing ICE when they did they had rather spent that time on rebuilding SI using components that would have been cross platform. It also would have kept Softimage off Autodesks radar for a bit longer. Once it was in Autodesks's domain there would never be the will / money /dev time to get that type of task done. That and it kills every time when I install Softimage (in my job I do that a lot) and you install Composite when theres a perfectly good compositor built in (if it had been developed) Unfortunately that's not a developers fault its a managements fault. Softimage is the app where great tech goes to die. To me that is inexcusable. ________________________________________ From: Eugen Sares [sof...@mail.sprit.org] Sent: 14 February 2014 04:17 PM To: softimage@listproc.autodesk.com Subject: Re[2]: Survey - how would you do this? While we are at it, out of interest: could you elaborate a bit what the part of Softimage is that is married so tightly to Windows? UI, event handling, whatever...? Is Soft not laid out in a way so that higher functional levels sit atop 'abstract' lower level ones, so you could make changes down there comparatively easy? Thanks! Eugen ------ Originalnachricht ------ Von: "Luc-Eric Rousseau" <luceri...@gmail.com> An: "softimage@listproc.autodesk.com" <softimage@listproc.autodesk.com> Gesendet: 14.02.2014 15:10:38 Betreff: Re: Survey - how would you do this? >> Unfortunately it will be Softimages achilles heel if they don't find >>a way off of it (which is unlikely given the very small dev team) >> COM doesn't scale the way new 3d apps require. To many bottlenecks. >> > >It's moot, but COM is fine, it's no more or less scalable than C++. >Firefox is entirely built with a cross platform clone of COM, called >XPCOM. The problem is that we made XSI only for a Windows NT-only >future. The mainwin decision was meant to be something temporary until >SGI died out. It's not just COM, it's a 100% windows sdk app. > >On Fri, Feb 14, 2014 at 8:42 AM, Angus Davidson ><angus.david...@wits.ac.za> wrote: >>> Jumping into Modo for my first attempt at particles. Managed to get >>>the following after my allotted 5 minutes >> >> pic.twitter.com/EDOKamNkkn >> >> Just used a plain cube as a poly source. Need to update that with a >>more random rock ;) >> --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com = <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table>
