The worst code i've ever seen....
-
The stuff that nightmares are made of! Thank Bill for smiting java with C# :D
-
It's slow... it chews memory like a beast.... it boosts productivity like a monkey eating a dog......... http://www.java.com/en/[^]... If you want your application to be slow and not very good, use Java.
Last symester in High school I learned Java. It was so annoying. For our final sumative we had to make a game (We're kids oaky) and due to time constraints I had to work on it at home. At home I have JRE 1.6, at school they have JRE 1.5. Java 1.5 wouldn't display my game properly, it was all screwed up. I like C# way, way better.
-
In both my Bachelor's and Master's programs, we were forced to use it...
"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus
For a post piling on Java (which is the best proof yet against my theory that no language is proof against sufficiently determined idiots; cf. "outsourcing"), to use a .sig line with a dead-accurate evaluation of VB just made my morning. (Yes, you can write idiotic code in other languages; you just have to work much harder at it.)
Jeff Dickey Seven Sigma Software and Services Phone/SMS: +65 8333 4403 Yahoo! IM: jeff_dickey MSN IM: jeff_dickey at hotmail.com ICQ IM: 8053918 Skype: jeff_dickey
-
...and all the java crowd say the same thing about .NET. Move on, nothing to see.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Exactly Chris. I for one applaud the work your team does, and creating a separate Java home is another excellent idea which will be appreciated by most of us. To those of you who hate (or are frightened of) Java, please don't waste space in this forum airing your prejudices.
-
It's slow... it chews memory like a beast.... it boosts productivity like a monkey eating a dog......... http://www.java.com/en/[^]... If you want your application to be slow and not very good, use Java.
But.. but... it's portable... so it has to be good
-
It's slow... it chews memory like a beast.... it boosts productivity like a monkey eating a dog......... http://www.java.com/en/[^]... If you want your application to be slow and not very good, use Java.
Huh, I don't know Java. But I don't think it's that bad. C# isn't too fast, too. But there are pretty much features in C# now I don't want to miss like (automatic) properties, WPF, LINQ, extension functions,...
-
Java has many adnvantages over .NET and disadvantages as well - one of the most problematic (in my opinion) being not supporting value types, everything is object. But, you state that it chews lot of memory and is slow; having seen your latest articles do you have the courage to say that WPF and especially your code runs faster and with less memory than Java Swing GUI for example? P.S. I write in .NET also.
Thanks, Georgi
I don't know Java, tell me, which advantages has it? Not supporting value types of course is annoying, but this isn't solved very well in C#, too. You can't clone objects by default, they all have to implement ICloneable, which is not even generic!
-
I don't know Java, tell me, which advantages has it? Not supporting value types of course is annoying, but this isn't solved very well in C#, too. You can't clone objects by default, they all have to implement ICloneable, which is not even generic!
Dude, I am not sure you are familiar with value and reference types at all; it has nothing to do with ICloneable... As a GUI developer I may speak of the following advantages of Java Swing over .NET 2.0: Java is completely detached from the underlying OS - .NET is using Interop primarily; 99% of the controls are wrappers of their Win32 equivalents; you need to know Win32 API in order to create commercial controls. Let me mention that things are different in WPF - there is actual bridge which separates OS from the GUI. But still, WPF consumes lot of memory and is not the platform a company, which cares about performance, would choose on... That is my personal opinion of course.
Thanks, Georgi
-
Dude, I am not sure you are familiar with value and reference types at all; it has nothing to do with ICloneable... As a GUI developer I may speak of the following advantages of Java Swing over .NET 2.0: Java is completely detached from the underlying OS - .NET is using Interop primarily; 99% of the controls are wrappers of their Win32 equivalents; you need to know Win32 API in order to create commercial controls. Let me mention that things are different in WPF - there is actual bridge which separates OS from the GUI. But still, WPF consumes lot of memory and is not the platform a company, which cares about performance, would choose on... That is my personal opinion of course.
Thanks, Georgi
I think is the main difference between value and reference types is, that if you write
x = yand y is a value type, x contains a copy of y, while when y is a reference type, x contains a reference to y. To copy y, y is required to ICloneable. Is that false? -
Huh, I don't know Java. But I don't think it's that bad. C# isn't too fast, too. But there are pretty much features in C# now I don't want to miss like (automatic) properties, WPF, LINQ, extension functions,...
elektrowolf wrote:
C# isn't too fast, too
Uh, ***trying not to sound rude***, how inefficiently do you code?
-
Dude, I am not sure you are familiar with value and reference types at all; it has nothing to do with ICloneable... As a GUI developer I may speak of the following advantages of Java Swing over .NET 2.0: Java is completely detached from the underlying OS - .NET is using Interop primarily; 99% of the controls are wrappers of their Win32 equivalents; you need to know Win32 API in order to create commercial controls. Let me mention that things are different in WPF - there is actual bridge which separates OS from the GUI. But still, WPF consumes lot of memory and is not the platform a company, which cares about performance, would choose on... That is my personal opinion of course.
Thanks, Georgi
Georgi Atanasov wrote:
That is my personal opinion of course.
And which is why you can get away being so wrong ;P On a little more serious note...
Georgi Atanasov wrote:
Java is completely detached from the underlying OS
So? If it works then why not?
Georgi Atanasov wrote:
99% of the controls are wrappers of their Win32 equivalents; you need to know Win32 API in order to create commercial controls
I'm not sure i'd agree; I've created a Office Fleunt Ribbon control library using nothing more than WPF, which i'm happily using in a commercial grade application, with no problems (http://www.codeproject.com/KB/WPF/ribboncontrol.aspx[^], see also CIRIP).
Georgi Atanasov wrote:
WPF consumes lot of memory
It's a new technology, and so not full optimised yet; hey if you want to moan about something *new* then why not have a go about the lack of an open and save dialog. I'm sure exactly the same was said of MFC, Swing, etc.
Georgi Atanasov wrote:
is not the platform a company, which cares about performance, would choose on...
There are companies using it, admitadly few currently but growing by the day. Yes, performance is shocking until you learn how to use it properly and then it's more than fast enough. Companies in my eyes don't care about performance, they care about cost to produce something that does the job, and from my experience WPF reduces development time (after over 4-5 years of Windows Forms (and Java Swing for that matter) and only <6 months WPF programming).
-
I think is the main difference between value and reference types is, that if you write
x = yand y is a value type, x contains a copy of y, while when y is a reference type, x contains a reference to y. To copy y, y is required to ICloneable. Is that false?perhaps a better example might be x = y y.a_property = some_value if (x.a_property == y.a_property) then referance type else value type
-
Chris Maunder wrote:
...and all the java crowd say the same thing about .NET. Move on, nothing to see
But of course, they are wrong and we are right. Why? Well, because we are, well.... us.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
Chris Maunder wrote: ...and all the java crowd say the same thing about .NET.
***to the tune of big ben*** Wrong wrong wrong wrong..... wrong wrong wrong wrong...... wrong.... wrong... wrong....
-
perhaps a better example might be x = y y.a_property = some_value if (x.a_property == y.a_property) then referance type else value type
OK, but basically it's the same. So what did I understand wrong? It does have something to do with ICloneable, or not?
-
elektrowolf wrote:
C# isn't too fast, too
Uh, ***trying not to sound rude***, how inefficiently do you code?
.. I mean compared to C++. I don't think it's too slow, I've never had problems with C#'s performance, but for some algorithms you need C++.
-
.. I mean compared to C++. I don't think it's too slow, I've never had problems with C#'s performance, but for some algorithms you need C++.
elektrowolf wrote:
but for some algorithms you need C++.
like what? Yes, i'd agree there is a slight performance decrease compaired to c++ but it's neglible.
-
OK, but basically it's the same. So what did I understand wrong? It does have something to do with ICloneable, or not?
referance and values types have very little to do with ICloneable... values types a guess are effectively implementors of ICloneable as x = y produces essentially a clone of x
-
referance and values types have very little to do with ICloneable... values types a guess are effectively implementors of ICloneable as x = y produces essentially a clone of x
It is obvious that you are not familiar (to be honest your guesses amused me pretty much :)) with Value and Reference types - you may try the following article (the first found one after search). http://www.codeproject.com/KB/dotnet/Primitive_Ref_ValueTypes.aspx[^] If I may advise you - you need read more about the basics of .NET such as Common Language Runtime (CLR), IL, value and reference types, etc. And do not be that arrogant:
Derek Bartram wrote:
Uh, ***trying not to sound rude***, how inefficiently do you code?
. Having in mind that you even dare to compare the performance of native C++ against .NET and after examining some code from your "Famous" Ribbon library I am not completely sure that you are an efficiency master...
Thanks, Georgi
modified on Sunday, April 13, 2008 4:52 PM
-
.net slower than java or java slower than .net.... I can justify java slower than .net with about 10 minutes of coding (and 30mins of java tools downloads). Please don't ask me too though, really don't want the hassel of downloading java stuff.
HI Can you show me some written proof(Link to the articles, journal's, books etc) that C# is better than Java or vice versa. You can not comment on anything unless there is any written evidence for it. I am waiting for the proof... :) ta
modified on Sunday, April 13, 2008 8:42 PM
-
Dude, I am not sure you are familiar with value and reference types at all; it has nothing to do with ICloneable... As a GUI developer I may speak of the following advantages of Java Swing over .NET 2.0: Java is completely detached from the underlying OS - .NET is using Interop primarily; 99% of the controls are wrappers of their Win32 equivalents; you need to know Win32 API in order to create commercial controls. Let me mention that things are different in WPF - there is actual bridge which separates OS from the GUI. But still, WPF consumes lot of memory and is not the platform a company, which cares about performance, would choose on... That is my personal opinion of course.
Thanks, Georgi
OK, basically, they have nothing to do with ICloneable. But if you want to create a copy of a reference type, this type needs to implement ICloneable, whilst in C++, reference types can be both referenced and copied by default and you can define a copy constructor to change the copying process. I think this is solved much better in C++.