Inprise
شنبه 04 تیر 1384, 19:39 عصر
سلام؛
این نوشتهء پاول جالب و قابل تامله، از دستش ندید ؛ برام جالب بود که لااقل یکی از افراد نزدیک به حلقه مدیریت بورلند که تجربیات شغلی و کارش اش مشابه آنچه من داشته ام هست با من هم عقیده است ( قبلا" در مورد پاول تو تاپیک من باب پروژه های بزرگ مقیاسی که با BCB انجام شده حرف زده شده )
http://www.simventions.com/gustavson/2005/06/customer-interest-needs-net-win32.html
<span dir=ltr>
In fact, as I look around the landscape, I find two things are certain, which don't appear to change anytime soon. For market share and performance, the Windows API is still alive and well. And then, for cross platform capability, Java VM rules over .NET. </span>
<span dir=ltr>
Perhaps what should be encouraged is for Borland to extend the VCL for Delphi and C++Builder personalities to include support for 64-bit Windows. Perhaps a VCL Win64 equivalent to the current VCL Win32 library. Seriously, why put more energy into developing or using a .NET VCL, which provides a wrapper ontop of a wrapper, when we know the Windows API isn't going anywhere. Microsoft surely recognizes that if they dropped support for the win API, the wrath of the world would come upon them. The proof that they wouldn't drop this is that they've already quietly engineered and delievered a Win64 API to carry on their flagship Windows product.</span>
این نوشتهء پاول جالب و قابل تامله، از دستش ندید ؛ برام جالب بود که لااقل یکی از افراد نزدیک به حلقه مدیریت بورلند که تجربیات شغلی و کارش اش مشابه آنچه من داشته ام هست با من هم عقیده است ( قبلا" در مورد پاول تو تاپیک من باب پروژه های بزرگ مقیاسی که با BCB انجام شده حرف زده شده )
http://www.simventions.com/gustavson/2005/06/customer-interest-needs-net-win32.html
<span dir=ltr>
In fact, as I look around the landscape, I find two things are certain, which don't appear to change anytime soon. For market share and performance, the Windows API is still alive and well. And then, for cross platform capability, Java VM rules over .NET. </span>
<span dir=ltr>
Perhaps what should be encouraged is for Borland to extend the VCL for Delphi and C++Builder personalities to include support for 64-bit Windows. Perhaps a VCL Win64 equivalent to the current VCL Win32 library. Seriously, why put more energy into developing or using a .NET VCL, which provides a wrapper ontop of a wrapper, when we know the Windows API isn't going anywhere. Microsoft surely recognizes that if they dropped support for the win API, the wrath of the world would come upon them. The proof that they wouldn't drop this is that they've already quietly engineered and delievered a Win64 API to carry on their flagship Windows product.</span>