A Twitter Client For the Commodore 64
An anonymous reader writes "Johan Van den Brande has developed a Twitter client for the Commodore 64, allowing 140-character messages to be posted directly from this TV-connected 1982 home computer. This YouTube video shows how the Twitter client is — slowly! — loaded from a 5.25" floppy disk, how the latest Twitter messages are downloaded and shown on the TV screen, and how this tweet is posted. All that is needed is a C64, a TV, and a C64 Ethernet card. The Twitter client is implemented with the Contiki operating system, which otherwise is used for connecting tiny embedded systems to the Internet."
The drives your talking about are probably the 8050 quad density drive series (and the SFD-1001 - which was for the C64)) - 1 megabyte as I recall. Two problems with them - a) they were hard to buy and b) quad density disks are impossible to find (you can't even use pc high density disks with them). Still the one I saw demo'd was incredibly quick.
1541 used a 300 baud serial interface to the pc itself. In non burst mode programs took forever and a day to load or save - it wasn't entirely uncommon for a 15-20 minute load time.
Still it was light years faster than tape (which was less than 50 baud).
Yup - C64 was a complete hack, but you couldn't beat it for the price. For about 800-900 dollars you could have the PC and the 1541, where Apple ][ of the same vintage was 1500$+ with no accessories at all.
Not all companies back then developed directly on the C64 either.
There were dev tools for the PC for the C64 for example.
I don't think its cheating to use a bigger PC to develop a complex app for a smaller machine ;).
The C64 vs. Spectrum slugfests on usenet are legendary, and used to happen once or twice a year. And they were always hilarious! I mean, we're all grown ups with the wit of a child, and nobody is stupid there - it's really done for the fun of it. It does get deeply technical at times, but the humor is always present.
Slashdot has nothing on those long-winded usenet threads where we cudgel each other good!
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
If it makes you feel any better I've been loading it off of an SDHC card that is inside of a cartridge that emulates a 1541 disk drive.
http://www.1541ultimate.net/
On the contrary, I've used POV, probably the initial release and on that same Atari. Hell, I think I've even used DKBTrace. I've written my own GUI-less raytracers as well. It's kind of hard to do a magazine layout with POV, or design packaging, or create a logo, or composite effects into video. I've moved on to professional tools and will never look back unless I have some very specific need that only POV can fill. For procedural graphics and scientific visualization, it can be great. It's wonderful for hobbyists on a budget, or those in love with raytracing and willing to get their hands dirty, or those who want to learn more about raytracing in general. For work in a production environment? Get real. It continues to make advances, but it's still ten years behind the curve, and completely unwieldy for most CGI tasks. I have a friend who loves POV, she does all her game graphics with it. It shows.
CLI video editing? You must be on the moon. You're certainly not an editor, unless your idea of editing is ripping DVDs. I cut my editing teeth on 3/4" U-matic tape. Then I moved up to a CMX, which is a computerized analog linear editing system with a text interface and dedicated console and computer controlled VTRs. Then I moved up to a traditional, computerized, timeline-based NLE with analog capture/playback, and then eventually digital I/O. Today I use a next-generation NLE which is much faster and much more efficient than any form of editing before it or currently available from other vendors. Without those advances, I'd still be working on the first film. When a film has 1000+ edits, with each of those edits being tweaked up to seven or eight times, and each of those shots selected from twenty times as much logged footage, you don't want to screw around. What I do today, and what I do to stay competitive, would be virtually impossible and utterly impractical without a GUI. Film is a visual medium. It makes no sense not to edit it in a visually way. Would you edit audio without speakers or ears? I'm sure SoX is a fine tool, probably great in a proper tool chain, but you're on goofy pills if you think it's any kind of substitute for Pro Tools. I doubt you'll find a single musician that uses SoX for anything but purely utilitarian purposes (as opposed to creative ones), and even then, I'm doubtful.
+0 Meh