ASP.NET的渗透 - 开发人员继续使用VB6& ASP [英] Penetration of ASP.NET - Developers continue to use VB6 & ASP
问题描述
Joel Spolsky的新文章微软如何失去API战争在
http://www.joelonsoftware.com/articles/APIWar .html
描述了.NET如何失败，开发人员如何继续使用经典的VB6和ASP，以及微软如何失去对
首选API。
你真的应该阅读这篇文章。以下是一些摘录：
< Joel Spolsky>
"然而，人们并没有真正使用.NET。
哦，当然，其中一些是...
而不是.NET统一和简化，我们有一个很大的6路混乱，
，每个人都试图找出使用哪种开发策略
以及他们是否有能力将他们现有的应用程序移植到
..NET。
无论微软在他们的营销信息中多么一致
（''只使用.NET？信任我们！''），他们的大多数客户仍然使用
C，C ++，Visual Basic 6.0和经典ASP，更不用说来自其他公司的所有其他开发工具了。使用.NET的那些是使用ASP.NET来开发Web应用程序，这些应用程序在Windows服务器上运行，但不需要Windows客户端，这是一键＃
点我会在谈论网络时谈论更多内容。
如果您正在开发Windows GUI应用程序今天使用微软'
''官方''最新和最好的Windows编程环境，
WinForms，你将不得不重新开始两年后，支持Longhorn和Avalon的
。这就解释了为什么WinForms完全是b $ b死产的原因。希望你没有投入太多。 Jon Udell从微软发现了一张
幻灯片标有我如何在Windows窗体之间选择和
Avalon？并询问，''为什么我必须在Windows窗体和
Avalon？''一个很好的问题，而且他找不到很好的答案。
所以你已经得到了Windows API，你有VB，现在你已经有了几种语言版本的
..NET，并且不会过于依赖任何
，因为我们正在制作Avalon，你知道，它只会运行在最新的微软操作系统上，而这个操作系统没有任何人可以用来支付
loooong时间。而且我个人还没有时间非常深入地学习.NET
，而且我们还没有移植Fog Creek的两个应用程序来自
经典ASP和Visual Basic 6.0到.NET因为我们没有回报
投资。没有。就我而言，只有Fire和Motion才有价值......
Web用户界面约为80那里有％，即使没有新的网页
浏览器我们也可能在那里得到95％。这对于大多数人来说是足够好的，对于那些已经投票开发几乎所有重要的新应用程序作为网络的开发人员来说，这当然足够了。 >
申请。
这意味着，突然之间，微软的API并不重要。 Web
应用程序不需要Windows。
微软并没有注意到这种情况发生了。当然
他们做了，当影响变得清晰时，他们猛烈抨击了
刹车。有希望的新技术如HTA和DHTML在他们的轨道上停止了。 Internet Explorer团队似乎已经消失了;
他们几年来已经完全失踪了。没有办法微软会让DHTML获得更好的价格
已经是：它对他们的核心业务来说太危险了，丰富的
客户端。微软最近的一个重要模仿是：''微软在富客户端上打赌这个公司。''
就像我一样不愿意这么说，很多开发人员早已将b
移到网上并拒绝退回。大多数.NET开发人员都是
ASP.NET开发人员，为微软的网络服务器开发......没有什么是b / b这对微软和它所享受的利润都是好兆头它的
API功率。新的API是HTML，应用程序
开发市场中的新赢家将是能够让HTML唱歌的人。
< / Joel Spolsky>
我不同意的文章中唯一的句子是：
JS> ASP.NET很棒;我一直在网上工作
JS>开发十年，它真的只是一个
JS>在那之前的所有事情发生了。
在我眼里，ASP.NET不是未来的一代，而只是一个微软重写几年前可用的一些着名的Perl模块
：
- 使用模板生成动态网页和
- 加密表单数据。
dotnetforfood
经典ASP规则!!!
< blockquote>有趣的.......
-
问候
史蒂文烧伤
Ur IT Mate Group
www.it-mate.co.uk
保持免费！
" dotnetforfood" <做*********** @ yahoo.com>在消息中写道
news：64 ************************* @ posting.google.co m ... < blockquote class =post_quotes> Joel Spolsky的新文章微软如何失去API战争在
http://www.joelonsoftware.com/articles/APIWar .html
描述了.NET如何失败，开发人员如何继续选择经典的VB6和ASP，以及Microsoft如何失去对
首选API的控制权。 />
你真的应该阅读这篇文章。以下是一些摘录：
< Joel Spolsky>
然而，人们并没有真正使用.NET。
哦，当然，其中一些是。 ..
而不是.NET统一和简化，我们有一个很大的6路混乱，
每个人都想弄清楚使用哪种开发策略
以及他们是否有能力将他们现有的应用程序移植到.NET。
无论微软在他们的营销信息中有多么一致
（''只是使用.NET-相信我们！''），他们的大多数客户仍在使用
C，C ++，Visual Basic 6.0和经典ASP，更不用说其他公司的所有其他开发工具了。那些使用.NET的人正在使用ASP.NET开发Web应用程序，这些应用程序在Windows服务器上运行但不需要Windows客户端，这是一个关键点当我谈论网络时，我会谈论更多内容。
如果您今天使用微软的'官方'开发Windows GUI应用程序'最新和最好的Windows编程环境，WinForms，你将不得不在两年内重新开始支持Longhorn和Avalon。这就解释了为什么WinForms完全是死产的原因。希望你没有投入太多。 Jon Udell发现了一张来自微软的幻灯片标有我如何在Windows窗体和Avalon之间选择？并且问道，''为什么我必须在Windows窗体和Avalon之间选择？ ？''一个很好的问题，而且他找不到很好的答案。
所以你有Windows API，你有VB，现在你'已经有了几种语言版本的.NET，并且不会过于依赖任何一种语言，因为我们正在制作Avalon，你看，它只会在
最新的微软操作系统，没有人会有一个足够的时间。而且我个人还没有时间深入学习.NET，而且我们还没有将Fog Creek的两个应用程序从经典ASP和Visual Basic 6.0移植到.NET，因为对我们来说，投资没有回报。没有。就我而言，它只是Fire和Motion ......
Web用户界面大约有80％，甚至没有新的网络
浏览器我们可能在那里得到95％。对于大多数人来说这是足够好的，对于那些投票赞成将几乎所有重要的新应用程序开发为Web应用程序的开发人员来说，这当然是足够好的。
<这意味着，突然之间，微软的API并不重要。 Web应用程序不需要Windows。
并不是微软没有注意到这种情况正在发生。当然，他们确实这样做了，当影响变得清晰时，他们猛烈地踩刹车。 HTA和DHTML等有前途的新技术已经停止了。 Internet Explorer团队似乎已经消失;
几年来他们已经完全失踪了。没有办法让微软能够让DHTML获得比它更好的优势：它对于他们的核心业务，即富有的客户来说太危险了。微软最近的一个重要模仿是：''微软正在把这家公司押在富客户身上。''
就像我讨厌说的那样，一大块开发人员早已转移到网络上并拒绝退回。大多数.NET开发人员都是ASP.NET开发人员，为微软的网络服务器开发......这对于微软来说是个好兆头，而且由于它的API功能，它带来的好处也是如此。新的API是HTML，应用程序开发市场中的新赢家将是能够让HTML唱歌的人。
< / Joel Spolsky>
唯一的句子在我不同意的文章中是：
JS> ASP.NET很棒;我一直在使用网页
JS>开发十年，它真的只是一个
JS>在那之前的所有事情发生。
在我看来，ASP.NET并不是未来的一代，而只是微软重写一些着名的Perl模块几年前
那个：
- 使用模板生成动态网页和
- 加密表单数据。
dotnetforfood
经典ASP规则!!!
Dream on。每分钟都有一个傻瓜出生。
这是一篇有趣的文章。坦率地说，它让我笑了起来。一旦你熟悉了.NET
在工业中采用的事实，那么它的大部分
都是轻微的。它仍然非常有趣，有点摇摇欲坠，但是你需要精神病才能认为.NET不会留下来。
例如，生产力并不是通过任何方式提炼到记忆中的.b $ b b管理。那只是废话。句法结构和易用性远远超出了这个。 C ++只是一种难以掌握的语言，而且所有这些困难都不会存在于手动内存管理中，尽管很大一部分是关于它的。
它只是一个句法难度很大。即使你没有玩记忆，也有很多方法可以自己在脚下拍摄。
结合网络这一事实做一些任务并不成熟
你会意识到这个世界已经足够大了，可以让桌面程序员和网页开发人员不会像作者那样造成混乱。
-
问候，
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
有花絮吗？在此处获取... http://tinyurl.com/27cok
dotnetforfood <做*********** @ yahoo.com>在消息中写道
news：64 ************************* @ posting.google.co m ... < blockquote class =post_quotes> Joel Spolsky的新文章微软如何失去API战争在
http://www.joelonsoftware.com/articles/APIWar .html
描述了.NET如何失败，开发人员如何继续选择经典的VB6和ASP，以及Microsoft如何失去对
首选API的控制权。 />
你真的应该阅读这篇文章。以下是一些摘录：
< Joel Spolsky>
然而，人们并没有真正使用.NET。
哦，当然，其中一些是。 ..
而不是.NET统一和简化，我们有一个很大的6路混乱，
每个人都想弄清楚使用哪种开发策略
以及他们是否有能力将他们现有的应用程序移植到.NET。
无论微软在他们的营销信息中有多么一致
（''只是使用.NET-相信我们！''），他们的大多数客户仍在使用
C，C ++，Visual Basic 6.0和经典ASP，更不用说其他公司的所有其他开发工具了。那些使用.NET的人正在使用ASP.NET开发Web应用程序，这些应用程序在Windows服务器上运行但不需要Windows客户端，这是一个关键点当我谈论网络时，我会谈论更多内容。
如果您今天使用微软的'官方'开发Windows GUI应用程序'最新和最好的Windows编程环境，WinForms，你将不得不在两年内重新开始支持Longhorn和Avalon。这就解释了为什么WinForms完全是死产的原因。希望你没有投入太多。 Jon Udell发现了一张来自微软的幻灯片标有我如何在Windows窗体和Avalon之间选择？并且问道，''为什么我必须在Windows窗体和Avalon之间选择？ ？''一个很好的问题，而且他找不到很好的答案。
所以你有Windows API，你有VB，现在你'已经有了几种语言版本的.NET，并且不会过于依赖任何一种语言，因为我们正在制作Avalon，你看，它只会在
最新的微软操作系统，没有人会有一个足够的时间。而且我个人还没有时间深入学习.NET，而且我们还没有将Fog Creek的两个应用程序从经典ASP和Visual Basic 6.0移植到.NET，因为对我们来说，投资没有回报。没有。就我而言，它只是Fire和Motion ......
Web用户界面大约有80％，甚至没有新的网络
浏览器我们可能在那里得到95％。对于大多数人来说这是足够好的，对于那些投票赞成将几乎所有重要的新应用程序开发为Web应用程序的开发人员来说，这当然是足够好的。
<这意味着，突然之间，微软的API并不重要。 Web应用程序不需要Windows。
并不是微软没有注意到这种情况正在发生。当然，他们确实这样做了，当影响变得清晰时，他们猛烈地踩刹车。 HTA和DHTML等有前途的新技术已经停止了。 Internet Explorer团队似乎已经消失;
几年来他们已经完全失踪了。没有办法让微软能够让DHTML获得比它更好的优势：它对于他们的核心业务，即富有的客户来说太危险了。微软最近的一个重要模仿是：''微软正在把这家公司押在富客户身上。''
就像我讨厌说的那样，一大块开发人员早已转移到网络上并拒绝退回。大多数.NET开发人员都是ASP.NET开发人员，为微软的网络服务器开发......这对于微软来说是个好兆头，而且由于它的API功能，它带来的好处也是如此。新的API是HTML，应用程序开发市场中的新赢家将是能够让HTML唱歌的人。
< / Joel Spolsky>
唯一的句子在我不同意的文章中是：
JS> ASP.NET很棒;我一直在使用网页
JS>开发十年，它真的只是一个
JS>在那之前的所有事情发生。
在我看来，ASP.NET并不是未来的一代，而只是微软重写一些着名的Perl模块几年前
那个：
- 使用模板生成动态网页和
- 加密表单数据。
dotnetforfood
经典ASP规则!!!
阿门！
-dlbjr
清晰的施舍决议
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!!!
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
这篇关于ASP.NET的渗透 - 开发人员继续使用VB6& ASP的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
