Results 1 to 21 of 21

Thread: [RESOLVED] Save VB6 From it's slow death!

Thread Tools
- Show Printable Version
Display
- Switch to Linear Mode
- Switch to Hybrid Mode
- Threaded Mode

Threaded View

Jan 30th, 2014, 05:17 PM #14
Niya

View Profile

View Forum Posts
Angel of Code

Join Date

Nov 2011

Posts

9,017
Re: Save VB6 From it's slow death!

Oh God, not another one of these threads.

Originally Posted by axisdj

I know many .net folks cringe at the idea, but I'm we want to create native apps that are not bogged down with a huge framework of classes we don't need, and JIT compilation.

I won't even bother.

Originally Posted by axisdj

My apps are NOT business apps they control robotics and radio station automation where native apps just perform better because of constant hardware interaction...

VB6 would be a half measure at best. Just do it right and write the thing in C. That way you gain portability through all the various C compilers out there that target different platforms. We don't need to revive work on VB6 for this.

Last edited by Niya; Jan 30th, 2014 at 06:24 PM.

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
Reply With Quote