|
glennPattonWork wrote: I came to Windows from the embedded side, really reading data coming in via various ports and showing in Windows. VB6 was the quickest way as the company was run by a Micro-Sharft consultant.
Before .NET, there was only two choices for embedded software; eVC or eVB.
Gotta love your Mono 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Only for big embedded products that didn't use a Micro-controller. C still rules the small world!
|
|
|
|
|
However C++ is arriving (and Lua, and MicroPython).
|
|
|
|
|
Just don't see the point, C++ I would not trust to bloat... also class, pah! struct...
|
|
|
|
|
I do see the point. There is no bloat, unless you explicitely put it in.
C++ is multi paradigm: you may also use it effectively just as 'better C'.
As matter of fact I welcome the introduction of C++ in PIC32 microcontrollers code development.
|
|
|
|
|
Sure, a C++ compiler can compile your source code using only the plain C subset of C++.
The question is: Are you then develping in C, or in C++?
|
|
|
|
|
That wouldn't make much sense.
C++ has a lot of interesting features (templates for instance), even without considering OOP.
|
|
|
|
|
Our principal application is almost 2 million lines of VB.Net. As a c# developer I was hesitant but it really is just about getting your head around a more verbose syntax and several months to break the semi-colon and curly braces habit! Wherever possible, I still prefer c# as it feels more grown up. The biggest issue is finding engineers willing to work with VB.Net - the second you mention VB the phone goes dead...
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
Nice flame war!  A nice reminder of the VB shaming that exists here. 
As a solo developer the choice between C# and VB is dependent on one thing only: Which one am I the most productive in? it all boils down to the same MSIL anyway and my clients don't care.
Now, back to the VB shaming. (since it's Saturday) It seems that haters will hate. The same old weak arguments regurgitated to prove why their beloved C# is superior and VB is trash and not worthy for serious work...or that programmers who prefer (or are stuck with) VB are inferior and should be scorned and ridiculed.
I think as a community, we can do better than to get all evangelical about something so petty. I don't have a dog in this fight...I like them both equally...just a tool to get a job done.
"Go forth into the source" - Neal Morse
|
|
|
|
|
Crowing may be decoration with deodorant (11)
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
rodomontade? (crowing)
Anagram of "deodorant" + "mo" (though I am not sure how decoration becomes mo/om)
|
|
|
|
|
Well done - OM is what you needed it's the order of merit award - you are up Monday
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
I best set an alarm then!
Was a good clue, took me a while and very nearly gave up on it.
|
|
|
|
|
Thanks, as a matter of interest, do you use anagram solvers et al when doing these ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
pkfox wrote: do you use anagram solvers
Not for solving, though sometimes when trying to come up with clues. I am pretty good with anagrams so that's not normally an issue for me.
However, if I am struggling with a clue and can't solve it on my own, I do use a thesaurus to try and make progress. Which was the case with your clue today.
I find the hardest part (for me) in solving clues in trying to identify if a word should be taken "as is", or if it's meant to be a synonym.
|
|
|
|
|
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
modified 8-Nov-18 14:23pm.
|
|
|
|
|
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, 2013
|
|
|
|
|
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
|
|
|
|
|
As a general rule, people showing the kind of hashness as you do, toward one tool (or standard, or whatever) tend to have a poor understanding of how to use it. Or they consider it out of its intended scope of usage.
A number of years ago, I switched jobs, from a Solaris environment to a non-*nix-environment: I really never made friends with Solaris. Nor with the company standard editor emacs. I made both crash quite regularly. More than once, I demonstrated to my colleauges what I had been doing. They looked over my shoulder, and screamed out: Hey, you mustn't do THAT! What the h** did you do that for? Well, I did it to show you how I made Solaris crash (or emacs)... This happened several times, and every time they made me the cruel sinner who didn't know to behave, and ruined their concept of Solaris as the worlds most rock solid OS. Well, it was - as long as you didn't do anything that could make it crash...
In my new job, they were running a different OS (this was before Windows became the only alternative; it was in mincomputer/supermini area), which crashed several times a day. The Unix educated sysops did everything to make Sintran III appear as if it were Unix. I happened to know Sintran III well, so, as a left hand job, I became sort of sysops supervisor, telling them the proper way to maintain a Sintran III machine. I spent a week or two cleaning up the procedures. Three months later, some people were still complaining about the frequent crashes, and I had to drag them over to show them the system logs: The system hadn't had a single stop for three months.
Systems, languages, methods ... may be severely misused, abused, used in inappropriate ways or for inappropriate purposes. That doesn't mean the poor abused thing is evil, despisable or even bad. What you could say is that "X is not suitable for application Y, because it lacks a suitable way of doing A, B and C" (maybe it does have a provision, but for reasons 1, 2 and 3, that provision does not fulfill our requirements).
Any system, language or method that is widely used, is well suited for a certain class of tasks. Otherwise it wouldn't have been widely used. There may be other tools that would also be satisfactory. If you went into those environments using the tool you hate, presenting your arguments, you might learn that you hate reasons are not valid there.
E.g. lots of software people argue for open source, but lots of tool users would never ever consider looking at the source code of the tool. Or cost: You may save a thousand dollars on not paying for Visual Studio but sticking to emacs: How many man days saved does it take to pay for the software? Will the software save that many man days? (For VS, it has paid its price many times, compared to emacs, in my case.) Adaptation to established procedures: I have rejected a good handful of tools because the UI did not communicate in established professional terms and/or didn't support established work procedures or standards. The software developers just made their best guess.
To illustrate this with an experience of my own: In the old days when we had needle matrix printers with an ink ribbon, I was teaching a week long course, introducing computers to office workers who had never seen any more advanced tool than an IBM Selectric before. I taught them on screen editing, automatic text justifation, chapter numbering and TOC generating - all the things that we, as developers, were proud of. The last hour was reserved for reactions and comments to the course. The first thing that came up, and the only thing that all the participants agreed about, was the color of the printer ribbon! The black was almost bluish - cold, unfriendly. Would it be possible to get a more brownish ribbon, to give their correspondance a warmer, more friendly impression?
That was an essential point for the acceptance of our office automation system! Lots of systems succeeds because they e.g. provide (high quality) translations of the UI. That they use the right terms. That the end users understand what's going on.
I never used VB, so I can't tell why it has been so successful. I guess many of the reasons are non-technical. Then again I could say the same about other system that is used within the software business, such as the Internet protocols: They certainly didn't succeed becase they were the best designs, but 99% for non-technical reasons. Then entire "C class" of languages: The same. You won't be able to point out technical merits that can explain why the "C class" came to dominate the programming world. Then it is not fair to condemn VB purely on its technical merits (or lack thereof).
|
|
|
|
|
Member 7989122 wrote: As a general rule, people showing the kind of hashness as you do, toward one tool (or standard, or whatever) tend to have a poor understanding of how to use it. Or they consider it out of its intended scope of usage.
Or like me, they simply want to trigger the commie hippies that love it.
Member 7989122 wrote: A number of years ago ... blah f*ckin blah ... That the end users understand what's going on.
(yawn)
Member 7989122 wrote: I never used VB,
Count your blessings. I've had to use VB, VBscript, VBA, and VB.net. I've been a programmer for almost 40 years, and I think that makes me qualified to identify crap when I see it. It's like the MS Access of computer languages.
".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
|
|
|
|
|
John Simmons / outlaw programmer wrote: It's like the MS Access of computer languages.
Or as I like to call it "MS Abscess"... 
Sincerely,
-Mark
mamiller@rhsnet.org
|
|
|
|
|
Just because you can use a shovel for pounding nails and "everyone" else is doing it too, doesn't mean it's a good thing.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Why shouldn't we?
All programming languages have their good and bad.
However, there's one thing certain. VB sucks big time.
The whole language is way too wordy.
It ruins my display with too many characters.
"If" must be closed by "End if"
"For" must be closed by "End For"
"While" must be closed by "End While"
How many characters are there in the last one? 9! 9 characters in order to close a code block!
I used VB as a beginner. I moved to C# when I got better. Nowadays I use C#, Java, PHP, Javascript (Jquery). I have never thought of going back to VB. It's like an embarrassing past I wan't to bury forever. Using {} is so much much better.
|
|
|
|
|
... except when you accidentally close the wrong block, and spends hours to find out why it is not working.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
