Visual Basic needs more credit
-
People that don't already write code are -cheaper per hour -easier to train -get the job done faster -get the job done without added flare -almost half the cost overall as other programmers -they write in full words (no bad habits)
also have no clue when something breaks... I have seen VB programmers programming like they are chucking bricks over a wall!
-
I own 3 companies.
Great. Hopefully the people you're hiring for your companies are on the same page with you. Personally, I disagree, and wouldn't hire someone who agreed with you on this particular subject because it likely means they think a lot of other things that I don't agree with. Have a nice day.
-
Great. Hopefully the people you're hiring for your companies are on the same page with you. Personally, I disagree, and wouldn't hire someone who agreed with you on this particular subject because it likely means they think a lot of other things that I don't agree with. Have a nice day.
I wrote Unidex, its competes with SQL, its about to be released as it was just finished. It allows for pictures, video and songs to be placed in a record - the actual data not the file name... It also can index 200 GB of memory, create 8 million records an hour, have records in the same table with different number of columns, records can have columns unique to its record. In fact Unidex does all the hard work that pretty much I need to stay away from anyone that thinks they know computers.
-
also have no clue when something breaks... I have seen VB programmers programming like they are chucking bricks over a wall!
Lmao indeed indeed Gladly I am using Unidex and not SQL so the guess work for my programmers is next to nothing.
-
If you're used to working in a case-sensitive language, the difference between
Heightandheightis pretty obvious. And if you're that worried about it, you can always call your variable something else!
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I have a habit of avoiding case sensitive languages as it creates more problems, then the advantage you gave
-
I wrote Unidex, its competes with SQL, its about to be released as it was just finished. It allows for pictures, video and songs to be placed in a record - the actual data not the file name... It also can index 200 GB of memory, create 8 million records an hour, have records in the same table with different number of columns, records can have columns unique to its record. In fact Unidex does all the hard work that pretty much I need to stay away from anyone that thinks they know computers.
And? I'll bet you'd be extremely disruptive at planning meetings. You can have it your way if you want. I just wouldn't have you in my company. And, you say it competes with SQL, meaning 'it attempts to go after the same market.' Which is well and good, but that doesn't mean anything, because I haven't heard of it, and probably most other people who use SQL haven't either. I wrote a database server, and query language for it too, and sold it commercially. That doesn't make me any more of an expert than someone who hasn't. Nor does it make you. It just means you know what an index is, the appropriate data structures for using it, etc. Congratulations. You're still wrong ;)
-
And? I'll bet you'd be extremely disruptive at planning meetings. You can have it your way if you want. I just wouldn't have you in my company. And, you say it competes with SQL, meaning 'it attempts to go after the same market.' Which is well and good, but that doesn't mean anything, because I haven't heard of it, and probably most other people who use SQL haven't either. I wrote a database server, and query language for it too, and sold it commercially. That doesn't make me any more of an expert than someone who hasn't. Nor does it make you. It just means you know what an index is, the appropriate data structures for using it, etc. Congratulations. You're still wrong ;)
Just remember that once you hear of us.
-
Just remember that once you hear of us.
I sincerely wish you all the best. I just think you're still wrong about VB.
-
PIEBALDconsult wrote:
Try writing an event that returns a value in VB
How do you do that in C# that you can't do in VB?
Wrong is evil and must be defeated. - Jeff Ello[^]
Consider these two C# statements:
public delegate bool IsItSafe() ;
public event IsItSafe Probe ;they compile just fine and actually work as they should, but the VB.net equivalent:
Delegate Function IsItSafe() as Boolean
Event Probe As IsItSafeyields:
C:\Projects\Template.vb(26) : error BC31084: Events cannot be declared with a delegate type that has a return type.
Event Probe As IsItSafe ~~~~~Not that it's something that is common, but I do use a few events that return bool values in an unusual project of mine.
You'll never get very far if all you do is follow instructions.
-
I would not hire you sorry. The reason you can not use the with operator in such a fashion is scope
And this, in turn, is why I wouldn't hire you: you don't look past what is and see what could be. See, a simple rule that ambiguous member references within a With statement are not allowed (and are a compiler error) would sort out the scoping issues, produce something that has significantly more expressive power, and not make the language any more complicated. The fact that this is not part of the language is irrelevant: there are open-source visual basic compilers (eg, as part of the Mono project) that would be easily extended to support whatever extensions you like. This is not, of course, to say that I would advocate for such a feature to be added. It wouldn't result in any increase in code readability (rather, it would significantly decrease readability), and any given piece of code is likely going to be read far more times than it will be written.
-
I sincerely wish you all the best. I just think you're still wrong about VB.
What that it needs more credit? There are practically no differences between the two, and opinions for and against it being a better language then others suggest that I am right.
-
As I have learned but there is no period before either height so now the reader of the code has to guess at the scope of the object Real genius
It's pretty obvious from context that one of those is a property name on the object you're setting, and one is a name in the local scope, and that's all the . tells you. It's no different from public Form Form (or Dim Form As Form or whatever you write in VB) and other places where you have the same word in two different contexts.
-
And this, in turn, is why I wouldn't hire you: you don't look past what is and see what could be. See, a simple rule that ambiguous member references within a With statement are not allowed (and are a compiler error) would sort out the scoping issues, produce something that has significantly more expressive power, and not make the language any more complicated. The fact that this is not part of the language is irrelevant: there are open-source visual basic compilers (eg, as part of the Mono project) that would be easily extended to support whatever extensions you like. This is not, of course, to say that I would advocate for such a feature to be added. It wouldn't result in any increase in code readability (rather, it would significantly decrease readability), and any given piece of code is likely going to be read far more times than it will be written.
I own 3 companies - do you own any? In order to get C# lines to fit into the viewable area of the screen it is common practice to use a short variable notation, in visual basic it is common to use full words like PictureNameTextBlock - so when variables are that long the lines of code stretch far out off the screen - making the with block extremely important, once we compare the differences at a management stand point we saw reading visual basic was like reading English while reading C# code in general was impossible and had to rely on comments. Visual basic saves a lot of money.
-
It's pretty obvious from context that one of those is a property name on the object you're setting, and one is a name in the local scope, and that's all the . tells you. It's no different from public Form Form (or Dim Form As Form or whatever you write in VB) and other places where you have the same word in two different contexts.
When dealing with multiple languages from multiple teams anything that makes you think twice about it has to go.
-
I have a habit of avoiding case sensitive languages as it creates more problems, then the advantage you gave
The way you are making this statement is theological, not theoretical. In this audience, if you want that statement to actually stand, you'll have to go into great detail as to WHY you think that. I've been working in case sensitive languages for 30 years, without any problems I can think of regarding the language itself. Humans can mess up any language, regardless of syntactic richness, protections, etc. That is because the language only enforces syntactic correctness.. and most issues with code lie in either algorithm design or overall architectural design, which no language can protect you from no matter how rich.
-
The way you are making this statement is theological, not theoretical. In this audience, if you want that statement to actually stand, you'll have to go into great detail as to WHY you think that. I've been working in case sensitive languages for 30 years, without any problems I can think of regarding the language itself. Humans can mess up any language, regardless of syntactic richness, protections, etc. That is because the language only enforces syntactic correctness.. and most issues with code lie in either algorithm design or overall architectural design, which no language can protect you from no matter how rich.
If you studied languages you would know that opinions are not religion but thanks. Here is am example a large amount of new programmers make int64 Height = 150; int64 width = 150; When the programmer uses Height and Width, the Width has a underline, and because of the number of lines in the file the programmer creates a new variable int64 Width = 150; While this one programmer is using the uppercase Width his peers are using the lowercase width. Is that clear enough for you, Sorry I assumed you had enough experience to know the issues with dealing with case sensitive variables.
-
I came from Cobol and JCL, with 25 years of experience. I own a start up software company. Anyone that has C experience or web experience I find are bad employees, they make great leaders, not great employees, unless your business in devoted to C and C type languages, then you probably have 20 programmers to my one.
Correlation is not causation. Maybe the reason the C programmers are necessary is the nature of the problem that cause C to be picked as the implementation language in the first place. I've spent most of the last 30 years programming very near the hardware level. VB would have been a huge inconvenience for the types of problems I was solving. This doesn't make C/C++ inherently better or worse then VB.. only suited to a different problem domain. As to good vs. bad employees.. there are lots of ways to get those.. I've seen my share of good VB programmers and bad C programmers.. and VICE VERSA. Again.. correlation does not equal causation.
-
Considering the missing connection between me knowing C# can get away without using the with word, proves its problems. The with keyword gets the coder in a mindset.
Nonsense. Mindsets in programming are about how we handle abstractions. Expression syntax is just that.. expression syntax. I find I use the same mindset for programming no matter what language I use.. and I've used a lot over the years. Basic, C, C++, Algol, Perl, Forth, 8086 assembler, 6502 assembler (yes.. I'm that old). I find this statement highly unconvincing.
-
Advertising your other post is spam
-
No better way to learn. I was told that C# and visual basic are the same language but I can find things in Visual Basic that are not in C# and things in C# that are not in Visual Basic
They use the same underlying IL machine. I don't think its said anywhere that they are exactly the same.. If you read the book on the IL assembler the author talks in great detail on the differences between VB and C# and how the IL abstractions express them both. That qualifies this argument as a strawman.
