06-09-2011, 10:48 AM
[quote name='Brightcolours' timestamp='1307614475' post='9090']
There are not all that many alternatives to .NET to use certain functionality in Windows... I guess that is the reason for developers of even calculation intensive software to start with .NET. Even if they in the end could do without.
Microsoft themselves do not use .NET for most of their products, but they are privy to OS internals and library access which 3rd party developers have no access to.
[/quote]
I don't think developers are so insane to code the raw conversion itself directly in C#/.NET. But the UI alone feels slow, sluggish and buggy. And at least Adobe manages to develop their applications without .NET. So there seem to be other reasonable ways to access the Windows API.
I would be interested to hear whether Capture One (in recent versions) and Capture NX are as buggy and slow on a Mac as they are on Windows.
There are not all that many alternatives to .NET to use certain functionality in Windows... I guess that is the reason for developers of even calculation intensive software to start with .NET. Even if they in the end could do without.
Microsoft themselves do not use .NET for most of their products, but they are privy to OS internals and library access which 3rd party developers have no access to.
[/quote]
I don't think developers are so insane to code the raw conversion itself directly in C#/.NET. But the UI alone feels slow, sluggish and buggy. And at least Adobe manages to develop their applications without .NET. So there seem to be other reasonable ways to access the Windows API.
I would be interested to hear whether Capture One (in recent versions) and Capture NX are as buggy and slow on a Mac as they are on Windows.