I don't care what MS does in their libraries, but my code will be explicit. I even use nice long variable names with underscores between words in the name!
you are right... I was thinking implicit typing versus explicit typing.
I still do not use it and since nothing forces you to use it, you have to go out of your way. I feel it was put there to make VB developers feel more comfortable.
you have to go WAY out of your way to use var and extension methods. It is still much more natural to statically type your variables and define all your methods in the class definition (well... extension methods could be a bit of an issue since it is easy, but I hate dealing with them so I don't care)
sorry tin man. MS has no control over it. They have ruled out being able to sue it since they declared that mono can use MS patents dealing with.net and the CLI in perpetuity.
Idiots have been claiming that MS will drop the ax on Mono any day and it has never and will never happen.
MS has a legaly binding statement that says mono and anyone who implements it is not liable under any MS patents. Your argument is an ignorant non-starter.
missing 2% that is irrelevant to 98% of development is not something to really care about when talking about it being an alternative.
FOSS-Nuts would extol the virtues of Kaffe before Java was opened up and no one said a peep about how utterly horrible it was and how much it was missing. Mono is nearly identical to.Net and for the UI, GTK# easily offers a cross platform toolkit.
Going GTK# means you get designer support in monodevelop. It is a very good tool.
Mono is a soon to be feature complete c# framework that is nearly identical to.net. a little redevelopment of UI code is worth it to many people if they are trying to sell to move to a cross platform market, including mobile devices.
who cares about WPF? GTK# is available to code in and provides complete cross platform abilities. WCF would be nice but is not required.
For someone starting a project, it is easy to build using Mono. For someone wanting to be cross platform using c#, mono is easy to use and it is very easy to avoid using WCF and WPF. WCF will be fully supported with in the next year.
best thing about the kindle version is the author (or copyright holder, depending on how bad the author's deal is it could be the same thing) gets 70% of the money if they price it according to Amazon's price point, 30% if they decide to set their own price.
My price point was hit for the device when it hit $189. I wanted it because of the convenience to carry books and it is easier for my to hold (low tonality in my hands makes it stressful to hold a book open)
Slashdot Mirror
I like to make it easy to read my code.
I don't care what MS does in their libraries, but my code will be explicit. I even use nice long variable names with underscores between words in the name!
I was more interested in the content than the actual pictures... since the conclusion was basically
"these numbers mean squat since the performance variance depends greatly on the underlying environment"
Reading must be a dying art.
you are right... I was thinking implicit typing versus explicit typing.
I still do not use it and since nothing forces you to use it, you have to go out of your way. I feel it was put there to make VB developers feel more comfortable.
No... I mean Tin Man... he is so paranoid he has wrapped his entire body in tin.
Well... that would be like saying the KDE framework isn't good for GUIs since it doesn't support win32 or winforms UIs.
or... you know... not
http://dotneverland.blogspot.com/2008/07/yet-another-benchmark-of-clr-vs-jvm.html
verbose? you must write C code.
you have to go WAY out of your way to use var and extension methods. It is still much more natural to statically type your variables and define all your methods in the class definition (well... extension methods could be a bit of an issue since it is easy, but I hate dealing with them so I don't care)
http://monodevelop.com/Download
seems to show an OS X build.
You are a fuckign Liar.
Google "Microsoft Promises Not to Sue Mono"
They have said they own the patents and they have publicly affirmed they will never sue mono or people who develop using mono. case closed... next!
How is using a current version of mono + GTK# different than me using .net 3.0 + GTK#?
sorry tin man. MS has no control over it. They have ruled out being able to sue it since they declared that mono can use MS patents dealing with .net and the CLI in perpetuity.
Idiots have been claiming that MS will drop the ax on Mono any day and it has never and will never happen.
why isn't it good for GUI apps? GTK# is a good cross platform toolkit and has a good designer in mono develop.
MS has a legaly binding statement that says mono and anyone who implements it is not liable under any MS patents. Your argument is an ignorant non-starter.
excuse me, but developing a C# application against the mono framework is completely portable.
missing 2% that is irrelevant to 98% of development is not something to really care about when talking about it being an alternative.
FOSS-Nuts would extol the virtues of Kaffe before Java was opened up and no one said a peep about how utterly horrible it was and how much it was missing. Mono is nearly identical to .Net and for the UI, GTK# easily offers a cross platform toolkit.
Going GTK# means you get designer support in monodevelop. It is a very good tool.
Mono is a soon to be feature complete c# framework that is nearly identical to .net. a little redevelopment of UI code is worth it to many people if they are trying to sell to move to a cross platform market, including mobile devices.
who cares about WPF? GTK# is available to code in and provides complete cross platform abilities. WCF would be nice but is not required.
For someone starting a project, it is easy to build using Mono. For someone wanting to be cross platform using c#, mono is easy to use and it is very easy to avoid using WCF and WPF. WCF will be fully supported with in the next year.
best thing about the kindle version is the author (or copyright holder, depending on how bad the author's deal is it could be the same thing) gets 70% of the money if they price it according to Amazon's price point, 30% if they decide to set their own price.
My price point was hit for the device when it hit $189. I wanted it because of the convenience to carry books and it is easier for my to hold (low tonality in my hands makes it stressful to hold a book open)
try looking at the freaking link moron. Very little is missed in Mono.
MS is litigious?
Saying doesn't make it so.
you can interpret it both ways. You are simply providing the benefit of the doubt.
Java was the next Cobol about 5 years ago.
Mono is pretty much caught up. will all features of .net
There are a few exceptions, but nothing that can't be worked around quickly.