Dumb VB and C++ fact of the Day
-
There's no Visual Basic 13.0 nor C++ 13.0. They went from VB 12.0 in VS 2013 to VB 14.0 in VS 2015, and Visual C++ 12.0 in VS 2013 to Visual C++ 14.0 in VS 2015. [Edited to add the C++ factoid. Yeah, this is my afternoon of productivity]
cheers Chris Maunder
Have you considered FORTRAN 19? I've heard that it's hard to find machines to punch Hollerith cards these days, but I'm sure that they can be located on Alibaba.com. If you can't find it, I think I still have a copy of Visual C++ 1.4 in my stockpile; I'll be happy to send it along, if I can find it, and you're feeling nostalgic. You'll find, as you travel, that few hotels have a 13th floor; I prefer to stay in those that do, simply because I'm a bit contrarian. Most of the good things that have happened in my life happened on Friday, the 13th, so I have no irrational fear of that arbitrary date.
Will Rogers never met me.
-
Because 13 is an unlucky number. Note, however, that even actively avoiding v13 doesn't rescue VB from being a pile of crap.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I'm curious to know why you feel that way about VB.NET, which can express virtually everything that C# can; and like other .NET languages can make use of (almost all of) the types in the .NET Framework. There are obviously various small differences (VB.NET allows inferring the delegate type, allows assigning a numeric string to a number, etc.) Generally, I have found only one reason to prefer C# over VB.NET -- VB.NET's syntax uses English words where C# would use symbols.
-
There's no Visual Basic 13.0 nor C++ 13.0. They went from VB 12.0 in VS 2013 to VB 14.0 in VS 2015, and Visual C++ 12.0 in VS 2013 to Visual C++ 14.0 in VS 2015. [Edited to add the C++ factoid. Yeah, this is my afternoon of productivity]
cheers Chris Maunder
Developers and simple arithmetic: never the twain shall meet.
I wanna be a eunuchs developer! Pass me a bread knife!
-
13 is the age when one should be moving from VB to a programming language. No later than puberty. :)
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
This thread is about VB.NET, which can express virtually everything that C# can express, albeit with a wordier syntax. Do you mean that C# is not a real programming language? Or do you mean that VB6 / VBA is not a real programming language (which I could get behind, if not entirely agree with)?
-
Have you considered FORTRAN 19? I've heard that it's hard to find machines to punch Hollerith cards these days, but I'm sure that they can be located on Alibaba.com. If you can't find it, I think I still have a copy of Visual C++ 1.4 in my stockpile; I'll be happy to send it along, if I can find it, and you're feeling nostalgic. You'll find, as you travel, that few hotels have a 13th floor; I prefer to stay in those that do, simply because I'm a bit contrarian. Most of the good things that have happened in my life happened on Friday, the 13th, so I have no irrational fear of that arbitrary date.
Will Rogers never met me.
Friday 13th has always been lucky for my family, my Granddad was rescued for the sea twice(!) on Friday 13th in World War One (he was plucked out of the sea once and then that ship was sunk! so, maybe not as lucky as he could have been but...).
-
13 is the age when one should be moving from VB to a programming language. No later than puberty. :)
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
Obligatory reference (youtube)[^]
I wanna be a eunuchs developer! Pass me a bread knife!
-
Please don't be so harsh with VB. I'm working in business automation industry and my day to day languages are C#, TypeScript, VB. Imho VB is the most effective for writing business login.
stepan hakobyan wrote:
Please don't be so harsh with VB.
VB sucks in all of its evil incarnations. That's as un-harsh as I can be.
stepan hakobyan wrote:
I'm working in business automation industry and my day to day languages are C#, TypeScript, VB.
I'd like to show some sympathy or your plight, but you've no doubt had plenty of opportunities to remedy that situation, but you persist in exposing yourself to VB, so I'm not sure how you think I should react.
stepan hakobyan wrote:
Imho VB is the most effective for writing business login.
That's just crazy talk right there.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I'm curious to know why you feel that way about VB.NET, which can express virtually everything that C# can; and like other .NET languages can make use of (almost all of) the types in the .NET Framework. There are obviously various small differences (VB.NET allows inferring the delegate type, allows assigning a numeric string to a number, etc.) Generally, I have found only one reason to prefer C# over VB.NET -- VB.NET's syntax uses English words where C# would use symbols.
ZevSpitz wrote:
I'm curious to know why you feel that way about VB.NET
Because the name starts with "VB".
ZevSpitz wrote:
which can express virtually everything that C# can; and like other .NET languages can make use of (almost all of) the types in the .NET Framework.
The words "virtually" and "almost" should be indicators for you...
ZevSpitz wrote:
There are obviously various small differences (VB.NET allows inferring the delegate type, allows assigning a numeric string to a number, etc.)
"Inferring" and being typeless do not make VB a better idea. Unless you're a commie... or liberal...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
There's no Visual Basic 13.0 nor C++ 13.0. They went from VB 12.0 in VS 2013 to VB 14.0 in VS 2015, and Visual C++ 12.0 in VS 2013 to Visual C++ 14.0 in VS 2015. [Edited to add the C++ factoid. Yeah, this is my afternoon of productivity]
cheers Chris Maunder
Yes they were. Both VB.Net 13.0 and C++ 13.0 were ready for release in VS 2014 code name Dev 13. However it only worked on Windows 9. Windows 9 release was killed by Windows 10 which was released midway through 2015. So VS 2014, VB.Net 13.0, C++ 13.0 and Windows 9 were effectively all fake news. There is a reason for everything.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
-
ZevSpitz wrote:
I'm curious to know why you feel that way about VB.NET
Because the name starts with "VB".
ZevSpitz wrote:
which can express virtually everything that C# can; and like other .NET languages can make use of (almost all of) the types in the .NET Framework.
The words "virtually" and "almost" should be indicators for you...
ZevSpitz wrote:
There are obviously various small differences (VB.NET allows inferring the delegate type, allows assigning a numeric string to a number, etc.)
"Inferring" and being typeless do not make VB a better idea. Unless you're a commie... or liberal...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Some facts: ;P 1. I am not a liberal or commie - in fact I think Atilla the Hun and Genghis Kahn were lily-livered pinko-liberal pooftahs. 2. I have written lots and lots of VB.NET - and got paid for it. :cool: 3, I have a 50 foot yacht in the marina. Sadly, the marine police have removed my small armoury therefrom until such time as I leave. Your move! :laugh: :laugh:
-
There's no Visual Basic 13.0 nor C++ 13.0. They went from VB 12.0 in VS 2013 to VB 14.0 in VS 2015, and Visual C++ 12.0 in VS 2013 to Visual C++ 14.0 in VS 2015. [Edited to add the C++ factoid. Yeah, this is my afternoon of productivity]
cheers Chris Maunder
That's the only dumb VB fact you have? :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Some facts: ;P 1. I am not a liberal or commie - in fact I think Atilla the Hun and Genghis Kahn were lily-livered pinko-liberal pooftahs. 2. I have written lots and lots of VB.NET - and got paid for it. :cool: 3, I have a 50 foot yacht in the marina. Sadly, the marine police have removed my small armoury therefrom until such time as I leave. Your move! :laugh: :laugh:
-
There's no Visual Basic 13.0 nor C++ 13.0. They went from VB 12.0 in VS 2013 to VB 14.0 in VS 2015, and Visual C++ 12.0 in VS 2013 to Visual C++ 14.0 in VS 2015. [Edited to add the C++ factoid. Yeah, this is my afternoon of productivity]
cheers Chris Maunder
-
Some facts: ;P 1. I am not a liberal or commie - in fact I think Atilla the Hun and Genghis Kahn were lily-livered pinko-liberal pooftahs. 2. I have written lots and lots of VB.NET - and got paid for it. :cool: 3, I have a 50 foot yacht in the marina. Sadly, the marine police have removed my small armoury therefrom until such time as I leave. Your move! :laugh: :laugh:
A fact you missed: 0) Real programmers know enumerated lists start with 0.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Another VB fact: I am retired on a tropical island in the Caribbean after 25 years of VB /VB.Net programming :) Who's next?
I'm not retired because I'm busy replacing VB-based crap-ware with C#.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I'm not retired because I'm busy replacing VB-based crap-ware with C#.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
I'm curious to know why you feel that way about VB.NET, which can express virtually everything that C# can; and like other .NET languages can make use of (almost all of) the types in the .NET Framework. There are obviously various small differences (VB.NET allows inferring the delegate type, allows assigning a numeric string to a number, etc.) Generally, I have found only one reason to prefer C# over VB.NET -- VB.NET's syntax uses English words where C# would use symbols.
ZevSpitz wrote:
I'm curious to know why you feel that way about VB.NET
ZevSpitz wrote:
VB.NET allows ... assigning a numeric string to a number
I think you've just answered your own question there! :-D (
Option StrictandOption Explicitshould always beOn. IMO, there shouldn't even be an option to turn them off.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
A fact you missed: 0) Real programmers know enumerated lists start with 0.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013And 3 facts you missed: 0. Real programmers don't care what language they use; because they are able to solve the problem in any language. 1. Smart programmers solve the problem in the way it is the least work and pays the most. 2. Really good programmers won't be used on projects where they have to fix the crap of someone else (that's where juniors are for).
-
ZevSpitz wrote:
I'm curious to know why you feel that way about VB.NET
ZevSpitz wrote:
VB.NET allows ... assigning a numeric string to a number
I think you've just answered your own question there! :-D (
Option StrictandOption Explicitshould always beOn. IMO, there shouldn't even be an option to turn them off.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
ZevSpitz wrote:
I'm curious to know why you feel that way about VB.NET
ZevSpitz wrote:
VB.NET allows ... assigning a numeric string to a number
I think you've just answered your own question there! :-D (
Option StrictandOption Explicitshould always beOn. IMO, there shouldn't even be an option to turn them off.)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
IMO, there shouldn't even be an option to turn them off.)
All of this is presuming that VB should be allowed to exist in the first place.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
