Board index » delphi » Mr. Grimes' Farewell

2005-03-07 10:36:40 PM
delphi216
I saw this discussed here earlier IIRC--
www.ddj.com/documents/s=9211/ddj050201dnn/
According to Slashdot, someone at Microsoft has responded to the
criticism in their blog (and Mr. Grimes also responded via comments to
the blog entry). Now to go read it myself. :P
weblogs.asp.net/danielfe/archive/2005/02/22/378343.aspx
And another blog response here (also via Slashdot)--
swigartconsulting.blogs.com/tech_blender/2005/02/grumpy_grimes.ht
ml
Will
--
Want native support in Delphi for AMD64/EM64T? Vote here--
qc.borland.com/wc/qcmain.aspx
 

Will DeWitt Jr. writes:
reply is this:
blogs.msdn.com/danielfe/archive/2004/11/02/251254.aspx
"While the .NET Framework hasn't been around for a long period of time
(shiping in February 2002), there is quite a lot of work being done by
different teams to use the .NET Framework across Microsoft's product
line. Below is a quick list of just some of the ways we're using
managed code in products that ship today and how we plan to use managed
code in the future."
-Craig
--
Craig Stuntz [TeamB] ?Vertex Systems Corp. ?Columbus, OH
Delphi/InterBase Weblog : blogs.teamb.com/craigstuntz
Want to help make Delphi and InterBase better? Use QC!
qc.borland.com -- Vote for important issues
 

Geez, things must be changing at Microsoft. I can recall when even
mentioning "Bob" in any sarcastic manner could cost you your job at
Microsoft. I was part of a consulting group hosted by Microsoft some
years ago and we were instructed in our orientation to make no "funny
comments about Bob". Of course the implication was that Bill was
sensitive to that since it was his Wife's idea. I Guess .Net wasn't
her idea. : - )
--
David Farrell-Garcia
Whidbey Island Software LLC
Posted with XanaNews 1.17.2.7
 

Will DeWitt Jr. writes:
assessment in Biblical terms:
I think the Delphi community is in state of diaspora. I think a large
percentage of the uninterested have found themselves in some sort of a
purgatory. A post win32 and pre .NET limbo. A unique condition which
was hastened by the arrival of Delphi 8 and more specifically with that
of D2005 (which had .NET based IDE for Win32 development as well).
Am I pretty convinced that a large percentage of the Delphi community
would have left the marching bands of .NET go by unnoticed. This, had
it not been for Borland's success in tempting the poor Delphi developer
to take a bite of the fruit from the forbidden .NET tree. Crunch!
Fate sealed.
Some of the Delphi developers have realised their pathetic fate. These
poor souls are not accepting the inevitable. They are not prepared for
their eschatological destinies yet. They want alternatives to .NET.
These are the brave 64-bit Crusaders. Or should I say: 64-bit suicide
bombers? :)
Kind regards
Abdullah
ps. We also have the agnostics who insist on running Win32 on all
future platforms from Microsoft! Shame on them.
 

Craig Stuntz [TeamB] writes:
"Another area where .NET is very VB-like is Microsoft's attitude to the framework.
Microsoft treats .NET as a useful library to extend its products, and to date,
it has not shown any more conviction to the framework.
There have been a few .NET products written entirely in .NET"
In the link you provided, Dan Fernandez comes to Microsoft's defense and
points out several places where Microsoft has used the .NET framework.
However, all this comes back to the original point of Mr. Grimes assertion that
Microsoft hasn't really written that many products entirely in .NET.
( The key word was "entirely". )
Most of those products Dan Fernandez pointed out
were not totally written using 100% .NET technology.
So, it seems to me that Mr. Grimes is correct,
we have yet to see any major software programs such as
IE, Visual Studio, Word, or even WordPad written totally using .NET technology ( such as C# ).
Inquiring minds do wish for evidence that Microsoft has confidence to write major products
totally in the .NET environment without treating it as some sort of library.
I'm still waiting to see the evidence myself.
If anyone has any, please let us know.
 

"David Farrell-Garcia" <XXXX@XXXXX.COM>writes:
She's good at spending Bill's money. ;-)
 

buy them, don't they? :-)
(that's what the "L" stands for). That part of .NET is like a bigger
VCL/RTL. I don't know why people don't understand that.
There are other bits to it, particularly in the web space, but in the
Windows space it is really just like having a bigger version of what we
have in Delphi. it is not scary or threatening or particularly difficult
to learn. It doesn't tie you in to MS any more than writing for Windows
does in the first place. The only real issue some people might have is
performance, and at least in principle, there isn't any reason that
can't be improved.
If you need to use hand-crafted assembler, then by definition that won't
be managed code, of course.
Cheers,
Jim Cooper
__________________________________________
Jim Cooper XXXX@XXXXX.COM
Tabdee Ltd www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
__________________________________________
 

Jim Cooper writes:
a. Evangelists touting it as either the /only/ viable future path for Windows
application development or, at their most extreme, the imminent replacement
for the entire Windows API and harbinger of doom for all unmanaged code.
b. M$ marketroids bolting the .NET appellation on to every passing new technology.
 

recent example of that posted here.
Cheers,
Jim Cooper
__________________________________________
Jim Cooper XXXX@XXXXX.COM
Tabdee Ltd www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
__________________________________________
 

Jim Cooper writes:
 

me though. She still thinks I somehow rigged this :-)
www.koalanet.com.au/australian-slang.html
Cheers,
Jim Cooper
__________________________________________
Jim Cooper XXXX@XXXXX.COM
Tabdee Ltd www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
__________________________________________