Board index » delphi » Re: Why aren't you upgrading?

2006-10-10 06:45:26 PM
delphi165
Ingvar Nilsen writes:
But seriously, I remember it too - although I surely didnt have the
URL's you gys did :)
--
"Programming is an art form that fights back"
www.KudzuWorld.com/
Need a professional technical speaker at your event? See www.woo-hoo.net
 

Bob Dawson writes:
where after the kool aid everyone is dead. Thats the kool aid I wont
stick around for.
--
"Programming is an art form that fights back"
www.KudzuWorld.com/
Need a professional technical speaker at your event? See www.woo-hoo.net
 

jeffc writes:
the 2 limit just in Chicago alone. Wow!!!!!
WinForms made sense to be behind VCL.NET. It was compatible, better,
and WinForms was just a GDI wrapper anyways. But to wrap WPF would be
really bad IMO.
--
"Programming is an art form that fights back"
www.KudzuWorld.com/
Need a professional technical speaker at your event? See www.woo-hoo.net
 

"Nick Hodges (Borland/DTG)" <XXXX@XXXXX.COM>writes
won't get very far."
--
Download my historical nonfiction and/or satirical (etc.) fiction books free
from here:
www.lulu.com/blackbirdcraven
 

"Clay Shannon" writes:
I'm wondering if by now poor old Nick doesn't have shin bone showing from
kicking at those damn pesky dawgs. ;-)
 

In article <452b3c48$XXXX@XXXXX.COM>,
"Tim Jarvis [Borland/DTG]" <XXXX@XXXXX.COM>writes:
--
-David
Quis custodiet custodes ipsos?
 

Brian Moelk writes:
they didnt do this (ie as it is now). Might be somethig for a 3p. ;)
crtical.
--
"Programming is an art form that fights back"
www.KudzuWorld.com/
Need a professional technical speaker at your event? See www.woo-hoo.net
 

Chad Z. Hower writes:
controls. There are also those security issues which I'd agree for
Client GUI apps, this is less of an issue, but it is still an issue.
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Jeff,
I think the conundrum is, if you're DevCo do you bet the farm on
Microsoft not being able to force the .net issue.
Right now, .net is a choice. How much longer will that be the case?
That's the serious question. If Microsoft can force people, by way of
being the owner of Windows, to use .net and deprecate native apps, then
native apps could become what console/dos apps are now, technically
supported sorta, but no one really uses them for anything other than
utilities now.
I'm not saying it will happen, but it could...and that would be death
to a company that decided to not hedge their bets with .net.
Randy
 

"Randy Magruder" <XXXX@XXXXX.COM>writes news:452bb351
I am so impressed you've got the ear of the Borland insiders.
-d
guid: F81D3051-87D9-4C0B-AF76-5F6683F3F710
 

"Jamie Holloway" <Jamie@>writes
didn't spend enough time covering Microsoft stuff. Write to Dennis and
demand that they rehire me -- at a much higher page rate, of course. ;-)
Dave
 

"Dave Jewell" <XXXX@XXXXX.COM>writes:
but there seems to be a lot less programming content than there
once was. Others like Huw seem to not be getting much work
there either.
Rick Carter
XXXX@XXXXX.COM
Chair, Delphi/Paradox SIG, Cincinnati PC Users Group
 

Randy Magruder writes:
rewritten as a pure .NET application. Remember MS has a ton of native
C++ code.
Office) depend on native code support. They can move towards .NET, but
without the whole ecosystem of applications and broad industry support,
their own profit base will be decimated.
to be unsupported in even 10 years is pretty much FUD as far as I'm
concerned.
They will move towards .NET and they will expose API's, features and
interfaces exclusively in .NET (eventually...post longhorn) and .NET
will be important.
This is why I am advocating a .NET strategy for Delphi more in line with
MS' C++ one: a mixed mode compiler. IMO, this strategy makes sense as
it leverages Delphi's current strength and customer base as well as
pushing it forward in .NET.
--
Brian Moelk
Brain Endeavor LLC
XXXX@XXXXX.COM
 

Ingvar Nilsen writes:
read the entire thing (seeing it now, I do recall it), however it is very
clear that Jeff explained his reasons, there was argument about it, you were
invited to contact John Frazier, and so on.
If the discussion was *purely* about Kylix, technically Jeff was correct and
Kylix did have its own groups. It still remains, as I expected and asserted:
they were not cancelled merely because they *mentioned* Kylix or had Kylix
in the subject line, they were cancelled due to the *content*, which Jeff
judged to be off-topic.
--
Wayne Niddery - Winwright, Inc (www.winwright.ca)
"The only reason some people get lost in thought is because it's
unfamiliar territory." - Paul Fix
 

"I.P. Nichols" <XXXX@XXXXX.COM>writes
referring to some threads that took place in this group a few years back. I
do remember some ill-informed journalists getting hold of the idea, and it
spread from there. it is easy to find vestiges of this stuff: E.g:
discuss.fogcreek.com/joelonsoftware4/default.asp
"Today, the .NET framework works over Win32 - it works by calling Win32
functions. Microsoft is planning to change this in Longhorn - large parts
of the future .NET framework which will exist in Longhorn will NOT run over
Win32. .NET will be the native API of Longhorn and future Windows OSes."
(Mike)
Probably the most damning document I have found is this one:
news.zdnet.com/2100-9595_22-5101117.html
Written by some guy called John Carroll, it states that:
"WIN32 will still exist for backwards compatibility, of course, and native
access APIs will exist for those applications which need it (THOUGH I
SUSPECT THAT MANY OF THEM WILL CALL THE MANAGED APIS THROUGH COM INTEROP).
However, Microsoft intends to ensure that all Longhorn functionality is
accessible from a 100% managed program." (My emphasis)
Sorry Mr. Carroll, but in your dreams, mate. The idea of existing Win32
apps running on top of a Win32 emulation layer which calls down to a managed
API through COM interop is totally laughable. Hint: I press a key in Word.
I go take a shower, take the dog for a walk, get home, make a coffee.
Nope - Word still hasn't displayed that keystroke yet.... ;-)
Dave