Authoring Windows Applications In Assembly Language |
First off, Assembly Language can be beautiful and legible. Here are two GIF images of my own code. This is what I see when I am writing 100% pure Assembly Language for Windows: Sample #1 Sample #2. Am I sick? Perhaps. Am I a dinosaur destined for early extinction? Yeah, probably. But I truly love programming. It's what I do. It fulfills me and sustains me . . . and I'm never in a hurry to "just be done with it." I can't stand sloppiness in my work, so for me that means writing the smallest, tightest, fastest, most economical computer programs possible. And THAT means authoring Windows applications in Assembly Language.
Though the rest of the world may argue that they're more "productive" (when measured by hard disk space consumed per second), I stand by the principle that: "Small Is Beautiful".
Sure, I think so. Don't you? When I began the development of the first Windows application I'd ever created, ChromaZone, I was determined not to let the fact that I was writing for Windows keep me from creating really great software. And frankly, I just don't consider a utility program that's 4 megabytes big, and contains all sorts of files that the author didn't create, to be "really great software". Do you? So I needed to figure out how to write Windows Applications in Assembly Language. (Just as I had created SpinRite and all prior products in my life.) Well, I did that, and ChromaZone became a testament to what one guy who really cares about quality can produce.
Anyway ... ChromaZone is 16-bit Windows Assembly Language Technology. But before I had it completed the world had (pretty much unnecessarily) moved over to the "bigger must be better" 32-bit world of Windows 95. <<sigh>> So the next thing I did was to develop the technology to create modern state of the art 32-bit Windows Applications in the same 100% pure assembly language. That's where I am today. Every scrap of code I've written and offer on this web site was written in small, tight, lean and mean assembly language. You really can feel the difference. Here's another example ...
Many visitors to this site have asked if I could provide them with some help getting started authoring 32-bit Windows Applications in Assembly Language. So I created the "Small Is Beautiful" Starter Kit containing everything you'd need to assemble a full-function, state of the art 32-bit Windows Application in assembly language . . .
The file is 20k . . . Sorry it's so big, but I included all of the source code and header files, as well as a copy of the finished SIB.EXE so you could see the result even if you didn't have the other required assembly tools!
SIB.ZIP (20k) -- This zip file contains all of the files necessary to assemble a state of the art 32-bit Windows Application ... written in nothing but assembly language (it also contains the executable SIB.EXE app so that you can see what it looks like and browse the files even if you don't own a copy of Microsoft's Macro Assembler, MASM, or Linker). The App includes a toolbar with standard icons, tool tips, a status bar and common dialogs. And ... of course ... full source code for the entire project.
Even though Assembly Language programming seems to be a lost and dying art, the Web is chock full of interesting and useful resources. Here are some of the better goodies I've uncovered in my travels:
|
My personal home page | My resumé | Join my eMail system. |
Authoring Windows applications in assembly language. |
Gibson Research Corporation is owned and operated by Steve Gibson. The contents of this page are Copyright (c) 2024 Gibson Research Corporation. SpinRite, ShieldsUP, NanoProbe, and any other indicated trademarks are registered trademarks of Gibson Research Corporation, Laguna Hills, CA, USA. GRC's web and customer privacy policy. |
Last Edit: May 04, 2013 at 18:12 (4,178.30 days ago) | Viewed 41 times per day |