www.Slow-AssEuphoria.com
Damn!
After some benchmarks, written by yours truly zupahh
l33t hax0r coder, I found out Eu is slow
as...well...hell!
It takes it a 100 times longer to execute a simple
for-loop with an evaluation inside when compared to
the same code written in LCCWin.
But, however, once translated to C and compiled with
LCCWin, it's only 20 times slower on that subject.
I still can't believe why there's still "Almost As
Fast As Compiled C!" floating around here.
Sure, Eu is faster than QBasic, or a 1993 freeware
crap-ass Small C compiler or some shit. But can it
stand up tall against Vector C (Uses sequences BTW)
and VC++ 6.0? What about VC++ 7.0 when it is released?
What about COM, DCOM, ActiveX, OLE, Direct X 8?
And then you wanna know why Microsoft don't write
their
OSes in Euphoria? Or why there's just "a few hundred"
customers in the entire world after 8 years of being
sold?
Don't get me wrong, Euphoria is an excellent language,
and features great memory handling for DOS.
But it just hurts me to see such and excellent, the
best, easiest, must flexible, and sexy language in the
world, with 25.000 lines of C code wasted to it, being
created by people that don't see a market when they
are publically decapitated in the middle of one.
That much effort the write Euphoria, that excllent a
language syntax, and that crap-assed out-dated slow
features. Yeah! Woohoo! You can display images up to
256 colors in size! At 1 FPS on an Intel IV 2Ghz! In
DOS only! YEAH! THAT'S WHAT WE NEED TO WRITE THE NEXT
UNREAL TOURNAMENT!! Come on... Ya gotta do better than
that.. Spead up the interpreter a little... Translate
to Machine Code internally.. GET RID OF WATCOM FOR
CRYING OUT LOUD! THE CREATORS DID! Go get VC++ 6.0 to
compile Exw.exe. With full optimisations. Add DLL
compilation support. Add object file compilation
support (I personally designed the method to do this
interpreted). Hand-code the interpreter in Assembler
for all I care, but don't slap some new library
routines based on old ones but with an easier sytax
and call it all new version.
I'm here to do one thing; Make sure Eu gets what it
deserves.
I'm gonna be bitchin' and flamin' untill yall listen
to what I say.
I know Eu's flaws. Fix up that translator for example.
Run sequence.ex with the interpreter. Write down the
results. Now compile it with the translator. See what
I
mean? It's almost the same results, with the exeption
of the interpreter being FASTER in some procedures.
I thought you were going to write a translator to make
things faster, not slower. Sure here and there, for
loops and crap, the translator is faster. But how much
faster? You shouldn't be sattisfied untill C runs
SLOWER than Euphoria once compiled to C.
Use clever #ifdef constructs combined with calls to
call() in the source produced so you can optimise some
sections with machine code. Implement simple global
optimisation techniques into the interpreter and
translator. The following code:
for i = 1 to 487487878787 do
myvar = i
end for
Should NOT be ran. It should just be re-written to
"myvar = 487487878787" by the interpreter. Dead code
sections should be stripped out. Variables that are
never called should not be created. Cache-burst,
peephole, function call, evaluation, etc. optimising
should all be implemented. and blah blah blah.....
ah hell....
I'm getting tired bitchin' all day long....
I'm gonna go get some sleep..............
Mike The Spike
PS. Wha? GET OFF YOUR LAZY ASS ROB AND START
WORKING!!.......NOW! hehe J/K :p
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
|
Not Categorized, Please Help
|
|
