What if there was a NEW vb6

[Niya]

That's not true, MS released MS Dos. It only took... Oh wait, maybe they shouldn't hold their breath :P

lol and it wasn't even the latest DOS. It's DOS 3.1 or something. I downloaded it a few months back. When they eventually do this with VB it would probably be VB2 lol.

[DataMiser]

Or VBDos

[Niya]

Or VBDos

Yes, even more likely.

[Niya]

Wait a second......why was axisdj banned ? Sauce on this anyone ?

[dilettante]

Probably refused to program in VB.Net.

[jayinthe813]

he was on thin ice after he posted a bunch of decompilers (to showcase his point about ability to steal code). I wonder what happened after that, hmm..

[dee-u]

Looking at his posts he is last seen talking about VB6 and XML.

[Niya]

Looking at his posts he is last seen talking about VB6 and XML.

Well it couldn't be those posts. I'm thinking his offensive was committed via PM. Or it could be that his offensive posts were removed by the mods as mine were when I was first banned.

[axisdj]

Well it couldn't be those posts. I'm thinking his offensive was committed via PM. Or it could be that his offensive posts were removed by the mods as mine were when I was first banned.

>> Can we bring back ___ at the same time?

Can we bring back C...wait...no need the application owners did not kill it.
Can we bring back C++...wait...no need the application owners did not kill it.
Can we bring back ADA...wait...no need the application owners did not kill it.
Can we bring back FORTRAN...wait...no need the application owners did not kill it.
...
Can we bring back VB6...NO!
MS says you must recode all you currently working apps to .Net. Stop being lazy and get to it!
...wait...will MS be paying our clients to pay us to do the recoding?

But MS supports the open model now?
Nope. Not for VB6. Apparently their model is a "semi"-open source commitment. Not for anything that would overtake .Net. Huh?

Then why are they killing something that incredibly successful? Why indeed!

[axisdj]

This may be another option:

There is a PowerBASIC project to develop a converter from the VB6 programming language to PowerBASIC.
http://www.powerbasic.com/support/pb...splay.php?f=70

It seems others value VB6 more than Microsoft.


Every time I want to give up I meet another dev or municipality that runs a vb6 generated app.....

[dday9]

The cool thing, especially in the United States, is if you do not like how a person/group of people is/are operating a business you can:
1) Take majority ownership and make some changes
2) Complain to the company
3) Create you own business with a similar product to your liking

I'm sure all the money from all the users of VBForums combined is not enough to take majority ownership of Microsoft, so number 1 is out. You and several others have repeatedly complained to Microsoft, yet they have taken a stance and they are very clear that they are sticking to it.

Really your only viable alternative is the last suggestion. If you do not like the semi-open support of VB6 and you do not like VB.Net, then create your own version of VB6 and market/support it the way you would want to. Other than yourself, who/what is stopping you from doing that?

[DataMiser]

>> Can we bring back ___ at the same time?

Can we bring back C...wait...no need the application owners did not kill it.
Can we bring back C++...wait...no need the application owners did not kill it.
Can we bring back ADA...wait...no need the application owners did not kill it.
Can we bring back FORTRAN...wait...no need the application owners did not kill it.
...
Can we bring back VB6...NO!

Funny, of course you are not saying can we bring back Visual C++ 2.5 or any other specific version on anything other than VB.

Can we bring back VB, no need it is still going strong just undergone some evolution just as have all the others that are still around.
Ironically Fortran also got a major revision shortly after VB did and also moved toward OOP

One thing I have noticed lately despite the fact that a few people keep yammering for a new version of VB6 is that the VB6 sections of the forums are getting quite a bit less activity than in the past and the VB.Net sections are getting more.

[Gruff]

Voting with my feet by walking away from this topic.

[NeedSomeAnswers]

>> Can we bring back ___ at the same time?

Can we bring back C...wait...no need the application owners did not kill it.
Can we bring back C++...wait...no need the application owners did not kill it.
Can we bring back ADA...wait...no need the application owners did not kill it.
Can we bring back FORTRAN...wait...no need the application owners did not kill it.
...
Can we bring back VB6...NO!
MS says you must recode all you currently working apps to .Net. Stop being lazy and get to it!
...wait...will MS be paying our clients to pay us to do the recoding?

But MS supports the open model now?
Nope. Not for VB6. Apparently their model is a "semi"-open source commitment. Not for anything that would overtake .Net. Huh?

Then why are they killing something that incredibly successful? Why indeed!

Moan Moan Moan, boring ...... You just can't move on can you?

Its like those people who complain that a piece of Ikea Furniture has been discontinued and that specific piece of furniture was THE ONE THEY WANTED. Nothing else will do and the Evil Ikea people wont bring it back no matter how much they complain!!!

The things is VB6 is not dead, you can still use it. It works with Windows 8, it will work with Windows 9 it will probably even work with the one after that.

Oh and one final thing BORING !!!

[Mr_Cam]

I'm still appalled at why people still use VB6. Like, there are newer / better versions. Or i am just missing something here?
Because it seems quite silly to cry about this lame VB6 crap. Really. Just. Why?

And i agree with NeedSomeAnswers, boring indeed.

[techgnome]

Moan Moan Moan, boring ...... You just can't move on can you?

Its like those people who complain that a piece of Ikea Furniture has been discontinued and that specific piece of furniture was THE ONE THEY WANTED. Nothing else will do and the Evil Ikea people wont bring it back no matter how much they complain!!!

The things is VB6 is not dead, you can still use it. It works with Windows 8, it will work with Windows 9 it will probably even work with the one after that.

Oh and one final thing BORING !!!

I'm still appalled at why people still use VB6. Like, there are newer / better versions. Or i am just missing something here?
Because it seems quite silly to cry about this lame VB6 crap. Really. Just. Why?

And i agree with NeedSomeAnswers, boring indeed.

So quit replying and feeding the beast.

-tg

[FunkyDexter]

I'm still appalled at why people still use VB6.

About the best argument I've seen so far is that they have a large body of work in it already that they need to maintain. I'm not sure that argument still holds water after well over a decade but I do have some sympathy.

I think the posting pattern forum AxisDJ linked to says it all though: a few days of enthusiasm followed by... not alot. One guy doing all the work and everyone else just telling him all the stuff he's getting wrong. It's the same pattern I've seen on every other project of this type.

AD, I hope this project happens for you, I really do. But I wouldn't hold my breath and I certainly wouldn't build a business strategy on it.

[dilettante]

I'm still appalled at why people still use VB6. Like, there are newer / better versions. Or i am just missing something here?

No, there is no newer/better version. VB6 was the end of the product line.

You are just confused by The Great Pretender, VB.Net. Its many failings have been enumerated thousands of times since the the Great Destruction in 2001.

What I don't understand is why the naked emperors who use .Net are so frightened by VB6 programmers and feel such a need to attack constantly. Could it be that they really do know they have no clothes on?


How Microsoft Lost the API War was a look back a few years later. While it has taken longer than some predicted (Joel was right again) Microsoft has managed to destroy itself with that rough beast .Net, and in the wake of Windows 8 faces market share erosion that accelerates day by day.


Join us! There is a far more dynamic world of opportunity out there in the post-PC world.

[dday9]

No, there is no newer/better version. VB6 was the end of the product line.

You are just confused by The Great Pretender, VB.Net. Its many failings have been enumerated thousands of times since the the Great Destruction in 2001.

What I don't understand is why the naked emperors who use .Net are so frightened by VB6 programmers and feel such a need to attack constantly. Could it be that they really do know they have no clothes on?


How Microsoft Lost the API War was a look back a few years later. While it has taken longer than some predicted (Joel was right again) Microsoft has managed to destroy itself with that rough beast .Net, and in the wake of Windows 8 faces market share erosion that accelerates day by day.


Join us! There is a far more dynamic world of opportunity out there in the post-PC world.

I too will take the same route that Gruff took. Good luck to you.

[dilettante]

Well one could always become a missionary I suppose.

Letting go of Visual Basic
(my former life as a programmer)…

[FunkyDexter]

What I don't understand is why the naked emperors who use .Net are so frightened by VB6 programmers and feel such a need to attack constantly

One could also ask why you are so frightened by .Net programmers and feel such a need to attack constantly. Perhaps it's because you are aware you are wearing no clothes.

.Net developers really aren't scared of VB6 developers, any more than you are scared of .Net developers. We've all simply made our choice of platform based on the criteria that were most applicable to us. Ask us whether your choice of platform is better than ours and of course we'll say no, because if the answer was yes we'd have made a different choice.

I read the article, ten years out of date and, actually, still hasn't come true. I'm still seeing plenty of Winforms development which was, acording to that article, stillborn... over a decade ago. You've got to admire a stillborn technology that can outlive a headless chicken. But hey, let's not let reality to get in the way of overly enthusiatic hyperbole.

[dilettante]

If you read through all of these very similar threads you'll find that VB6 programmers almost never "attack" but have to defend against the repeated attacks from .Netters all the time.

I'm pretty sick of it and as far as I am concerned .Net can't die a quiet death soon enough. This is VB Forums and not VB.Net Forums. VB.Netters are guests here, and becoming less welcome day by day.

[FunkyDexter]

To be honest I see a mix of healthy debate and unhealthy attacks coming from both sides and in roughly equal measure.

And I really don't see any difference in status between Classic programmers and .Net programmers. It's all VB and we're all guests.

[szlamany]

I can feel some passive aggressive attitude from the Classic folk.

I just uncovered something earth shattering. VB.Net is written in VB6

Ok - maybe not...

I came from 20 years of programming outside of the PC world. When I got into PC's and started using VB6, it felt like a hobbyist language to me. The BASIC's I used in the past had evolved over those 20 years - VB6 looked like something from an Altair box. PC's seemed to have a nice API - but the method of getting to that API was over-the-top complicated - at least the syntax was visually. VB6 seemed to actually not be of the "same world as the API" it sat upon.

When I first saw VB.Net the shining gem of it all was the object-like name spaced method to attack the API. Now, for example, I could write my own HTTP listener by using a cleanly and uber-consistently written library of objects and functions and methods that expose the API.

So here I am 14 years into PC's and the .Net release by MS has only made me more productive.

I recently created code to read PST files. MS released a really nice C++ pstsdk (http://pstsdk.codeplex.com/) and I was able to bring that into a .Net solution and effortlessly process PST files with basically a handful of lines of code.

I like the way MS plays in this evolving industry.

[NeedSomeAnswers]

If you read through all of these very similar threads you'll find that VB6 programmers almost never "attack" but have to defend against the repeated attacks from .Netters all the time.

I'm pretty sick of it and as far as I am concerned .Net can't die a quiet death soon enough. This is VB Forums and not VB.Net Forums. VB.Netters are guests here, and becoming less welcome day by day.

What i find is VB6 developers consistently posting exactly the same argument and moaning about it again and again and again. It just gets boring after a while and its difficult to maintain sympathy for people who are not engaging in reality.

If you see my posts early on these subjects i tried to engage at least but after a while i realised that they all wanted the virtually impossible or nothing.

And also this artificial VB6's vs .Nets things. For many years (and i am sure i am far from the only one) i programmed in VB6, in fact i still do occasionally as we still have systems written in VB6.

I have written in ColdFusion & Flex and PHP

I now write more .Net than anything else BUT i also do more Web then i ever have before, and am moving towards more Json, JavaScript and JQuery.

I like many of us i am sure, i see my self as a Developer, not a .Net developer or VB6 developer, just a Developer!!!

Computer Languages are just tools in our toolbox

[szlamany]

I now write more .Net than anything else BUT i also do more Web then i ever have before, and am moving towards more Json, JavaScript and JQuery.

Same here!

I like many of us i am sure, i see my self as a Developer, not a .Net developer or VB6 developer, just a Developer!!!

Computer Languages are just tools in our toolbox

Really well said!

[techgnome]

dil - if you're feeling like you're being attacked, perhaps you should work on increasing your THAC0.

-tg

[FunkyDexter]

Surely that would need to be his AC. From what I've seen Dil's THACO is just fine.

[techgnome]

Or both. If he had a better THAC0 we wouldn't be here it would seem. He'd try to use a Cone of Silence on us .Netters. Maybe a change of class is in order.

-tg

[Niya]

Its many failings have been enumerated thousands of times since the the Great Destruction in 2001.

Ironic that you'd support its ancestor which has 1000x more failings. You people really confuse the hell out of me.

[Mr_Cam]

Not my fault it sucked and continues to suck...
*Shots Fired*
*Shots Fired*
*Shots Fired*
*Shots Fired*

[FunkyDexter]

Thinking about it Dil's THACO isn't that great. His #Att on the other hand is sky high.

[Shaggy Hiker]

The cool thing, especially in the United States, is if you do not like how a person/group of people is/are operating a business you can:
1) Take majority ownership and make some changes
2) Complain to the company
3) Create you own business with a similar product to your liking

I'm sure all the money from all the users of VBForums combined is not enough to take majority ownership of Microsoft, so number 1 is out. You and several others have repeatedly complained to Microsoft, yet they have taken a stance and they are very clear that they are sticking to it.

Really your only viable alternative is the last suggestion. If you do not like the semi-open support of VB6 and you do not like VB.Net, then create your own version of VB6 and market/support it the way you would want to. Other than yourself, who/what is stopping you from doing that?

Hey! You are ripping off the final chapter of Battle Programming 3.0. The chapter on How to Destroy a Company that annoys you (or something to that effect) covered this more succinctly: Provide the same service for free.

Here you are trying to cover the same ground that has already been thoroughly covered by existing literature. Moti should be annoyed, but his Barkski is worse than his biteski.

[Nightwalker83]

Hey! You are ripping off the final chapter of Battle Programming 3.0.

Oh dear, here we go again!

[Shaggy Hiker]

Oh dear, here we go again!

Lots of people say that in this thread.

[Carlos Rocha]

Lots of people say that in this thread.

Yup, they keep coming just to say that. Maybe because VB.NET is too simple and gives them lots of spare time?

[Shaggy Hiker]

Could be. On the other hand, perhaps they have all read Battle Programming.

[FunkyDexter]

Everyone should read Battle Programming. It's a fantastic piece of literature and should be on the school curiculum.

[NeedSomeAnswers]

Everyone should read Battle Programming. It's a fantastic piece of literature and should be on the school curiculum.

What do you mean should be, at the Academy i have just Opened IT IS the cirriculum!

[Niya]

Yup, they keep coming just to say that. Maybe because VB.NET is too simple and gives them lots of spare time?