|
-
Jun 15th, 2014, 11:37 AM
#11
Re: VB6 is DEAD!
 Originally Posted by Schmidt
Nah, come on ... where was the insult?
What shoe did you choose to put on (aka why do you *feel* insulted)?
I mean, I've calmly explained just my point of view... if you think that I'm utterly wrong,
then there's no reason to feel insulted - just laugh at me - or label me "backwards" or
"unwilling to learn new things" or just "VB-cry-baby" or whatever creative (and of
course non-insulting) attribute for a VB6-developer comes to mind *this* day.
But you are NOT utterly wrong. You have a rational view and post some good stuff which is well supported. You're clearly quite a capable and knowledgeable programmer. What drives me crazy is that you can't seem to resist adding swipes at people to otherwise good posts. That particular post labeled all .NET programmers as misguided fools. You talked about the C++ programmers "shaiking their heads at ...those who wasted their time and money...etc." Are we to assume that those C++ programmers were actually idiots who couldn't comprehend the wisdom of people who wasted their time and money? Are we to assume that those C++ programmers were shaking their heads not in disbelief, but in some kind of ecstatic frenzy?
No, probably not, since in the very next sentence you described .NET programmers as being those fooled by MS-foolishness. So, how could anybody see that as anything other than snidely condescending? And to what end?
That's not the point.
There's a whole lot of other VB6-devs like me, who simply decided what they thought was right for them
to do (at that point in the past) - and "unwillingness to learn new things" or even more ridiculous:
"fear of OOP-concepts" was the least, believe me.
That's clearly true. I never thought you, in particular were even hesitant about OOP (nor Carlos, for that matter), I do think it's a valid reason to be hesitant about moving from a non-OOP language to an OOP language, as they are quite different in structure, but I didn't think it was your concern. I also agree that there are lots of VB6 devs like you, who feel that MS should have gone in a different direction. Depending on what that other direction happened to be, I may or may not agree with you. However, it doesn't mean that all the people, like me, who switched to .NET and gladly discarded VB6 once we realized what .NET had to offer are simple fools deluded by MS. Just as the VB6 afficianados can't agree as to what features are essential to a new version, those who moved to .NET probably had all kinds of different motivations, as well. For my part, I was forced into it because VB6 didn't work for PDAs (not counting eVB, which wasn't VB and really really sucked). Once I got into it a little bit, I was so happy with it I never used VB6 again. I didn't remain with one foot in each boat, I just moved over and didn't look back. Does that make me a deluded fool that all those wise C++ coders shake their heads at? Probably not.
Sometimes the decision "to wait until some things become more clear" is not
unwise, you know?
That's true. Of course, .NET in the modern version (discounting 2002 and 2003, as they were a different form of animal), has now been around longer than VB4/5/6 were actively being advanced, so...you can't wait forever. .NET will also die, just as VB6 did (and 4 and 5 before it). As long as the sole reason you are waiting is not to say "I told you so," and as long as you can progress personally in that time, the you should do as you want. What else you said, including not liking Java, I fully agree with. I don't really care about native code, but it DOES have some benefits that would be of value to me...though minor value, frankly, but that's just my situation. So, if .NET compiled to native code, all the better, but since it doesn't, it doesn't bother me much.
What I'm pointing out to you is simply, that I cannot understand why you
*still* mark people who made such a decision, as "living in the past" -
*especially* after experiencing all those confusing decisions and the latest
back-paddling maneuvers on the part of MS over the last years and months.
I try not to mark people as living in the past for sticking with VB6. Until axisdj started the various threads he started, I had no idea that there was any particular passion around those who used VB6 or .NET. I assumed that it was just a tool like any other tool. I have worked in several languages, as have you, and I expect to work in several more before I retire. I'd love it if there was one size that fit all, but I'm resigned to the fact that there is not and will not be, so I choose what I like and what I don't like, but they are all just tools that I can pick up and put down. I have no emotional attachment to them and expected others to feel the same way...with the exception of C++ coders looking down on VB coders, which is so trite that there are cartoons about it.
On the other hand, once I did see how much passion some people have about some particular language, I'd have to say that I find it kind of fascinating, which does lead me to write things that could be considered, "poking the nest." I still don't care about the languages, though, I'm interested in the viewpoints. Axisdj, for his part, explained himself quite well, and I see why he feels as he does. I don't agree with him, but his views come from a reasonable motivation. Fatina, on the other hand, has some issues. She refuses to say anything about why she is so passionate about VB6, which is especially odd because I'm getting the impression that she isn't, herself, a programmer.
In any case, I would say that by now the basis for all of these threads is mostly just stoking the fires.
My usual boring signature: Nothing
 
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|