brainfuck

I use brainfuck through this custom ruby library I wrote; it's basically a meta language which generates brainfuck for me using readble syntax as input

What are your implementations?

wooooooooooby da booooooooooooooby

I write x86 ASM that a WIN32 application written in SEPPLES loads into dynamically allocated memory and runs.

Oh and WINDOZE is really not that bad. You just have to remember your SetErrorMode and SetExceptionFilter.

ASM is awesome. I don't get why more people don't use it. It forces you to write shit in such a way that it becomes more and more optimized as time goes on (kinda the opposite of Java). Old crapcode that is no longer needed in memory? Overwrite that shit with new code or use it as storage! Bloated macro files? Store that shit in a directory you never look into! You can define functions AFTER using them! You never have to worry about types or objects!
In fact you can just overwrite random portions of memory. Don't worry about shit like overwriting your own code. Your code tells you when you went wrong by not working, and in that case you can just change a few memory addresses to other random values and it will work again!
Awesome! You don't have to think, you can just FEEEEEEElLLLLllLLZLZZZZZLLLLLoaHOH GODhowDidthisGODASDSOOOOOOOOOOOOOOOOO
ASM IS GOD
I WORSHIP ASM

>>4
Where did you learn ASM ? I wish I could write some.

>>5
http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html

>>5
I wish I could write some.
It's easy, just remember that in x86 ESP is the only general-purpose register that affects something important (the stack pointer). The other 7 are good to go.
Just move ESP into the middle of a huge memory location and you can have recursive functions that recurse millions of times without overflows. The stack is also just a location in virtual memory. To understand virtual memory, think from the POV of the virtual memory, not "real" memory. There is no such thing as "real" memory unless you actually want to take your RAM apart and poke it with needles.

Where did you learn ASM ?
This page: http://ref.x86asm.net/coder32.html , Google and trial and error. Try it until it fails, not until it succeeds. The general mindset I have is that what you should learn is how things don't work. Something works? Fuck with it until it doesn't. If you cannot get it to break, congratulations, you can define that particular functionality in whatever way turns you on.


However, with the mindset I described above, it's easy to fall into the http://en.wikipedia.org/wiki/A_dicto_simpliciter fallacy. Don't actually overclock your computer until it breaks, unless you have many computers.

I'm currently writing an MS-DOS device driver, you really can't fuck around like that

bampu pantsu