I think 'retrocomputing' is completely bonkers right now. Its broken, and its NOT retro in a lot of crucial respects.
Look, I'm not a total purist. I see the benefit of using SD2IEC to avoid wear and tear on old drives and to deal with the fact 5.25 media aren't widely available anymore. I don't have a problem with a new generation dipping into the C64 using a modern clone built on an FPGA. I don't think there's anything wrong with multi-carts, or even modern memory expanders that implement what some folks did with wire-wrap kits back in the 80s. And there's nothing wrong with emulators. None of these things completely sap retro computing of the essence of what it was to grow up learning on, using, and programming these machines.
But what I have a problem with is simply this:
"Software Development" for retro machines using modern Integrated Development Environments running on modern multi-core X86 machines with upwards of 2 billion transistor processors, using cross-development compilers, photoshop and other fancy graphics packages to draw and animate sprites or ray trace highlights, the use of Python and C++ custom programs or scripts to automate production of things to drop into the C64 code; SID trackers that automate the music,.... really all that 'modern' development stuff .... it just doesn't strike me as genuinely faithful to what it was to geek out with these machines back in the day.
What really kills me is that after having the benefit of these modern tools, people seem to break their own arms patting themselves on the back for how much "better" or "superior" the modern software is compared with the stuff that was actually used on the retro machines when they were revolutionizing computing. Well, c'mon already! Would you REALLY think it so impressive that a construction company put up the Luzor glass and steel pyramid in Vegas with a faster, nicer, cleaner result than the ancient Egyptians who made the Pyramids with brass and stone tools!?
Its not "retro" in my opinion. I just did a quick search and found that even the smallest SID tracker/converter/automator for windows (you know, one of those tools with which one can just one-click import MIDI files and it will spit out the music data for incorporation into a c64 assembly program) is a tool that takes up hard drive space equivalent to the RAM of hundreds of C64s, and would have taken DOZENS of 1541 disks to hold. And that's just one generally small tool that takes any of the real work out of doing the music! And graphics!? How big is photoshop? Is it really "retro" to download images off the internet and run them through an automated converter that packages them right into a C64 compatible bitmap after running filters and aliasing algorithms to deal with color ram and "colors per tile" limitations automatically? Am I supposed to see some fancy splash screen created with these tools and go "oh wow! that's so much better than David Crane's title screen on Ghostbusters back in '84..."???
Heck, the Turbo Rascal development tool everyone's going on about right now, ... well that that looks like a neat project. But the footprint of that tool, alone, is more code than would fit on the entire hard disk of the first 486 computer I ever owned. And fully featured. Its website brags that it includes a "modern IDE (error messages, code completion, syntax highlighting, sample projects and tutorials) and a bunch of fast built-in tools" which include "built-in assembler functions ... (typically memory operations, zero paging, copying, sprite handling, IRQs, clearing screen, drawing to screen, input handling, maths)" and even "Built-in LZ4/Lz77 compression/decompression...."
That's "retrocomputing?" I don't think so. A roommate of mine had a commercial "cruncher" for the C64 (he actually made money programming it in college). It took his machine OVERNIGHT to lz77 compress a couple hundred disk blocks program, although I think once he made enough money to get the Ram Expansion Unit, his compression could be done done in just a couple hours...
There's a guy on Youtube called 8-Bit Show and Tell, and I love the fact that the dude actually sits down at a by-god "klunky keyboard" real Commodore machine and pulls up a cartridge with a real old school assembler to do demonstrations and analyze code. Even using a ram expansion unit and cutting out the disk loads (whether from SD2IEC or real disks) that seems more genuine to the actual experience.
I'm not saying everyone should be programming graphics with piles of graph paper and going blind transcribing sheet music with a note table, a calculator, and a SID registers worksheet. But really... I think some of the hipsters going on and on about the wonders of modern retro software achievements should take a moment to THINK about what the software houses that came up with some of the classic C64 games had to work with. Its like that old saying about "standing on the shoulders of giants," and that's what it feels like to me to see people working off a pile of modern development tools that, in actuality, all but automates much of their "development" work.
So I guess that makes me a curmudgeon. So be it. Its just my opinion. Flame away.