Vertigo #$FF

HW: #ForthBox #vdc2 #vdcII #fpga.

SW: #Forth, Common #Lisp, #Python, #Asm, #APL, #J, #Rust.

Creator of the VIBE screen editor, Kestrel computers, and most recent project: ROSE. My code likely runs on your harddrives.

Burnout emeritus.

#nobot

Pronouns: He/Him preferred, but don't much care really.
Furry?: Yes; I am a black dragon named Vertigo. FA: https://www.furaffinity.net/user/vertigo2023
Website: https://www.falvotech.com
Favorite weakly/strongly-typed language?: Forth/Rust.

Public Key

npub1qss6q2f7fql07a2ftc8r8usfjcmkl6yq9hh87glx79tq8uukarssd9k4t3

NIP-05 Address

vertigo_at_hackers.town@momostr.pink

Profile Code

nprofile1qqsqggdq9ylys0hlw4y4ur3n7gyevdm0azqzmmnly0n0z4sr7wtw3cgckf2cu

Author Public Key

npub1qss6q2f7fql07a2ftc8r8usfjcmkl6yq9hh87glx79tq8uukarssd9k4t3

Show more details

Last Notes

2024-05-26 15:42:51

Remember folks, electroluminescent displays and "wires" are just light emitting capacitors.
My job is done here. Until next time...
(Skeletor runs away)

2024-05-23 01:40:52

- reply

All that being said, I still like the man-page formatting for reference documentation. You can have the most pristinely architected C code in the world, but if I can't wrap my head around the over-arching architecture and/or how pieces fit together, the first place I will go to will be the API documentation for help.

2024-05-22 00:22:31

- reply

I think the Wayland devs are on top of that game; users aren't necessary when your desktop is broken.

2024-05-18 17:11:02

- reply

That's true, I'm not sure why I didn't think of that.

2024-05-18 17:05:15

- reply

I would argue that every place gets dusty. I think the next best priority would be easy to clean. I was going to recommend hanging it from the ceiling, but then that impinges on the easy to clean priority. So, ultimately, not sure where a good spot would be.

2024-05-15 03:37:54

Not going to lie; defining $FF0000-$FFFFFF as "Z80 I/O Space" in the latest ForthBox emulator build is satisfying.
The limited register needs of the (new) KIA-II core fits nicely with the Z80's "256 byte" I/O space.
Maybe I can define some kind of "high level" storage controller standard that also takes up only two bytes of I/O space, so I can access DASD images in emulation as well as in real hardware.

2024-05-14 21:09:42

- reply

Good to know! I'll keep that on file for future reference.

2024-05-14 21:06:47

- reply

Makes sense. If I can get DIN 41612 connectors for a price that is competitive with pin headers, that's my preferred option.

2024-05-14 20:53:03

- reply

to be fair, that is one retailer that I did not price search on. I will need to consider them next time.

2024-05-14 20:41:03

- reply

people keep telling me that connectors with ultra cheap prices exist, if only I knew where to find them. Yet when I search on Mauser, Digikey, or even on Amazon, I've yet to find even a low spec connector for cheaper than $5, with $7 being about average for decent grade connectors (500 insertions or more).

2024-05-14 20:36:33

- reply

For me, is the insane cost. For a *decent* pair of mating connectors, I'm looking at $10-$15, *just* for the connectors.
I can get the same rigidity, lifetime, and applicability using ordinary pin headers (arranged in a 2xN configuration) for around $5.

2024-05-13 04:27:30

- reply

They sell tiki torches at most home improvement centers.
Just saying . . . 😏 😇 j/k

2024-05-10 21:01:00

Part of me wants to make another attempt at building a multitasking operating system.

2024-05-09 19:46:16

- reply

That's exactly why I coined the word Neo-retro.

2024-05-02 01:58:29

- reply

When you get to the point of a PCB that has a number of bodge wires on it, then congratulations, you've almost completed the first design! What you're feeling is, in my experience, perfectly normal.

2024-05-02 00:24:24

- reply

Ruby almost comes close. Almost.
That said, I still like plain-vanilla Smalltalk syntax the best.

2024-04-19 18:27:47

- reply

I guess this settles the age-old industry debate over which is better. The answer is 6502, if only by a technicality (it's still in active production).

2024-04-12 17:49:51

- reply

I think this is one of the reasons why GTK 1.0/2.0 has so thoroughly and completely obliterated its competition.

2024-04-11 23:50:29

Fuck you, Windows. <li> Git clone project in %UserProfile%\Desktop\git.</li><li> Build.</li><li> CMake vomits because of a path name too long error (even though path name is noticeably less than 260 characters in length).</li><li> Use Explorer to drag and drop the source folder to C:\G (G standing for Git, of course).</li><li> Gets to 98% complete, then <strong>EXPLORER COMPLAINS OF A DESTINATION PATH NAME TO LONG ERROR.</strong> For a file named <code>memory_map</code>.</li>
Yes.
That's fucking right.
C:\G\memory_map is too fucking long of a path name for Windows Desktop to handle when copying files.
Sigh.
I'm just going to crawl into a corner and fucking cry.

2024-04-08 05:45:01

- reply

Is there any evidence of it being under source control? It sounds like, if any was used at all, you were stuck using backups as a surrogate for proper branching.