Just a few quick notes regarding binaries:
- Binaries for Windows (native & .NET) are provided
- Binaries for DOS (real mode & DPMI) are provided
- The updated macOS & iOS versions will be available within a couple of days
With this done, I'll be focusing on documentation, examples, and getting it packaged for more systems. (Looking at FreeBSD ports & NetBSD pkgsrc currently)
Update on #retro #forth for #dos: I committed the VM+IO source to the repository (as `interfaces/dos/repl.c`) and added a few lines to shrink the string buffers, so there's now 1927 cells free on startup. Not a lot of space, but there's only so much that can be done when running a 32-bit VM on a 16-bit host.
The "write it yourself" mantra applies to when you're learning and/or developing something new. Once you've written it, you are free to re-use code YOU'VE written in a subsequent project, since:
1. You're in the ideal position to understand its tradeoffs, and,
2. You can fix and refine it effortlessly as needed.
@ajroach42 I think the net and the general availability might be a blessing and a curse. On the one side I get powerful software on my machine at the blink of an eye.
On the other hand comming up with your own solutions is discouraged, mainly by people shouting 'don't reinvent the wheel!'
That's one of the reasons I keep telling people to code it yourself.
I've managed to build a working(*) #retro 12 for 16-bit 8086. It fits (barely) into a single 64K memory segment. It's also *very* slow, as one might expect for a 32-bit virtual machine running on a 16-bit architecture..
The next step is to implement a virtual memory system so I can have more than 10k cells (the standard image + input buffer uses 8,575 cells).
(*) strings aren't working fully due to insufficient space for the rotating temp string buffers.
As someone who's been using computers since the early 1980s I can say for a fact that computers ARE harder. What's changed are User Interfaces in order to make things APPEAR easier, which doesn't really work for many of us much of the time. Because of this simplicity overlay it's gotten more complex to determine actual problems and solve them well. I truly believe this is intentional, meant to create a new industry--User Support--and take power away from individuals.
http://forthworks.com/retro/download/RETRO-DOS.ZIP or gopher://forthworks.com/9/retro/download/RETRO-DOS.ZIP
Another command line gopher client, this one based on Python 3 instead of C (that'd be cgo):
Please join the discussion at https://github.com/tootsuite/mastodon/issues/6072
Boost and if you have a GitHub account, get in there and at least leave emoji reactions. I don't want to bother development unless this is a thing a lot of folks care about. ^_^
A few brief notes:
- Written in Python 3 using mastodon.py
- Only tested under inetd on a FreeBSD 11 box
- This is *very* minimal; it provides selectors for posting toots, reading the home, local, federated timelines, and reading notifications
- ISC license
I'll be releasing the iOS interface to this later this month.