Joel Spolsky's new article "How Microsoft Lost the API War" at http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
..NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET—trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
..NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!! 24  2999 
Interesting.......
--
Regards
Steven Burn
Ur I.T. Mate Group www.it-mate.co.uk
Keeping it FREE!
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
Dream on. There's a sucker born every minute.
It's an interesting article. quite frankly, it had me laughing. Much of it
is slight of hand though once you are acquainted with the facts on .NET
adoption in industry. Still it's very entertaining, rambles a bit, but you
would have to be mentally ill to think that .NET isn't here to stay.
For instance, productivity isn't by any means distilled down to memory
management. That's just crap. Syntactic structure and ease of use far outway
this. C++ is just a difficult language to master, and all of this difficulty
does not live in manual memory management, though a large part is about it.
It is just a difficult syntax period. There are too many ways to shoot
yourself in the foot even if you didn't play with memory.
Couple that with the fact that the web just isn't mature to do some tasks
and you would realize that the world is big enough to have desktop
programmers and web developers without causing chaos like the author opines.
--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
Amen!
-dlbjr
Discerning resolutions for the alms
I remember in 1991 when VB came out and how many said you couldn't really do
anything with it and how it had a short life. http://en.wikipedia.org/wiki/Visual_...f_Visual_Basic
It's de ja vu all over again! (O:=
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m...
: Joel Spolsky's new article "How Microsoft Lost the API War" at
: http://www.joelonsoftware.com/articles/APIWar.html
: describes how .NET has failed, how classic VB6 and ASP continue to be
: preferred by developers, and how Microsoft has lost control of the
: preferred API.
:
: You really should read the article. Here are some excerpts:
:
: <Joel Spolsky>
: "And yet, people aren't really using .NET much.
: Oh sure, some of them are..."
:
: "instead of .NET unifying and simplifying, we have a big 6-way mess,
: with everybody trying to figure out which development strategy to use
: and whether they can afford to port their existing applications to
: .NET.
:
: "No matter how consistent Microsoft is in their marketing message
: ('just use .NET-trust us!'), most of their customers are still using
: C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
: other development tools from other companies. And the ones that are
: using .NET are using ASP.NET to develop web applications, which run on
: a Windows server but don't require Windows clients, which is a key
: point I'll talk about more when I talk about the web."
:
: "if you're developing a Windows GUI app today using Microsoft's
: 'official' latest-and-greatest Windows programming environment,
: WinForms, you're going to have to start over again in two years to
: support Longhorn and Avalon. Which explains why WinForms is completely
: stillborn. Hope you haven't invested too much in it. Jon Udell found a
: slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
: Avalon?' and asks, 'Why do I have to pick between Windows Forms and
: Avalon?' A good question, and one to which he finds no great answer."
:
: "So you've got the Windows API, you've got VB, and now you've got
: .NET, in several language flavors, and don't get too attached to any
: of that, because we're making Avalon, you see, which will only run on
: the newest Microsoft operating system, which nobody will have for a
: loooong time. And personally I still haven't had time to learn .NET
: very deeply, and we haven't ported Fog Creek's two applications from
: classic ASP and Visual Basic 6.0 to .NET because there's no return on
: investment for us. None. It's just Fire and Motion as far as I'm
: concerned..."
:
: "the Web user interface is about 80% there, and even without new web
: browsers we can probably get 95% there. This is Good Enough for most
: people and it's certainly good enough for developers, who have voted
: to develop almost every significant new application as a web
: application.
:
: Which means, suddenly, Microsoft's API doesn't matter so much. Web
: applications don't require Windows.
:
: It's not that Microsoft didn't notice this was happening. Of course
: they did, and when the implications became clear, they slammed on the
: brakes. Promising new technologies like HTAs and DHTML were stopped in
: their tracks. The Internet Explorer team seems to have disappeared;
: they have been completely missing in action for several years. There's
: no way Microsoft is going to allow DHTML to get any better than it
: already is: it's just too dangerous to their core business, the rich
: client. The big meme at Microsoft these days is: 'Microsoft is betting
: the company on the rich client.'"
:
: "Much as I hate to say it, a huge chunk of developers have long since
: moved to the web and refuse to move back. Most .NET developers are
: ASP.NET developers, developing for Microsoft's web server...None of
: this bodes well for Microsoft and the profits it enjoyed thanks to its
: API power. The new API is HTML, and the new winners in the application
: development marketplace will be the people who can make HTML sing.
: </Joel Spolsky>
:
: The only sentence in the article that I disagree with is:
: JS> "ASP.NET is brilliant; I've been working with web
: JS> development for ten years and it's really just a
: JS> generation ahead of everything out there."
:
: Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
: Microsoft rewrite of some well-known Perl modules available years ago
: that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
:
: dotnetforfood
:
: classic ASP rulez!!!
Errr....... there's a VB8 beta?;
"In 2004 Microsoft released a beta version of Visual Basic 8.0. "
Under "Evolution of Visual Basic"
--
Regards
Steven Burn
Ur I.T. Mate Group www.it-mate.co.uk
Keeping it FREE!
"Roland Hall" <nobody@nowhere> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl... I remember in 1991 when VB came out and how many said you couldn't really
do anything with it and how it had a short life.
http://en.wikipedia.org/wiki/Visual_...f_Visual_Basic
It's de ja vu all over again! (O:=
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation -
http://msdn.microsoft.com/downloads/list/webdev.asp MSDN Library - http://msdn.microsoft.com/library/default.asp
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m...
: Joel Spolsky's new article "How Microsoft Lost the API War" at
: http://www.joelonsoftware.com/articles/APIWar.html
: describes how .NET has failed, how classic VB6 and ASP continue to be
: preferred by developers, and how Microsoft has lost control of the
: preferred API.
:
: You really should read the article. Here are some excerpts:
:
: <Joel Spolsky>
: "And yet, people aren't really using .NET much.
: Oh sure, some of them are..."
:
: "instead of .NET unifying and simplifying, we have a big 6-way mess,
: with everybody trying to figure out which development strategy to use
: and whether they can afford to port their existing applications to
: .NET.
:
: "No matter how consistent Microsoft is in their marketing message
: ('just use .NET-trust us!'), most of their customers are still using
: C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
: other development tools from other companies. And the ones that are
: using .NET are using ASP.NET to develop web applications, which run on
: a Windows server but don't require Windows clients, which is a key
: point I'll talk about more when I talk about the web."
:
: "if you're developing a Windows GUI app today using Microsoft's
: 'official' latest-and-greatest Windows programming environment,
: WinForms, you're going to have to start over again in two years to
: support Longhorn and Avalon. Which explains why WinForms is completely
: stillborn. Hope you haven't invested too much in it. Jon Udell found a
: slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
: Avalon?' and asks, 'Why do I have to pick between Windows Forms and
: Avalon?' A good question, and one to which he finds no great answer."
:
: "So you've got the Windows API, you've got VB, and now you've got
: .NET, in several language flavors, and don't get too attached to any
: of that, because we're making Avalon, you see, which will only run on
: the newest Microsoft operating system, which nobody will have for a
: loooong time. And personally I still haven't had time to learn .NET
: very deeply, and we haven't ported Fog Creek's two applications from
: classic ASP and Visual Basic 6.0 to .NET because there's no return on
: investment for us. None. It's just Fire and Motion as far as I'm
: concerned..."
:
: "the Web user interface is about 80% there, and even without new web
: browsers we can probably get 95% there. This is Good Enough for most
: people and it's certainly good enough for developers, who have voted
: to develop almost every significant new application as a web
: application.
:
: Which means, suddenly, Microsoft's API doesn't matter so much. Web
: applications don't require Windows.
:
: It's not that Microsoft didn't notice this was happening. Of course
: they did, and when the implications became clear, they slammed on the
: brakes. Promising new technologies like HTAs and DHTML were stopped in
: their tracks. The Internet Explorer team seems to have disappeared;
: they have been completely missing in action for several years. There's
: no way Microsoft is going to allow DHTML to get any better than it
: already is: it's just too dangerous to their core business, the rich
: client. The big meme at Microsoft these days is: 'Microsoft is betting
: the company on the rich client.'"
:
: "Much as I hate to say it, a huge chunk of developers have long since
: moved to the web and refuse to move back. Most .NET developers are
: ASP.NET developers, developing for Microsoft's web server...None of
: this bodes well for Microsoft and the profits it enjoyed thanks to its
: API power. The new API is HTML, and the new winners in the application
: development marketplace will be the people who can make HTML sing.
: </Joel Spolsky>
:
: The only sentence in the article that I disagree with is:
: JS> "ASP.NET is brilliant; I've been working with web
: JS> development for ten years and it's really just a
: JS> generation ahead of everything out there."
:
: Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
: Microsoft rewrite of some well-known Perl modules available years ago
: that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
:
: dotnetforfood
:
: classic ASP rulez!!!
I have to question what Joel really knows about .NET.
I also have to question your knowledge as well.
: Whereas in my eyes ASP.NET is not a "generation ahead",
: but merely a Microsoft rewrite of some well-known Perl
: modules available years ago that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
Are you insane?
How do you do this in Classic ASP?
<%
If myCheckbox.Checked = True then
myTableRow.Visible = False
myCustomValidator.Enabled = False
End If
%>
To do this you write a whole bunch of routine or classes yourself but you
still need to have various bits of ASP (at least placeholders) intespersed
in the HTML itself. ASP.NET gets away from all that by giving you an OO and
event-driven programming paradigm, something you don't get with Classic ASP
Cheers
Ken
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m...
: Joel Spolsky's new article "How Microsoft Lost the API War" at
: http://www.joelonsoftware.com/articles/APIWar.html
: describes how .NET has failed, how classic VB6 and ASP continue to be
: preferred by developers, and how Microsoft has lost control of the
: preferred API.
:
: You really should read the article. Here are some excerpts:
:
: <Joel Spolsky>
: "And yet, people aren't really using .NET much.
: Oh sure, some of them are..."
:
: "instead of .NET unifying and simplifying, we have a big 6-way mess,
: with everybody trying to figure out which development strategy to use
: and whether they can afford to port their existing applications to
: .NET.
:
: "No matter how consistent Microsoft is in their marketing message
: ('just use .NET-trust us!'), most of their customers are still using
: C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
: other development tools from other companies. And the ones that are
: using .NET are using ASP.NET to develop web applications, which run on
: a Windows server but don't require Windows clients, which is a key
: point I'll talk about more when I talk about the web."
:
: "if you're developing a Windows GUI app today using Microsoft's
: 'official' latest-and-greatest Windows programming environment,
: WinForms, you're going to have to start over again in two years to
: support Longhorn and Avalon. Which explains why WinForms is completely
: stillborn. Hope you haven't invested too much in it. Jon Udell found a
: slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
: Avalon?' and asks, 'Why do I have to pick between Windows Forms and
: Avalon?' A good question, and one to which he finds no great answer."
:
: "So you've got the Windows API, you've got VB, and now you've got
: .NET, in several language flavors, and don't get too attached to any
: of that, because we're making Avalon, you see, which will only run on
: the newest Microsoft operating system, which nobody will have for a
: loooong time. And personally I still haven't had time to learn .NET
: very deeply, and we haven't ported Fog Creek's two applications from
: classic ASP and Visual Basic 6.0 to .NET because there's no return on
: investment for us. None. It's just Fire and Motion as far as I'm
: concerned..."
:
: "the Web user interface is about 80% there, and even without new web
: browsers we can probably get 95% there. This is Good Enough for most
: people and it's certainly good enough for developers, who have voted
: to develop almost every significant new application as a web
: application.
:
: Which means, suddenly, Microsoft's API doesn't matter so much. Web
: applications don't require Windows.
:
: It's not that Microsoft didn't notice this was happening. Of course
: they did, and when the implications became clear, they slammed on the
: brakes. Promising new technologies like HTAs and DHTML were stopped in
: their tracks. The Internet Explorer team seems to have disappeared;
: they have been completely missing in action for several years. There's
: no way Microsoft is going to allow DHTML to get any better than it
: already is: it's just too dangerous to their core business, the rich
: client. The big meme at Microsoft these days is: 'Microsoft is betting
: the company on the rich client.'"
:
: "Much as I hate to say it, a huge chunk of developers have long since
: moved to the web and refuse to move back. Most .NET developers are
: ASP.NET developers, developing for Microsoft's web server...None of
: this bodes well for Microsoft and the profits it enjoyed thanks to its
: API power. The new API is HTML, and the new winners in the application
: development marketplace will be the people who can make HTML sing.
: </Joel Spolsky>
:
: The only sentence in the article that I disagree with is:
: JS> "ASP.NET is brilliant; I've been working with web
: JS> development for ten years and it's really just a
: JS> generation ahead of everything out there."
:
: Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
: Microsoft rewrite of some well-known Perl modules available years ago
: that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
:
: dotnetforfood
:
: classic ASP rulez!!!
I read the article.
It's nothing more than one guy's rambling opinion.
--
I hope this helps,
Steve C. Orr, MCSD, MVP http://Steve.Orr.net
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
I would say this is Visual Basic 2005 : http://msdn.microsoft.com/vs2005/preview/default.aspx
Patrice
--
"Steven Burn" <pv*@noyb.com> a écrit dans le message de
news:eM**************@TK2MSFTNGP10.phx.gbl... Errr....... there's a VB8 beta?;
"In 2004 Microsoft released a beta version of Visual Basic 8.0. "
Under "Evolution of Visual Basic"
--
Regards
Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Keeping it FREE!
"Roland Hall" <nobody@nowhere> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl... I remember in 1991 when VB came out and how many said you couldn't
really do anything with it and how it had a short life.
http://en.wikipedia.org/wiki/Visual_...f_Visual_Basic
It's de ja vu all over again! (O:=
--
Roland Hall
/* This information is distributed in the hope that it will be useful,
but without any warranty; without even the implied warranty of
merchantability or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation -
http://msdn.microsoft.com/downloads/list/webdev.asp MSDN Library - http://msdn.microsoft.com/library/default.asp
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m...
: Joel Spolsky's new article "How Microsoft Lost the API War" at
: http://www.joelonsoftware.com/articles/APIWar.html
: describes how .NET has failed, how classic VB6 and ASP continue to be
: preferred by developers, and how Microsoft has lost control of the
: preferred API.
:
: You really should read the article. Here are some excerpts:
:
: <Joel Spolsky>
: "And yet, people aren't really using .NET much.
: Oh sure, some of them are..."
:
: "instead of .NET unifying and simplifying, we have a big 6-way mess,
: with everybody trying to figure out which development strategy to use
: and whether they can afford to port their existing applications to
: .NET.
:
: "No matter how consistent Microsoft is in their marketing message
: ('just use .NET-trust us!'), most of their customers are still using
: C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
: other development tools from other companies. And the ones that are
: using .NET are using ASP.NET to develop web applications, which run on
: a Windows server but don't require Windows clients, which is a key
: point I'll talk about more when I talk about the web."
:
: "if you're developing a Windows GUI app today using Microsoft's
: 'official' latest-and-greatest Windows programming environment,
: WinForms, you're going to have to start over again in two years to
: support Longhorn and Avalon. Which explains why WinForms is completely
: stillborn. Hope you haven't invested too much in it. Jon Udell found a
: slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
: Avalon?' and asks, 'Why do I have to pick between Windows Forms and
: Avalon?' A good question, and one to which he finds no great answer."
:
: "So you've got the Windows API, you've got VB, and now you've got
: .NET, in several language flavors, and don't get too attached to any
: of that, because we're making Avalon, you see, which will only run on
: the newest Microsoft operating system, which nobody will have for a
: loooong time. And personally I still haven't had time to learn .NET
: very deeply, and we haven't ported Fog Creek's two applications from
: classic ASP and Visual Basic 6.0 to .NET because there's no return on
: investment for us. None. It's just Fire and Motion as far as I'm
: concerned..."
:
: "the Web user interface is about 80% there, and even without new web
: browsers we can probably get 95% there. This is Good Enough for most
: people and it's certainly good enough for developers, who have voted
: to develop almost every significant new application as a web
: application.
:
: Which means, suddenly, Microsoft's API doesn't matter so much. Web
: applications don't require Windows.
:
: It's not that Microsoft didn't notice this was happening. Of course
: they did, and when the implications became clear, they slammed on the
: brakes. Promising new technologies like HTAs and DHTML were stopped in
: their tracks. The Internet Explorer team seems to have disappeared;
: they have been completely missing in action for several years. There's
: no way Microsoft is going to allow DHTML to get any better than it
: already is: it's just too dangerous to their core business, the rich
: client. The big meme at Microsoft these days is: 'Microsoft is betting
: the company on the rich client.'"
:
: "Much as I hate to say it, a huge chunk of developers have long since
: moved to the web and refuse to move back. Most .NET developers are
: ASP.NET developers, developing for Microsoft's web server...None of
: this bodes well for Microsoft and the profits it enjoyed thanks to its
: API power. The new API is HTML, and the new winners in the application
: development marketplace will be the people who can make HTML sing.
: </Joel Spolsky>
:
: The only sentence in the article that I disagree with is:
: JS> "ASP.NET is brilliant; I've been working with web
: JS> development for ten years and it's really just a
: JS> generation ahead of everything out there."
:
: Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
: Microsoft rewrite of some well-known Perl modules available years ago
: that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
:
: dotnetforfood
:
: classic ASP rulez!!!
I had a quick look at that page yesterday..... and did a search on MS's
site. Alas, no mention of VB8 :o(
--
Regards
Steven Burn
Ur I.T. Mate Group www.it-mate.co.uk
Keeping it FREE!
"Patrice" <no****@nowhere.com> wrote in message
news:uk**************@TK2MSFTNGP11.phx.gbl... I would say this is Visual Basic 2005 :
http://msdn.microsoft.com/vs2005/preview/default.aspx
Patrice
--
"Steven Burn" <pv*@noyb.com> a écrit dans le message de
news:eM**************@TK2MSFTNGP10.phx.gbl... Errr....... there's a VB8 beta?;
"In 2004 Microsoft released a beta version of Visual Basic 8.0. "
Under "Evolution of Visual Basic"
--
Regards
Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Keeping it FREE!
"Roland Hall" <nobody@nowhere> wrote in message
news:ec**************@TK2MSFTNGP10.phx.gbl... I remember in 1991 when VB came out and how many said you couldn't really do anything with it and how it had a short life.
http://en.wikipedia.org/wiki/Visual_...f_Visual_Basic
It's de ja vu all over again! (O:=
--
Roland Hall
/* This information is distributed in the hope that it will be useful,
but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation -
http://msdn.microsoft.com/downloads/list/webdev.asp MSDN Library - http://msdn.microsoft.com/library/default.asp
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m...
: Joel Spolsky's new article "How Microsoft Lost the API War" at
: http://www.joelonsoftware.com/articles/APIWar.html
: describes how .NET has failed, how classic VB6 and ASP continue to
be : preferred by developers, and how Microsoft has lost control of the
: preferred API.
:
: You really should read the article. Here are some excerpts:
:
: <Joel Spolsky>
: "And yet, people aren't really using .NET much.
: Oh sure, some of them are..."
:
: "instead of .NET unifying and simplifying, we have a big 6-way mess,
: with everybody trying to figure out which development strategy to
use : and whether they can afford to port their existing applications to
: .NET.
:
: "No matter how consistent Microsoft is in their marketing message
: ('just use .NET-trust us!'), most of their customers are still using
: C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
: other development tools from other companies. And the ones that are
: using .NET are using ASP.NET to develop web applications, which run
on : a Windows server but don't require Windows clients, which is a key
: point I'll talk about more when I talk about the web."
:
: "if you're developing a Windows GUI app today using Microsoft's
: 'official' latest-and-greatest Windows programming environment,
: WinForms, you're going to have to start over again in two years to
: support Longhorn and Avalon. Which explains why WinForms is
completely : stillborn. Hope you haven't invested too much in it. Jon Udell found
a : slide from Microsoft labelled 'How Do I Pick Between Windows Forms
and : Avalon?' and asks, 'Why do I have to pick between Windows Forms and
: Avalon?' A good question, and one to which he finds no great
answer." :
: "So you've got the Windows API, you've got VB, and now you've got
: .NET, in several language flavors, and don't get too attached to any
: of that, because we're making Avalon, you see, which will only run
on : the newest Microsoft operating system, which nobody will have for a
: loooong time. And personally I still haven't had time to learn .NET
: very deeply, and we haven't ported Fog Creek's two applications from
: classic ASP and Visual Basic 6.0 to .NET because there's no return
on : investment for us. None. It's just Fire and Motion as far as I'm
: concerned..."
:
: "the Web user interface is about 80% there, and even without new web
: browsers we can probably get 95% there. This is Good Enough for most
: people and it's certainly good enough for developers, who have voted
: to develop almost every significant new application as a web
: application.
:
: Which means, suddenly, Microsoft's API doesn't matter so much. Web
: applications don't require Windows.
:
: It's not that Microsoft didn't notice this was happening. Of course
: they did, and when the implications became clear, they slammed on
the : brakes. Promising new technologies like HTAs and DHTML were stopped
in : their tracks. The Internet Explorer team seems to have disappeared;
: they have been completely missing in action for several years.
There's : no way Microsoft is going to allow DHTML to get any better than it
: already is: it's just too dangerous to their core business, the rich
: client. The big meme at Microsoft these days is: 'Microsoft is
betting : the company on the rich client.'"
:
: "Much as I hate to say it, a huge chunk of developers have long
since : moved to the web and refuse to move back. Most .NET developers are
: ASP.NET developers, developing for Microsoft's web server...None of
: this bodes well for Microsoft and the profits it enjoyed thanks to
its : API power. The new API is HTML, and the new winners in the
application : development marketplace will be the people who can make HTML sing.
: </Joel Spolsky>
:
: The only sentence in the article that I disagree with is:
: JS> "ASP.NET is brilliant; I've been working with web
: JS> development for ten years and it's really just a
: JS> generation ahead of everything out there."
:
: Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
: Microsoft rewrite of some well-known Perl modules available years
ago : that:
: - use templates to generate dynamic web pages and
: - encrypt form data.
:
: dotnetforfood
:
: classic ASP rulez!!!
Opinions are like a**holes. Not only does everybody have one, but almost all
of them stink.
An opinion is a poor substitute for a fact.
In the absence of facts, avoid holding onto opinions. It might prevent you
from finding the facts later.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
"Ken Schaefer" <ke*******@THISadOpenStatic.com> wrote in message news:<ON**************@TK2MSFTNGP10.phx.gbl>... I have to question what Joel really knows about .NET.
How do you do this in Classic ASP?
<%
If myCheckbox.Checked = True then
myTableRow.Visible = False
myCustomValidator.Enabled = False
End If
%>
One way:
<%
IF myCheckboxChecked = TRUE THEN
myTableRowVisible = FALSE
myCustomValidatorEnabled = FALSE
END IF
%>
Hey, you already know the details!
To do this you write a whole bunch of routine or classes yourself but you
still need to have various bits of ASP (at least placeholders) intespersed
in the HTML itself. ASP.NET gets away from all that by giving you an OO and
event-driven programming paradigm, something you don't get with Classic ASP
And something that you don't really need. You .NET OOPers aren't yet
fully aware of Microsoft's latest moves. I'm not the only one who
thinks you don't need OOP (and event-driven architectures).
Microsoft's Don Box discusses how OOP is no longer useful at http://news.com.com/2100-1046_3-5148148.html :
"Moving developers away from the object-oriented world is a key
element of Microsoft's battle for mindshare with the likes of IBM, Sun
Microsystems, BEA Systems, Oracle and other rivals..."
According to Mr. Box:
"The ability for programs to communicate is a core tenet for the way
we want Longhorn to work," said Box. But, he said, object-oriented
programming is just not all it was made out to be. "What promised in
the '90s to be the most promising technology turned out not to be. By
the 1990s, no one disputed that we could make objects work as an
industry, but we got carried away with the metaphor. We naively said,
'This notion of objects that seems to pan out so well when writing
programs...should work for communications between programs.'"
Read the article and weep for OOP.
..NET is little more than a set of templates combined with several
unnecessarily burdensome new OOP-oriented languages. The consistency
of these languages, manifest in the CLR, is of the sort characterized
by Ralph Waldo Emerson in his famous statement:
"A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines."
Microsoft has many "little minds." They need to learn to think outside
the Box.
dotnetforfood
Ouch! Someone needs their meds!
-dlbjr
Discerning resolutions for the alms
"Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote It's nothing more than one guy's rambling opinion.
concerning Joel Spolsky's outstanding article "How Microsoft Lost the
API War" http://www.joelonsoftware.com/articles/APIWar.html
After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
sites. But only I am reading your (non-informative, boring,
uninteresting, empty, useless, wasted) post!-)
Whose opinions are respected: Spolsky's or yours?
Steve's. Hands down.
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64**************************@posting.google.c om... "Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote It's nothing more than one guy's rambling opinion.
concerning Joel Spolsky's outstanding article "How Microsoft Lost the
API War"
http://www.joelonsoftware.com/articles/APIWar.html
After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
sites. But only I am reading your (non-informative, boring,
uninteresting, empty, useless, wasted) post!-)
Whose opinions are respected: Spolsky's or yours?
So basically, what we need is a web based rich client. http://www.bindows.net/ is a cool attempt, but it is based on JavaScript.
Do you know of any more?
Sharon.
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64**************************@posting.google.c om... "Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote It's nothing more than one guy's rambling opinion.
concerning Joel Spolsky's outstanding article "How Microsoft Lost the
API War"
http://www.joelonsoftware.com/articles/APIWar.html
After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
sites. But only I am reading your (non-informative, boring,
uninteresting, empty, useless, wasted) post!-)
Whose opinions are respected: Spolsky's or yours?
There are plenty of people (like yourself) that like to knock .NET, and
there are plenty of these people on the internet.So references per se are
not a good measure of credibility.
Microsoft employs a lot of very intelligent people, who are working both to
ensure that Microsoft stays at the top of the heap -and- that it keeps its
developers onside (because that's what makes the Microsoft platforms a
compelling choice for business).
So, who's more credible - Spolsky, who has a chip on his shoulder about
..NET? or Microsoft, which is a company that's been a proven winner?
I mean, Spolsky writes stuff like this:
<quote>
And personally I still haven't had time to learn .NET very deeply, and we
haven't ported Fog Creek's two applications from classic ASP and Visual
Basic 6.0 to .NET because there's no return on investment for us. None
</quote>
By his own admission, he knows very little about 'Net. And ROI is not just
about signing new customers - it's also about reducing costs - manageability
and supportability costs. I'm sure Spolsky knows this, but is just being
disingenuous by leaving it out.
He writes stuff like:
<quote>
And here's the clincher: I noticed (and confirmed this with a recruiter
friend) that Windows API programmers here in New York City who know C++ and
COM programming earn about $130,000 a year, while typical Web programmers
using managed code languages (Java, PHP, Perl, even ASP.NET) earn about
$80,000 a year. That's a huge difference, and when I talked to some friends
from Microsoft Consulting Services about this they admitted that Microsoft
had lost a whole generation of developers. The reason it takes $130,000 to
hire someone with COM experience is because nobody bothered learning COM
programming in the last eight years or so, so you have to find somebody
really senior, usually they're already in management, and convince them to
take a job as a grunt programmer, dealing with (God help me) marshalling and
monikers and apartment threading and aggregates and tearoffs and a million
other things that
</quote>
The reason it costs more to hire people like this is because the
applications that *require* this expertise are non-trivial. I can write COM
components without too much trouble. I know a little about threading and
marshalling, but that doesn't mean I can write something that'll work well
in a huge enterprise environment. ON the other hand, the average web
developer doesn't need to work in that environment. There are plenty of web
apps that don't require that expertise. I'm sure Spolsky knows that too, but
he just doesn't bother to mention it. He's choosing to "colour" his story
with the things that support his opinion, leaving out things that everyone
else knows, but which don't support his opinion.
Cheers
Ken
"dotnetforfood" <do***********@yahoo.com> wrote in message
news:64**************************@posting.google.c om...
: "Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote
: > It's nothing more than one guy's rambling opinion.
:
: concerning Joel Spolsky's outstanding article "How Microsoft Lost the
: API War"
: http://www.joelonsoftware.com/articles/APIWar.html
:
: After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
: sites. But only I am reading your (non-informative, boring,
: uninteresting, empty, useless, wasted) post!-)
:
: Whose opinions are respected: Spolsky's or yours?
"dotnetforfood" wrote in message
news:64**************************@posting.google.c om...
: "Steve C. Orr [MVP, MCSD]" <St***@Orr.net> wrote
: > It's nothing more than one guy's rambling opinion.
:
: concerning Joel Spolsky's outstanding article "How Microsoft Lost the
: API War"
: http://www.joelonsoftware.com/articles/APIWar.html
:
: After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
: sites. But only I am reading your (non-informative, boring,
: uninteresting, empty, useless, wasted) post!-)
:
: Whose opinions are respected: Spolsky's or yours?
(___!_{|})
You know what that is? That's Spolsky's butt with your lip prints tattooed
on it.
I doubt I'll hear more dribble this year, unless you keep talking except
when the Demon-crats have their convention.
There are 3 types of people in the world...
.... those that make things happen
.... those that watch things happen
.... those that wonder what happened.
Guess that makes you the wonderer. What is your goal here? Do you really
expect everyone to ooh and ahh and agree with your mindless rantings? Since
when did Spolsky become the voice for development and when did you become
his campaign manager? Is there really a point here or are you as bored with
your life as we are with your posts?
If fun to see how everyone react to someone's opinion.
I might not be the best programmer and know what everything means yet but I
know for a fact that .NET is much better then all other I program in.
It already saved me hours of development time on several website and it
decreased the "space" being used with a few 100mb on sites.
It already has been profitable for me and my friends for who I am making the
sites. They already saved some bucks on the monthly renting webspace
and all this is made possible by .NET. A friend of mine owns a gameshop and
had a MS Access DB with Frontend build in running but since he's opening
a new gameshop he needed that the program would work everywhere. Guess what,
in just 4 days I made the entire program in .NET while I had 6 weeks to
finish it.
I dont care about money and stuff thats going on with programmers and so,
heck I dont even get paid (althrou I wish I was lol) but I program because I
like it.
I learn new things because I like it. and you know, I like .NET :D
Richard
"dotnetforfood" <do***********@yahoo.com> schreef in bericht
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
"Richard" wrote in message
news:40***********************@newsreader.eweka.nl ...
: If fun to see how everyone react to someone's opinion.
: I might not be the best programmer and know what everything means yet but
I
: know for a fact that .NET is much better then all other I program in.
: It already saved me hours of development time on several website and it
: decreased the "space" being used with a few 100mb on sites.
:
: It already has been profitable for me and my friends for who I am making
the
: sites. They already saved some bucks on the monthly renting webspace
: and all this is made possible by .NET. A friend of mine owns a gameshop
and
: had a MS Access DB with Frontend build in running but since he's opening
: a new gameshop he needed that the program would work everywhere. Guess
what,
: in just 4 days I made the entire program in .NET while I had 6 weeks to
: finish it.
:
: I dont care about money and stuff thats going on with programmers and so,
: heck I dont even get paid (althrou I wish I was lol) but I program because
I
: like it.
: I learn new things because I like it. and you know, I like .NET :D
Well said Richard. Giving your opinion about something you've experienced,
good or bad, is informative and a benefit for all. This thread beginning,
and the article referenced, while opinions, are written as "THE WORD" and
any opposition to it returns a comment similar to:
[After 5 days, Spolsky's "rambling opinion" is referenced by over 2500
sites. But only I am reading your (non-informative, boring,
uninteresting, empty, useless, wasted) post!-)
Whose opinions are respected: Spolsky's or yours?]
....which turns this pretty much into nothing more than a flame war. It's
nice to see a refreshing post such as yours.
--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - http://www.microsoft.com/technet/scriptcenter/
WSH 5.6 Documentation - http://msdn.microsoft.com/downloads/list/webdev.asp
MSDN Library - http://msdn.microsoft.com/library/default.asp
D**n! I could have sworn that horse was dead...
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Ken" <Ke*@discussions.microsoft.com> wrote in message
news:24**********************************@microsof t.com... actually, i thought the article was saying that the Windows API was dead
and you're a good example of why. why develop for Windows when making a web
based app is SO much easier to implement/install/etc.?
so he's not saying that asp.net is dead (that's some other guy's title).
he's saying that Microsoft lost the app war with the web.
"Richard" wrote:
If fun to see how everyone react to someone's opinion.
I might not be the best programmer and know what everything means yet
but I know for a fact that .NET is much better then all other I program in.
It already saved me hours of development time on several website and it
decreased the "space" being used with a few 100mb on sites.
It already has been profitable for me and my friends for who I am making
the sites. They already saved some bucks on the monthly renting webspace
and all this is made possible by .NET. A friend of mine owns a gameshop
and had a MS Access DB with Frontend build in running but since he's opening
a new gameshop he needed that the program would work everywhere. Guess
what, in just 4 days I made the entire program in .NET while I had 6 weeks to
finish it.
I dont care about money and stuff thats going on with programmers and
so, heck I dont even get paid (althrou I wish I was lol) but I program
because I like it.
I learn new things because I like it. and you know, I like .NET :D
Richard
"dotnetforfood" <do***********@yahoo.com> schreef in bericht
news:64*************************@posting.google.co m... Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
.NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET-trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
.NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
After reading your post, I couldnt convince my self to read that article. But as I read Alvin Bruney's post, I'll read that article when I want a good laugh. For now I already have had a lot of laughs on the new features recently added to the new java, they just added autoboxing!!!! Aint that cool? The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
The only thing that you disagree with is perhaps the only thing written right in the article.
Abubakar.
http://joehacker.blogspot.com
"dotnetforfood" wrote:
Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
..NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET—trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
..NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!!
Wah Jee Wah!
"Abubakar" wrote: After reading your post, I couldnt convince my self to read that article. But as I read Alvin Bruney's post, I'll read that article when I want a good laugh. For now I already have had a lot of laughs on the new features recently added to the new java, they just added autoboxing!!!! Aint that cool?
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
The only thing that you disagree with is perhaps the only thing written right in the article.
Abubakar.
http://joehacker.blogspot.com
"dotnetforfood" wrote:
Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
Oh sure, some of them are..."
"instead of .NET unifying and simplifying, we have a big 6-way mess,
with everybody trying to figure out which development strategy to use
and whether they can afford to port their existing applications to
..NET.
"No matter how consistent Microsoft is in their marketing message
('just use .NET—trust us!'), most of their customers are still using
C, C++, Visual Basic 6.0, and classic ASP, not to mention all the
other development tools from other companies. And the ones that are
using .NET are using ASP.NET to develop web applications, which run on
a Windows server but don't require Windows clients, which is a key
point I'll talk about more when I talk about the web."
"if you're developing a Windows GUI app today using Microsoft's
'official' latest-and-greatest Windows programming environment,
WinForms, you're going to have to start over again in two years to
support Longhorn and Avalon. Which explains why WinForms is completely
stillborn. Hope you haven't invested too much in it. Jon Udell found a
slide from Microsoft labelled 'How Do I Pick Between Windows Forms and
Avalon?' and asks, 'Why do I have to pick between Windows Forms and
Avalon?' A good question, and one to which he finds no great answer."
"So you've got the Windows API, you've got VB, and now you've got
..NET, in several language flavors, and don't get too attached to any
of that, because we're making Avalon, you see, which will only run on
the newest Microsoft operating system, which nobody will have for a
loooong time. And personally I still haven't had time to learn .NET
very deeply, and we haven't ported Fog Creek's two applications from
classic ASP and Visual Basic 6.0 to .NET because there's no return on
investment for us. None. It's just Fire and Motion as far as I'm
concerned..."
"the Web user interface is about 80% there, and even without new web
browsers we can probably get 95% there. This is Good Enough for most
people and it's certainly good enough for developers, who have voted
to develop almost every significant new application as a web
application.
Which means, suddenly, Microsoft's API doesn't matter so much. Web
applications don't require Windows.
It's not that Microsoft didn't notice this was happening. Of course
they did, and when the implications became clear, they slammed on the
brakes. Promising new technologies like HTAs and DHTML were stopped in
their tracks. The Internet Explorer team seems to have disappeared;
they have been completely missing in action for several years. There's
no way Microsoft is going to allow DHTML to get any better than it
already is: it's just too dangerous to their core business, the rich
client. The big meme at Microsoft these days is: 'Microsoft is betting
the company on the rich client.'"
"Much as I hate to say it, a huge chunk of developers have long since
moved to the web and refuse to move back. Most .NET developers are
ASP.NET developers, developing for Microsoft's web server...None of
this bodes well for Microsoft and the profits it enjoyed thanks to its
API power. The new API is HTML, and the new winners in the application
development marketplace will be the people who can make HTML sing.
</Joel Spolsky>
The only sentence in the article that I disagree with is:
JS> "ASP.NET is brilliant; I've been working with web
JS> development for ten years and it's really just a
JS> generation ahead of everything out there."
Whereas in my eyes ASP.NET is not a "generation ahead", but merely a
Microsoft rewrite of some well-known Perl modules available years ago
that:
- use templates to generate dynamic web pages and
- encrypt form data.
dotnetforfood
classic ASP rulez!!! This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: dotnetforfood |
last post by:
I surveyed market penetration of various server-side technologies
using Google's search facility and posted them to the
microsoft.public.inetserver.asp.general newsgroup. Results are in
number of...
|
by: Tarundeep Singh Kalra |
last post by:
Hi,
i am a VC++ developer (MFC) and i want to use .NET at its best.
But all the samples , tuotorials etc are either in C# or VB.NET.
I have certain doubts :-
1). Is Microsoft going to phase...
|
by: dotnetforfood |
last post by:
Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by...
|
by: Scott |
last post by:
THis may not be the right forum for market questions, I'm looking for
an active set of .Net / C# folks to help us locate the right
information. We're considering .Net for a client and need to be...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
| |
