If your code can't fit on a 1.44MB Floppy Disk it belongs

>>60701536
Turbo pascal needed two discs.

No because we're no longer limited to the storage space of a floppy disk

I had to slim a program down from 9k compiled to under 7 to get it to fit on my robot arm.

File: IMG_20170504_165208.jpg (101KB, 684x788px) Image search: [Google]

101KB, 684x788px

>>60701536
What does the save icon have to do with your statement?

>>60701536
The code fits, but the data sure as hell doesn't.

>>60701536
Unless it's something for multiple architectures or large for good reasons, yeah sure. I want the 100MB JS framework meme to stop.

>>60701536
Does everything required to get the game running count, too? Because most games, even ones written for DOS using Allegro or something, won't fit otherwise.

Modern applications are simply more complex, and floppies aren't an efficient storage medium. I mean shit that one only has room for 9 lines, tops.

>>60701690
Complex is just another word for bloated

File: 5.jpg (372KB, 900x720px) Image search: [Google]

372KB, 900x720px

>>60701807
Pro-Ana Programmer.

>>60701536
Whosoever said this is a fucking retard.

>>60701536
Floppy disks are inferior trash, why do you think they are obsolete?

Still trying to optimise your code is never a bad thing. If you can get it to below 1.44MB that's not a bad thing.

But are you really going to be a be able to store something with complex physics sim on a 1.44MB floppy disk?

>>60701905
To be fair I wouldn't mind seeing something looks like a floppy disk mak a major come back that'd be fine. I think right now the only reason to use them is to store security info and encrypt it.

Most mongoloids can't open the fucker on their machine, most wouldn't know how to start decrypting it. And more importantly for thieving or jewey dipshits few would even think something important is on a floppy.

Obsolete tech belongs in the trash.