Hi Vickie, great question.



MISS.



I predict that JScript.NET is going to be in minimal use by only 5% of the 

ASP.NET community, and probably only for smaller tasks.  Now that we have 

C#, it's pretty much obsolete.  I was wondering while 

reading "Professional ASP.NET" why MS included JScript.NET at all.  



I attrbiute this to the downfall of the original JScript with Classic 

ASP.  Tech books and the media promoted VBScript too heavily, which 

filtered down through the communities, NNTP, and dev circles, which 

perhaps unfairly inundated JScript.  I'm glad to see that at least at this 

stage, people are giving C# a chance...and pushing it hard.  That implies 

progress.



I also believe that VBScript, being easier to learn, brought many 

traditional Web designers (the "FrontPage/Dreamweaver" crowd) into server-

side scripting.  If you're like me and don't come from a classical 

computer science background (I'm a marketing guy who learned to write code 

later), JScript was very intimidating.  VBScript made it somwehat easy to 

get into powerful scripting by comparison and dominated the playing 

field.  



Everyone is talking about VB.NET and C#, and they're all the rage.  Poor. 

poor JScript.NET...it's suffering an apathetic death.  People don't even 

know it's around.



Another query would be how the community feels about the longevity of J#.



Jason



---------------------------------------------------

 Jason Salas

 Web Development Manager

 KUAM-TV in Guam

 Mailto: jason@k...







> Hi guys,

> 

> I have another issues for you discuss and tell us about.

> 

> We've noticed that there doesn't seem to by much hype or buzz over the 

new 

> JScript .NET langauge at the moment. Do you think this will appear 

> gradually as more developers look towards .NET programming, or will the 

> other .NET langauges drown out their sibling? I'm interested in any 

views 

> you have on this, particularly if you currently use JScript within your 

> ASP pages and are thinking about transitioning to ASP.NET. Will you give 

> JScript .NET a go, or will you look towards C# or VB .NET?

> 

> Cheers,

> Vickie

> ASPToday editorial.

Good point about J#.



At first I was quite excited about J#, but I think that most people will 

go for C# or VB.NET.







> Hi Vickie, great question.

> 

> MISS.

> 

> I predict that JScript.NET is going to be in minimal use by only 5% of 

the 

> ASP.NET community, and probably only for smaller tasks.  Now that we 

have 

> C#, it's pretty much obsolete.  I was wondering while 

> reading "Professional ASP.NET" why MS included JScript.NET at all.  

> 

> I attrbiute this to the downfall of the original JScript with Classic 

> ASP.  Tech books and the media promoted VBScript too heavily, which 

> filtered down through the communities, NNTP, and dev circles, which 

> perhaps unfairly inundated JScript.  I'm glad to see that at least at 

this 

> stage, people are giving C# a chance...and pushing it hard.  That 

implies 

> progress.

> 

> I also believe that VBScript, being easier to learn, brought many 

> traditional Web designers (the "FrontPage/Dreamweaver" crowd) into 

server-

> side scripting.  If you're like me and don't come from a classical 

> computer science background (I'm a marketing guy who learned to write 

code 

> later), JScript was very intimidating.  VBScript made it somwehat easy 

to 

> get into powerful scripting by comparison and dominated the playing 

> field.  

> 

> Everyone is talking about VB.NET and C#, and they're all the rage.  

Poor. 

> poor JScript.NET...it's suffering an apathetic death.  People don't even 

> know it's around.

> 

> Another query would be how the community feels about the longevity of J#.

> 

> Jason

> 

> ---------------------------------------------------

>  Jason Salas

>  Web Development Manager

>  KUAM-TV in Guam

>  Mailto: jason@k...

> 

> 

> 

> > Hi guys,

> > 

> > I have another issues for you discuss and tell us about.

> > 

> > We've noticed that there doesn't seem to by much hype or buzz over the 

> new 

> > JScript .NET langauge at the moment. Do you think this will appear 

> > gradually as more developers look towards .NET programming, or will 

the 

> > other .NET langauges drown out their sibling? I'm interested in any 

> views 

> > you have on this, particularly if you currently use JScript within 

your 

> > ASP pages and are thinking about transitioning to ASP.NET. Will you 

give 

> > JScript .NET a go, or will you look towards C# or VB .NET?

> > 

> > Cheers,

> > Vickie

> > ASPToday editorial.