Vertigo

@vertigo
496 Followers
83 Following
17.6K Posts

Favorite languages in no particular order: #Forth, Common #Lisp, #Python, #Asm, #APL, #J. Creator of Ascetic Programming style, and the VIBE screen editor.

#RISCV hardware developer (KCP53000, #Kestrel3). #nmigen.

I block bots unconditionally; nothing personal. DEPRECATED: My new account is at @vertigo #nobot

Kestrel Computer Projecthttp://chiselapp.com/user/kc5tja/repository/kestrel-3/index
Amateur RadioGeneral; KC5TJA/6
FurryBlack Dragon
PronounsHe/Him/Whatever

The hat on this dragon is whatever you want it to be. Follow your dreams

pontifical, Avignon ca. 1330-1340

Tours, Bibliothèque municipale, ms. Diocèse 8, fol. 59r

Source: discardingimages.tumblr.com

#art #Mastoart #creativetoot #dragon

I know I would be excited about a computer like @vertigo 's future Kestrel 3 or even the new ZX Spectrum, or a Hacktari.

But this industrial thing by a massive evil corporation turns me off a lot.

@clacke @lupyuen Update to previous message: I now prefer @vertigo instead of this account. You'll find I'm much more active there. Thanks!

@wilfredh I'm skeptical that compilers are smart enough to convert sequential code into their event-driven equivalents in all cases. The author is right; the event-driven nature of an API needs to be architectural.

What we're seeing in blog posts like this is Unix finally admitting that VMS was right all along.

@thamesynne @mdhughes @djsundog Oh, and before I forget, @crc 's RetroForth environment as well.
@thamesynne @mdhughes @djsundog This is *literally* the premise behind both the original Tripos/BCPL programming environment, as well as the IBM OS/400 operating system environment.

Jetstream is the Walmart brand name for a line of cheap Chinese wifi base-station/routers; other popular, cheap brands like Wavlink and Winstars appear to come from the same manufacturer and they all share a grave security vulnerability: a powerful back-door.

1/

#tokyocameraclub
symbol of japan
How do we help this teenage comrade

@wilfredh """Instead of a flow of code that issues syscalls when needed, that have to think about whether or not a file is ready, they naturally become an event-loop that constantly add things to a shared buffer, deals with the previous entries that completed, rinse, repeat."""

And, Amiga developers the world over read this and ask, "What took you so long?"