Timeline for VB.Net vs C# debate
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2013 at 20:05 | comment | added | JohnFx | That's circular reasoning. Although I felt the same way early in my career, I am increasingly understanding that consistency as a measure of code quality is just us OCDing on the details that don't truly matter. I get where you are coming from and would have argued your point exactly 15 years ago. I've just come to understand that it adds more effort than value to the final product. | |
| May 22, 2013 at 15:22 | comment | added | Falcon | @JohnFx: Sure, it would matter a lot! Homogeinity is a trait of good code. Now when people are free to write: "Width, width, WIDTH,wIdTh" for example, homoegeneity will decrease and thus code quality WILL decrease. | |
| May 18, 2013 at 0:11 | comment | added | JohnFx | It is only sloppy code because the compiler can't interpret it. If all compilers were case insensitive it wouldn't matter a lick. Our job is not to write code for print in a magazine, it is to write code that does a job. "Sloppy" case doesn't inhibit that one bit. | |
| May 17, 2013 at 16:30 | comment | added | Falcon | It should be hard to write sloppy code in any programming language. Case insensitivity just encourages sloppy code. Case sensitivity does not slow you down at all, what kind of an argument is this? It slows you down when you make a lot of typos and then it's a good thing you are being slowed. | |
| Oct 18, 2011 at 12:31 | comment | added | JohnFx | Needing a coding standard to avoid insidious bugs like that, to me, is a negative. The presence of a workaround doesn't excuse it. | |
| Oct 18, 2011 at 11:52 | comment | added | Aidiakapi | 'I have never been in a situation where I wanted two identifiers in the same scope to differ only by case.' is pure subjective. This is exactly one of the reasons why I prefer C#. When applied correctly and consequent, it might make all sense to the world to have for example a parameter in the constructor with the name name and a public property with the name Name and then assign it through Name = name;. As long as you keep a coding standard, else I agree, then it can cause confusion. | |
| Jan 14, 2011 at 16:28 | history | edited | JohnFx | CC BY-SA 2.5 | added 393 characters in body |
| Jan 14, 2011 at 16:13 | history | edited | JohnFx | CC BY-SA 2.5 | deleted 12 characters in body |
| Sep 8, 2010 at 23:09 | history | edited | JohnFx | CC BY-SA 2.5 | added 249 characters in body |
| Sep 8, 2010 at 22:54 | comment | added | Paperjam | +1 for the web development comment. I use both VB.NET and C#, depending on the project, and find it much easier to go back and forth between C# and Javascript than VB.NET and JS. | |
| Sep 8, 2010 at 22:50 | history | answered | JohnFx | CC BY-SA 2.5 |