Why QBasic GUIs are pointless to make...

[seph]

Nobody will use them. Ever.

- They are slow
- They are outdated
- They are obsolete
- If ever a programmer needs a GUI for anything, he or she would most likely make their own
- They are each created with an interface/graphics only it's creator could truly love

The same applies for most programs, like game engines for example. The only program that comes to mind that anyone will use of yours (that isn't a game) is a library. And it sure as hell better be pure ASM and the fastest library ever made, or else nobody will use it.

Sorry for this post, too much free time on my hands. Actually I'm waiting for my stepbrother to get back from wherever he went, so we can finish this level of Phantasy Star Online (yet offline). I pretty much had to get to the master all myself Oh well, I guess I'll try and beat it now.

[Zack]

There's something called practice...And something called a challenge...A GUI can provide both.

[na_th_an]

Yeah. I guess QB coding is only for challenge, being plainly easier coding in C, 32bits with a good library. Coding in QB is a true challenge: You run out of memory, the language is slow, it is for 16 bits, adding sound is a pain, portability equals ZERO, it won't work properly for 90% of PC users (as they are only "users") and so forth. Coding in MSVC/Allegro/FMod is a piece of cake just for lazy coders like me.

So the point on coding a GUI is exactly the same point as coding anything else in QB, and Zack has depicted it really well.

[Agamemnus]

Seph is right that qb coders usually just code everything themselves. (GUI-wise, I mean) Why? Because we're lazy bastards.

[toonski84]

Meh, as far as I see it, no one's ever going to use a qb program. Why make them?

for yourself

[Sterling Christensen]

So that's what you think of the graphics/GUI lib I showed you on that other thread you started?

What do you mean slow? It's extremely fast. Did you even look at it?