C++ just has too much shit

Too much shit going on behind the scenes.  *rewrites application in Racket*

write your app in your processors assembly language then

>>2
And make sure all the shit goes on stage! :D

>>2,3
Well, I don't care if unimportant things go on behind the scenes, but since C++ has manually managed memory, I don't want anything going on behind the scenes.  All these stupid_pointers and copy constructors just fuck my shit up.

I initially used Tcl with Tk, but it was just way too slow and inflexible.  I'd write it in C, but since it's a GUI application (and not really something I'd want to use Curses for) it'd take too much time.  This is just some quick application (dungeon mapper for Wizardry) I don't intend to support for a long time.

>>4
Because you really need all the performance you can get, huh?

>>5
Dude, the program took like 20 seconds to start up.

>>6
Oh, ok. Never used Tcl/Tk, but are you sure that it's not just your computer?
And I'd just use something with automatic memory management, perhaps C# with .NET.

>>4
I'd write it in C, but since it's a GUI application (and not really something I'd want to use Curses for) it'd take too much time.
wat.

>>7
EXPART Windows user.

FUCK

>>8
Now that I think it over, the GUI part is not what would take the most time (although I know no API, so it just might) -- it'd be all the data structure stuff.  That just takes more time in C.

>>4
Qt

>>11
I used SFML, but I'd seriously prefer something honest like Win32 with GDI.

>>1
racket
Debian is still stuck on DrScheme.

I'm not sure what the problem is here.

>>8
Curses is the best shit ever.

>>15
Doesn't change the fact that it's still shit.

>>16
Use [u][i][b]New[/] Curses[/i][/u] then, fucker.

Don't change these.

Name:		Email:
Entire Thread Thread List