Disadvantages of C#??? just curious

[chandu]

Hello every body ,
upto now i saw advantages of C# only,i am curious about what are the
disadvantages of C#..(because any programming language should have some
positives and negatives..)

Thanks

Chandu

[Jon Skeet [C# MVP]]

Brian Gideon <br*********@ya hoo.comwrote:

<snip>

I don't know whether it'll be part of the BCL - without further
examination, I don't know whether I'd *want* it to be part of the BCL.
Being tucked away as part of robotics studio, however, I can't see it
getting as much use and examination as it possibly deserves though.

If I remember correctly the Microsoft Robotics Studio was like a 50 MB
download or something. That's an awful lot of baggage considering I'm
only interested in the CCR. And you're right. It's an esoteric
placement since its usefulness goes far beyond robotics.

Maybe it's time for a blog entry. You never know how stirring things up
might just persuade MS to release it separately...

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

Jon Skeet [C# MVP] wrote:

Göran Andersson <gu***@guffa.co mwrote:

>>Mono has problems keeping up with the framework - but it tends to
manage to get the *language* features released earlier than Microsoft
does, IIRC.

Doesn't Mono release every minor version to the public? That would mean
that the release rate of Mono can be much more frequent eventhough the
development rate of MS .NET is higher.

I didn't mention release *rate* - just release *availability*.

Which depends on the rate. :)

>>Frankly, I think MS is going to have to slow down the framework
development soon anyway - they've done an awful lot in 6 years, and I
think we could do with a bit of a break after LINQ has been released,
so everyone can catch up. Just MHO, of course. (Having said that, I
can't wait for CCR...)

Perhaps it will slow down somewhat, but I don't think that it will be by
much. I believe that one major reason that Microsoft has been able to
keep their .NET platform so dominant is that Mono has problems to keep up.

I don't see Mono as being much competition to Microsoft, to be honest.
I hope it'll prove really useful for development on Linux, but I can't
see it moving Windows shops onto Linux in a significant way.

--
Göran Andersson
_____
http://www.guffa.com

[Ravichandran J.V.]

Knowing about disadvantages first without knowing the field of
applicability is just a waste of time. Why not simply ask whether you
can do this with C#...

with regards,
J.V.Ravichandra n
- http://www.geocities.com/
jvravichandran
- Or, just search on "J.V.Ravichandr an"
at http://www.Google.com

*** Sent via Developersdex http://www.developersdex.com ***

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Jon Skeet [C# MVP] wrote:

Arne Vajhøj <ar**@vajhoej.d kwrote:

>per9000 wrote:

>>INDEED, the MONO-project http://www.mono-project.com/ is an excellent
example of C# (et. al.) being used in under GNU FDL. I fear/suspect
that C# + MONO will outlive C# + Windows and that the two might
diverge soon.

I do not see any indication of Mono taking over anything.

Indeed I see Mono having problems following the fast
release speed of Microsoft.

Mono has problems keeping up with the framework - but it tends to
manage to get the *language* features released earlier than Microsoft
does, IIRC.

It is much easier to write a compiler than to write tens of thousands
of library classes.

Frankly, I think MS is going to have to slow down the framework
development soon anyway - they've done an awful lot in 6 years, and I
think we could do with a bit of a break after LINQ has been released,
so everyone can catch up. Just MHO, of course. (Having said that, I
can't wait for CCR...)

MS has the money to keep on going, but as you say the customers
are having problems following.

Arne

[Jon Skeet [C# MVP]]

Arne Vajhøj <ar**@vajhoej.d kwrote:

Indeed I see Mono having problems following the fast
release speed of Microsoft.

Mono has problems keeping up with the framework - but it tends to
manage to get the *language* features released earlier than Microsoft
does, IIRC.

It is much easier to write a compiler than to write tens of thousands
of library classes.

Absolutely.

Frankly, I think MS is going to have to slow down the framework
development soon anyway - they've done an awful lot in 6 years, and I
think we could do with a bit of a break after LINQ has been released,
so everyone can catch up. Just MHO, of course. (Having said that, I
can't wait for CCR...)

MS has the money to keep on going, but as you say the customers
are having problems following.

Yes - I hope that MS will spend its time improving VS and possibly
creating new (isolated, separately downloadable) libraries to improve
development rather than extending the core framework itself - at least
for a while.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[JR]

I would suggest more refactorings.

JR
"Jon Skeet [C# MVP]" <sk***@pobox.co m???
??????:MP****** *************** ***@msnews.micr osoft.com...
Arne Vajhøj <ar**@vajhoej.d kwrote:

Indeed I see Mono having problems following the fast
release speed of Microsoft.

Mono has problems keeping up with the framework - but it tends to
manage to get the *language* features released earlier than Microsoft
does, IIRC.

It is much easier to write a compiler than to write tens of thousands
of library classes.

Absolutely.

Frankly, I think MS is going to have to slow down the framework
development soon anyway - they've done an awful lot in 6 years, and I
think we could do with a bit of a break after LINQ has been released,
so everyone can catch up. Just MHO, of course. (Having said that, I
can't wait for CCR...)

MS has the money to keep on going, but as you say the customers
are having problems following.

Yes - I hope that MS will spend its time improving VS and possibly
creating new (isolated, separately downloadable) libraries to improve
development rather than extending the core framework itself - at least
for a while.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

Jon,
That CCR.Core assembly weighs in at just 154Kb. Thanks for reminding me to
go back and revisit that. Some very elegant and useful code there.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Jon Skeet [C# MVP]" wrote:

Arne Vajhøj <ar**@vajhoej.d kwrote:

>Indeed I see Mono having problems following the fast
>release speed of Microsoft.
>
Mono has problems keeping up with the framework - but it tends to
manage to get the *language* features released earlier than Microsoft
does, IIRC.

It is much easier to write a compiler than to write tens of thousands
of library classes.

Absolutely.

Frankly, I think MS is going to have to slow down the framework
development soon anyway - they've done an awful lot in 6 years, and I
think we could do with a bit of a break after LINQ has been released,
so everyone can catch up. Just MHO, of course. (Having said that, I
can't wait for CCR...)

MS has the money to keep on going, but as you say the customers
are having problems following.

Yes - I hope that MS will spend its time improving VS and possibly
creating new (isolated, separately downloadable) libraries to improve
development rather than extending the core framework itself - at least
for a while.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Peter Bromberg [C# MVP] <pb*******@yaho o.yabbadabbadoo .comwrote:

That CCR.Core assembly weighs in at just 154Kb. Thanks for reminding me to
go back and revisit that. Some very elegant and useful code there.

Mmm... maybe I'll download it after all. I'm just amazed that it hasn't
been released on its own :(

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

Even Jeffrey Richter's article demo code does not contain the CCR.Core
assembly. Could have something to do with the EULA. Too bad!
Peter
--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"Jon Skeet [C# MVP]" wrote:

Peter Bromberg [C# MVP] <pb*******@yaho o.yabbadabbadoo .comwrote:

That CCR.Core assembly weighs in at just 154Kb. Thanks for reminding me to
go back and revisit that. Some very elegant and useful code there.

Mmm... maybe I'll download it after all. I'm just amazed that it hasn't
been released on its own :(

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

Peter Bromberg [C# MVP] <pb*******@yaho o.yabbadabbadoo .comwrote:

Even Jeffrey Richter's article demo code does not contain the CCR.Core
assembly. Could have something to do with the EULA. Too bad!

I was about to suggest you blogged about it to make another attempt to
prod MS into releasing it on its own. Then I went to your blog. Um,
okay, I'll go back to XLinq...

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too