This is alarming in it self.
Printable View
You guys should just stop screwing around and move to VB.Net already. All this talk about Delphi and Lazarus is just childish pouting simply because MS did something you didn't want them to do. Get over it already. I did.
DOS 6.22 is the future! :ehh:
We need a new BASICA.
I'm going to call my pet rat VeeBeeSix so when he dies a can say 'VeeBeeSix is dead'.
As someone who started in 8-bit Basic, moved to OOP and trained in Java during college, then to VB6 because unlike Java it could actually do GUIs well, and then moved to VB.NET because it was OOP, then to C# because it was more syntactially like Java and C but worked well on Windows - and who has spent most of my professional career programming web applications first in Web Forms, then in ASP.NET MVC, it astounds me that Javascript is making strides on the server realm by vehicles like Node.js.
Further astounding that C# is borrowing dynamic pieces of the js language to compete on the server with technologies like Ruby on Rails, and Node.
And then you have the constant drum of improvements to HTML5 and ECMAScript which 'promise' to bring cross-platform capabilities to every device, which in a sense, it has done already - every time you visit a website, they're all interactive JS applications and barely static web documents - all rendered in a runtime called your browser. Most of that cross-browser capability thanks to frameworks like jQuery, Angular, Backbone and YUI.
As far as VB6 - there's nothing about it I have missed other than the fact it was the first language I used to build my first salable application, but I probably couldn't fix a lick of code in it since I've long since forgotten it.
See this: http://msdn.microsoft.com/en-us/magazine/dn745870.aspx
Megan Winter: Friday, June 6, 2014 7:46 AM
For instance, VB.NET has very few programmers, that is a failure !
VB.NET was born of hate, the main reason is the decision from 2002. While VB.NET was shoved down our throat, VB6 was/is becoming more and more popular and had/has more and more open source projects for various fields.
"a major technical achievement" is when the new language it is taken over by the community of developers. This never happened to VB.NET in 12 years.
When other programming languages are preferred, then you have to admit that something is not right with your product. That is what Paul Yuknewicz did not realize when he rejected the idea "Bring back Classic Visual Basic, an improved version of VB6". This idea had the quickest climb to the uservoice top 5. Probably they were scared when they saw how quickly the VB6 idea was climbing.
Now, Paul Yuknewicz, instead of being regarded as a hero in the VB6 community, it will be regarded with hatred and many will write very bad things about him (for a good reason).
Let me tell you why you are the deeply deluded one: by your logic, Turbo Pascal, QBasic and C# would have to be on the first positions in the TIOBE top 10 because are older than VB6! But it is not so, thus it is best not to rush in early statements.
Interesting if somewhat rushed and incoherent look back:
Trust, Users and The Developer Division
And make no mistake, staying with VB6 is as much "walking away" as moving to Java.Quote:
At the end of the day, developers walked away from Microsoft not because they missed a platform paradigm shift. They left because they lost all trust. You wanted to go somewhere to have your code investments work and continue to work.
For the unaware: David Sobeski was a former Microsoft General Manager.
Ex-insiders are now free to reveal what a mess things have been.
@Fatina
Where you do come up with such non sense? VB.Net has very few programers? Non sense. Based on someone earlier talking about the signatures on the petition which was under 10k being a lot I suppose there must be less than 2,000 people using VB.Net and all of them registered here ;)
At any rate it is no surprise that they will not be doing another version of VB6, most of us knew that 10 years ago.
VB6 can not compile code for ARM processors
And the COM I was referring to is serial port rather than ActiveX
That is just plain dumb and just shows how twisted some VB6 developers have become. Even if you have some logical arguments in favour of VB6, which there obviously are, comments like this simply undermine everything else you have to say because they make you look crazy.
Seems that Fatina is an extremist and chooses to take the word of the internet as truth rather than like everything with a grain of salt.
Yes there are methods in .Net for this, you can use some stuff from VB6 and you can use the ocx controls.
My point was that as of Framework 1.1 which shipped with VB 2003 there was no method to talk to a serial port included and while you could make MSComm work on a PC you could not do so on mobile devices which is what I was developing for at the time. Framework 2.0 added the serial port support and many other things, also improvements made in the IDE in the 2005 release and rapidly became my preferred tool for mobile devices and many of my PC tasks as well though I still use VB6 quite a bit as well.
After reading this post from beginning to end I tend to think Shaggy Hiker asked a good question back in post #21.
Any shift in programming technology forces the programmer to absorb new concepts.Quote:
...What are the objections to VB.NET...
Sometimes this is not possible to do all on your own.
The knee jerk reaction for many is frustration or some other emotional response usually ending in shelving any study in the new direction.
My programming skills are mostly self taught. I can remember coming up against OOP for the first time. I didn't get it at all.
I taught myself Borland's Turbo Pascal from versions 2.5 on up. I decided to ignore OOP and keep producing procedural programs.
The folks on programming bulletin boards (Internet and Forum precursors) complained mightily.
"How dare Borland make this change." "I'll jump ship to Microsoft first." Etc...
I also ignored Microsoft Windows and continued to use MS-DOS. Mainly because i didn't own windows at home.
Finally Windows 98 became the tool of choice at work then Win NT and i needed to write apps for myself at work.
The company owned a copy of VB5 that no one was using so I loaded it on my machine and was very unhappy.
The hurdle this time was event driven programming. Functions and SubRoutines. It was a whole new world.
I found someone to give me a couple of hours of personal tutoring to get me started. After that I made headway but still had trouble with other concepts.
By the time i upgraded to VB6 I was pretty comfortable with the product. I had 'discovered' the internet and programming forums.
I cannot say enough how grateful I am to the VB community and the generous folk that dwell here and on other forums.
They are the reason I believe in giving back by helping when and where I can.
I ignored VB.NET for quite a while.
I made the jump from mechanical engineering to software engineering and amazingly was getting paid to code.
Part of the resistance was I was usually under pressure to create apps in short order. I didn't feel I had the time. Period.
Again the good folk online helped to explain the differences. The reasonlng behind the changes. How I could leverage them.
Even so It took a long while to accept OOP. I think seeing how the namespaces and the native classes simplifed using tools
finally tipped me over the edge. Now I cannot imagine not using classes and inheritence.
I also ignored WPF in favor of WinForms. Again the concepts are not easy for me.
Lastly I would like to address the future of programming. Historically I rescricted myself to desktop programming.
Never learned how to write web apps. Zero background.
So the question on my mind is what happens when Microsoft decides to stop supporting desktop development?
All signs point to that as the eventual goal. How many of us will curse and complain or make the jump when this happens?
Bulletin Boards? Showing a little age there ;)
I used to operate a BBS under OS/2, back then most of my coding was in VBDos with a little Pascal and Turbo C++ here and there, also self taught. Eventually I was forced to move to Windows and VB5 for work.
The Event Driven and graphical aspects of VB for windows was quite a lot different than working in the previous DOS languages, took a while to wrap my head around some of it but some of it was just so easy compared to what I had done in the past. VB.Net was kinda that way to, some things took a while to wrap my head around but right away I found that some things were much easier than they were in VB6. The very first program I wrote in VB.Net took less than 1/2 the time it would have taken me in VB6 and that is with years of experience in VB5/6 and none in VB.Net
I think the whole jar is missing.
That is not my message !
That's not true!
That's not true!
What does that even mean?
Nobody, outside of Apple, prefers to use Objective-C... I'll bet that in 12 months the number of developers that use Objective-C over Swift will be minuscule. Swift has generics, garbage collector, type inference, closures. tuples and so on... Where have we seen all of these features before? Oh, I know! In VB.Net!
Excuse me but when was QBasic last used? And how did C# get older than VB6, that's just stupid? Do you even have any idea of what you're talking about, because I certainly don't?
Well, personally I don't do shrink wrapped applications. I'm a consultant and everything I develop belongs to my customers. But if you want examples then here's a couple: Windows Defender is now an integrated part of Windows but before Microsoft acquired it, it was called GIANT AntiSpyware and it was written in VB.Net. Want another example? How about the next version of the VB.Net compiler? It is written in VB.Net.
One of the qualities of the computer lies in its continuous evolution.
VB6 is the past, vb.net is the present, and one day vb.net also it`ll becomes the past, and another new one will take its place.
I personally use both, and I love both.:)
I am more curious as to what word was censored out....
Hmm. Missing marbles and throwing out squirrels, as well.
I went to the article, since it was a Microsoft web site, to see who was writing such drivel. The MS article has nothing to do with the quoted text - it is another raving lunatic, full of hate.
So, the quote above is disingenuous at best. When someone has to resort to deception to prop up their standpoint, then you know they have nothing.
The opposite of love is not hate. It's indifference. (Total lack of feeling or importance.)
So Fatina. I am not a hater. I indifference you.
Wouldn't that be apathy then? Meh, what ever. Don't care.
-tg
Squirrels? Reminded me of:
CEO Friday: Why we don’t hire .NET programmers
Quote:
Programming with .NET is like cooking in a McDonalds kitchen. It is full of amazing tools that automate absolutely everything. Just press the right button and follow the beeping lights, and you can churn out flawless 1.6 oz burgers faster than anybody else on the planet.
However, if you need to make a 1.7 oz burger, you simply can’t. There’s no button for it. The patties are pre-formed in the wrong size. They start out frozen so they can’t be smushed up and reformed, and the thawing machine is so tightly integrated with the cooking machine that there’s no way to intercept it between the two. A McDonalds kitchen makes exactly what’s on the McDonalds menu — and does so in an absolutely foolproof fashion. But it can’t go off the menu, and any attempt to bend the machine to your will just breaks it such that it needs to be sent back to the factory for repairs.
Instead, we look for a very different sort of person. The sort of person who grew up cooking squirrels over a campfire with sharpened sticks — squirrels they caught and skinned while scavenging in the deep forests for survival. We don’t want a short order chef, we want a Lord of the Flies, carried by wolves into civilization and raised in a French kitchen full of copper-bottomed pots and fresh-picked herbs. We need people who can not only cook burgers, but cook anything, from scratch.
dilettante, You slay me. :)
I just remembered the strange analogy relating to programmers that involved squirrels as food.
As far as I can tell that whole post was based on mis-remembering the earlier:
Don't Make Squirrel Burgers
I am a girl you m o r o n !
Save the squirrels!