North star coffee, then you need a z80,cpm and s100 bus start in the morning.
alcinnz
boosted
I wanted to find a small niche hobby coding project that approximately nobody would care about.
I'm tooting about it now, and I don't expect you to care.
I want to use m68k-linux-gnu-as cross-assembler, but it doesn't support the Motorola syntax the original Amiga tools did.
How hard can it be to write a preprocessor that converts vasm mot syntax module compatible assembly to GNU as?!
Turns out, less trivial than I thought.
I wanted to find a small niche hobby coding project that approximately nobody would care about.
I'm tooting about it now, and I don't expect you to care.
I want to use m68k-linux-gnu-as cross-assembler, but it doesn't support the Motorola syntax the original Amiga tools did.
How hard can it be to write a preprocessor that converts vasm mot syntax module compatible assembly to GNU as?!
Turns out, less trivial than I thought.
alcinnz
boosted
Pretty good #C64 hardware rundown/comparison for the uninitiated.
Pretty good #C64 hardware rundown/comparison for the uninitiated.
alcinnz
boosted
Me, looking at the 8008/8080/Z80 instruction sets: "bah, why do you need conditional calls and conditional returns when the conditional jumps are already more than enough?"
Me, coding in 68000: "I really with I had conditional calls and conditional returns, relying on conditional jumps makes the code harder to read than necessary."
I am never happy.
Me, looking at the 8008/8080/Z80 instruction sets: "bah, why do you need conditional calls and conditional returns when the conditional jumps are already more than enough?"
Me, coding in 68000: "I really with I had conditional calls and conditional returns, relying on conditional jumps makes the code harder to read than necessary."
I am never happy.
alcinnz
boosted
In my little world of #RetroComputing, I have stumbled across minor issues in some of the tools that I use.
I've had two cases so far where maintainers very quickly took my suggestion and made it available in their main branch. I've also had one where I haven't heard back from the maintainer, i.e. where I'm going to need to maintain my own fork (for #RiscV compatibility). And that's OK. Beyond being glad that I got help, I'm glad that the original authors allow me also to do the work myself.
alcinnz
boosted
Do you like internet #ads? No?
What about #ads from the 90s and 2000s in #GIF format? Yes? The you're in luck, because this site has +800 of them for your personal enjoyment!
#RetroWeb #RetroComputing #SmallWeb#IndieWeb #90sInternet#90sWeb
Do you like internet #ads? No?
What about #ads from the 90s and 2000s in #GIF format? Yes? The you're in luck, because this site has +800 of them for your personal enjoyment!
#RetroWeb #RetroComputing #SmallWeb#IndieWeb #90sInternet#90sWeb
A situation that appears more and more, though, is that "with great power comes great responsibility." When using Free Software, you might only have yourself to rely on to maintain the software you use.
Don't get me wrong, most maintainers will go through great lengths to help their users, but that's from being kind and decent human beings, not from being contractually required to.
When using Free Software, it's also "free as in puppy": no upfront cost, but maintainance is on you.
In my little world of #RetroComputing, I have stumbled across minor issues in some of the tools that I use.
I've had two cases so far where maintainers very quickly took my suggestion and made it available in their main branch. I've also had one where I haven't heard back from the maintainer, i.e. where I'm going to need to maintain my own fork (for #RiscV compatibility). And that's OK. Beyond being glad that I got help, I'm glad that the original authors allow me also to do the work myself.