Results 1 to 40 of 663

Thread: VB6 is DEAD!

Threaded View

  1. #11
    Angel of Code Niya's Avatar
    Join Date
    Nov 2011
    Posts
    9,017

    Re: VB6 is DEAD!

    Quote Originally Posted by Carlos Rocha View Post
    Slow initial startup? that's it? no, it isn't. I still remember the first ATI control panel made with .NET. It was simply scaring!! "what is this, what did I do wrong, and only clicked that button...?". But it wasn't me, it was .NET fault.
    Only a poor workman blames his tools. Cliche, I know but it definitely applies here. I get no problem with my VB.Net apps other than the typical errors we make as coders like off-by-one errors or null references.

    Quote Originally Posted by Carlos Rocha View Post
    .NET is newer than the "old" Win32, so maybe it relies on faster technology
    You do know that ALL software in Windows uses the Win32 API right ? VB6 apps, .Net apps, Delphi apps. The VB6 runtime wraps these calls. The ActiveX components you may be using would also wrap these calls. The .Net Framework also wraps these calls. You can't escape Win32.

    Quote Originally Posted by Carlos Rocha View Post
    , but the principal factor is that .NET steals all the resources for itself
    Typically my .Net apps use around 8 MB of memory. I have 2 GB of RAM with around 800 MB free at any given time. How is that even close to using all the resources ?

    Quote Originally Posted by Carlos Rocha View Post
    Don't you think that, had Classic VB been evolved till now, it would be a lot faster now than back in 2000? and less resource hungry than .NET? Please be serious if you answer to this.
    Perhaps, but customers users don't really care about millisecond improvements as long as their favorite apps are fast enough.

    Quote Originally Posted by Carlos Rocha View Post
    .NET was a mistake, a big one, and Windows is suffering a lot because of that wrong move. C'mon, admit it, as M$ already did.
    How can it be a failure when its been embraced by millions and MS still updates it to this day. Wishing for it to fail doesn't make it so. MS abandoned VB6 something like 15 or 16 years now. VB.Net was its successor. If it failed, then why don't you have a new VB6 ?
    Last edited by FunkyDexter; Jun 17th, 2014 at 11:03 AM. Reason: Removed a couple of comments I didn't think were acceptable
    Treeview with NodeAdded/NodesRemoved events | BlinkLabel control | Calculate Permutations | Object Enums | ComboBox with centered items | .Net Internals article(not mine) | Wizard Control | Understanding Multi-Threading | Simple file compression | Demon Arena

    Copy/move files using Windows Shell | I'm not wanted

    C++ programmers will dismiss you as a cretinous simpleton for your inability to keep track of pointers chained 6 levels deep and Java programmers will pillory you for buying into the evils of Microsoft. Meanwhile C# programmers will get paid just a little bit more than you for writing exactly the same code and VB6 programmers will continue to whitter on about "footprints". - FunkyDexter

    There's just no reason to use garbage like InputBox. - jmcilhinney

    The threads I start are Niya and Olaf free zones. No arguing about the benefits of VB6 over .NET here please. Happiness must reign. - yereverluvinuncleber

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
  •  



Click Here to Expand Forum to Full Width