21–30 of 51 posts
You said `&&` is a stupid symbol and `and` is a better one, right? Sorry I think you're wrong because it's a symbol that used in almost all programming languages include c, c++, JavaScript and...
Earlier quoted context omitted.
And `PHP` has it, also! But I didn't see any big application/repository that uses `and` instead of `&&`, honestly.
Since I prefer the Pascal family of languages I do actually like "and", but I will use whatever is the default in a given language. This VB piece seems like a bit of VB programmer crap I usually hear from VB users that only dabble in programming without any proper developer education.
Sigh. I'll actually do the job of debunking these one by one. 1. Almost every mainstream language has case-sensitivity. This avoids ambiguity by having only one right way to express a given variable. Since Visual Studio has excellent autocomplete, you don't have to repeatedly use SHIFT, and you are unlikely to accidentally mistype the variable name. Of course, when I see an argument like, "When you accidentally leave…
It's at the top of the freaking article.
In my honest opinion, whilst VB is obviously fully supported, C# just "feels" more professional... When you get your head around the syntax, you can seamlessly move between C#/Javascript and many other languages that all follow similar syntax without even thinking.
In addition, there are so many more articles/examples/open source projects and just help out there for it.
Sigh. I'll actually do the job of debunking these one by one. 1. Almost every mainstream language has case-sensitivity. This avoids ambiguity by having only one right way to express a given variable. Since Visual Studio has excellent autocomplete, you don't have to repeatedly use SHIFT, and you are unlikely to accidentally mistype the variable name. Of course, when I see an argument like, "When you accidentally leave…
>Andy ‘Wise Owl’ Brown decided to write a tongue-in-cheek rant whilst he could still remember the pain-points It's at the top of the freaking article.
Or if the project manager is requiring all code to be formatting a certain way then I can re-format the code before I submit it. Plus with a language you can so quickly and painlessly re-format, why even require code style standards that dictate whitespace?
While some of this MIGHT be possible with VB.net, it is a lot trickier since whitespace is "content" in that language.
Sigh. I'll actually do the job of debunking these one by one. 1. Almost every mainstream language has case-sensitivity. This avoids ambiguity by having only one right way to express a given variable. Since Visual Studio has excellent autocomplete, you don't have to repeatedly use SHIFT, and you are unlikely to accidentally mistype the variable name. Of course, when I see an argument like, "When you accidentally leave…
It does. I'm pretty sure VB's "And" and "Or" don't short-circuit…
> 8. The author complains that the type for a variable declaration precedes the variable name in C#. Somehow this is a major problem. Obviously just scraping the bottom of the barrel here.
The author also complains that out-parameters have to be annotated as out-parameters in C#, apparently does not realize parameters don't have to be out-parameters.
> But he retorts that, "The point is that - as so often - Visual Basic makes something easier to code than C# does."
Basically, he complains that C# makes it harder to do the wrong thing than Visual Basic. Which tells you a lot about the mindset.
Sigh. I'll actually do the job of debunking these one by one. 1. Almost every mainstream language has case-sensitivity. This avoids ambiguity by having only one right way to express a given variable. Since Visual Studio has excellent autocomplete, you don't have to repeatedly use SHIFT, and you are unlikely to accidentally mistype the variable name. Of course, when I see an argument like, "When you accidentally leave…
Let's just bury that whole idea of 'programming for non-programmers' along with ugly shit that arose from it (cobol, vb, etc).