FLAC

When I use a lossless format, I don't want eight extra KILOBYTES of worthless
proprietary algorithms and bloated decoding !  I just want a music!!
Not a "wma".  Not a "aac".  Those aren't even WORDS!!!! FLAC!
FLAC! FLAC IS THE STANDARD!!!

When I program, I don't want 200 extra KILOBYTES of worthless crud. I just want it translated to machine code! Not an "as". Not a "nasm". Those aren't even WORDS!!!! FASM! FASM! FASM IS THE STANDARD!!!

>>2 only 22 bytes
org 100h;
use16;

display_text = 9

mov ah,display_text
mov dx,hello
int 21h

int 20h

hello db 'Hello world!',24h

Has anyone ever had sex with their mother?

>>4
Forced Indentation of Cock

Look at it this way.

On most browsers, you can bring up your browsing history by pressing Control-H. (No, this is not going to become a discussion of werecows.) On Firefox, this brings up a sidebar that shows up on the left side of the window. If you put your mouse over the edge of the sidebar, the cursor will turn into a different kind of arrow. By clicking and dragging it, you can move the edge of the sidebar back and forth. You are, to put it another way, manipulating the border between the normal window and the history window. By moving the mouse, you can increase the portion of the window devoted to either part. In a more extreme view of this situation, you're increasing or decreasing the amount of existence the sidebar has.

Now, let's apply this idea to something more abstract. Look out your window. If you don't live in a highly urbanized area, you should be able to see the horizon. Think of this as the border between the land and the sky. The land and sky are obviously distinguishable thanks to this boundary. Now, if you were to "drag" the sash between the sky and the land, or to manipulate the border between land and sky, you would end up causing the sky to become larger and the land to become smaller, or vice versa. An effect of this might be to cause something that was just on the ground to suddenly be hundreds of feet in the air. Truly a frightening situation to be in. So, look at it this way - manipulating the border between two physical things shifts whatever balance there is in the interaction between those things. Alternatively, by manipulating the border between two things, you can change the manner in which they exist.

Still, this isn't *that* abstract, since it's still dealing with real things in the real world. Many believe that in this world, there are those things that are true, and those that obviously aren't. This divides reality into two extremes: truth and falsehood. But, since we have two extremes, logically one can imagine a boundary between those two extremes - the border between truth and lies. If one were to manipulate this border, suddenly things that were pure fantasy (flying pigs, for the sake of argument) have become reality - or things from reality have ceased to exist. This is how Yukari is said to have invaded the moon - by manipulating the border between truth and lies, as applied to the reflection of the moon on a pond, she was able to make the reflection of the moon into a manifestation of the actual moon, and so send her youkai army onto it. This is what's truly amazing about Yukari's power - the ability to manipulate the border between completely abstract concepts allows her to fundamentally change reality as we know it (at least in terms of two abstract concepts).

>>6
this

>>3
% ll -H `which fasm` `which as` `which nasm`|awk '{ print $8 ": " $5 }'
/usr/bin/fasm: 72K
/usr/bin/as: 278K
/usr/bin/nasm: 584K

>>8
 Use the 16bit option. It will compile down to 22bytes(its a .COM).



_________________________
orbis terrarum delenda est
 http://xs135.xs.to/xs135/09042/av922.jpg

>>8
OMG NASM IS BLOATED
BRB WRITING ANONIX KERNAL

>>4
Oedipus.

>>8
What? GNU not bloated?

Let's take a look behind the scenes:

% ldd `which nasm`
        linux-vdso.so.1 =>  (0x00007fffab1fe000)
        libc.so.6 => /lib/libc.so.6 (0x00007f70a2bda000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f70a2f19000)
% ldd `which as`
        linux-vdso.so.1 =>  (0x00007fff58ffd000)
        libopcodes-2.18.so => /usr/lib64/binutils/x86_64-pc-linux-gnu/2.18/libopcodes-2.18.so (0x00007fcf50ac1000)
        libbfd-2.18.so => /usr/lib64/binutils/x86_64-pc-linux-gnu/2.18/libbfd-2.18.so (0x00007fcf507ec000)
        libc.so.6 => /lib/libc.so.6 (0x00007fcf504ad000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fcf50d15000)
% ll /usr/lib64/binutils/x86_64-pc-linux-gnu/2.18/libbfd-2.18.so /usr/lib64/binutils/x86_64-pc-linux-gnu/2.18/libopcodes-2.18.so|cut -d\  -f5
839K
336K

I thought so.

Awful thread.

When I make graphics, I don't want eight extra GIGABYTES of worthless
proprietary algorithms and bloated filters! I just want a picture!!
Not a "photoshop".  Not a "gimp".  Those aren't even WORDS!!!! MS PAINT!
MS PAINT! MS PAINT IS THE STANDARD!!!

gimp (n) - A narrow flat braid or rounded cord of fabric used for trimming.

Newer Posts

---

Don't change these.

Name:		Email:
Entire Thread Thread List