New video! I'm showing two (and a half) ways of getting the TL866 EPROM programmer to work in Linux.
YouTube: https://youtu.be/_oacXhtaLsk
PeerTube: https://makertube.net/w/kKdacAjugvbd6cDGyUSZew
#TL866 #EPROM #EPROMProgrammer #XGecu #MiniPro #Linux #LinuxMint #Wine #VirtualBox #Tutorial #HowTo #EPROMBurner
I picked up a TI-83 calculator at a yard sale for $5. This is just a portable retro computer. It's got a #Z80 running at 6 MHz which you can program directly, or with #BASIC. 32K of RAM.
I'm pretty sure the calculator I used in high school was a TI-82, so this is a tiny bit of an upgrade of that, being that it directly supports programs written in ASM, transferred via USB from a computer. Can't wait to make some graphs and play Tetris on this thing, once I find some AAA batteries.
#RetroDev #TI
get it on flatpak. download the snap. install it on the appstream-compatible application store. your distro's appstream-compatible application store has it for you
@xChaos As it happens, @permacomputer @vidak _has_ been thinking along these lines: https://basiclang.solarpunk.au/d/5-minimal-text-editor-inside-the-lua-repl/13
@akkartik I am myself all for #solarpunk (see hashtag #solarbike on my instance...) but I am not sure how wise would be to start thinking in Basic again. Well, I spent way too many days of my teenage years programming in Basic... but I somehow don't feel like it was worth it.
I admit that interpreter that fits to 4 to 8 KB is amazing result. ZX Spectrum Basic was 16 KB. Basic interpreter for my Sharp MZ-800, which had to be loaded from cassette tape, unfortunately, was quite good, but it was around 40 KB big.
4 KB is really good. But the entire idea of line numbering is... well... it is not really comfortable way of thinking. Or editing. On the other hand, simple, non bloated software would be useful. For certain tasks, single task environment is more than enough. And of course, the shorter code can be much easier to understand and debug, than long code.
Some time ago, I was amazed by Tiny C compiler for POSIX systems (it was able to compile itself, of course). Having something like Tiny C for Z-80 would be nice. I really missed being to use C on Z-80. Of course, Z-80 systems are often missing filesystems at all... C without file I/O is kinda crippled, but still much more powerful than Basic.
The, well, basic idea of Basic, that integers (sometimes even floats) and strings must be enough for everybody, is more or less true: yes, lot of useful stuff can be done with integers and strings. But I would still prefer to use something like subset of Python syntax... which reminds me, that my current thought experiment (not really started as project yet) is subset of Python transpiler to C (should be able to compile itself too). I consider it kind of solarpunk too, although it is not using 70s technology, but should be pretty useful running of 80s highend or 90s mainstream.
Thank you interwebs, I knew that the new iPhone form factor reminded me of something.
Perhaps with the right compile optimisations, the Arduino Mega might indeed work for a permacomputer platform...
Because this text editor comes in at under 5KB...
#gameDev #devlog #NicCLIM #McCLIM Map editor #alphaRelease explainer part 2 ! Things begin to get crazy. #commonLisp #programming .
https://screwlisp.small-web.org/lispgames/nicclim-alpha-part-ii-lambdas/
Here I focus on writing normal lisp lambdas, and pasting them into the active map. Part 3 will be about picking up the lambdas and walking around the map, using them (i.e. to effect hextille game of life).
I look forward to your thoughts. We are in strange waters.
okay!
the text editor is beginning to croak back into life!
this is a 100-ish line text editor written in Altair BASIC
i have corrected and adapted the program to run on this Tiny BASIC, which runs on virtually every micro-controller board available in the west:
https://github.com/slviajero/tinybasic
what happens in this video is:
1. a text file is loaded at the INPUT prompt
2. the file is read into memory with "R"
3. the file paged through with "N"
4. individual lines for editing are listed with "L"
please see the following source code:
#permacomputing #retrocomputing #retro #basic #tinybasic #vintagecomputing #programming
https://spectra.video/w/qvxsFMhciScC1T2py3eFvB
going live for a bit, working on the text editor that is supposed to ship with the suite of tools with the people's permacomputer model 1.
#permacomputing #retrocomputing #tinybasic #6502 #z80 #livecoding #peertube #retro #emacs #retrogames #texteditor #programming
Uh oh, I seem to have made a #Lisp parser (or, rather, bicameral reader https://parentheticallyspeaking.org/articles/bicameral-not-homoiconic) just now. Who would've thought that it's that easy?
one of the things that's always bugged me a bit about the design of #fennel is that we use parentheses mostly for calls to functions/macros but they are also overloaded in binding context to allow binding to multiple values:
(let [input "whatever"
(v1 v2) (input:match "([aeiou]).*([aeiou])")]
(print :vowels v1 v2))
at a quick glance if you miss the context, it looks like the second line is a call to a v1 function where it's actually binding
I have been thinking it might be clearer if we bind to what looks like a "call" to values instead:
(let [input "whatever"
(values v1 v2) (input:match "([aeiou]).*([aeiou])")]
(print :vowels v1 v2))
it seems clearer and more consistent but I'm not sure it's worth the extra typing... thoughts?
With the spare GPIOs, you can do some crazy stuff with the PCB. Here's my Sharp 128x128 Memory LCD attached to the "extra" pins.
what up fuckers
i have a rust codebase i started like 7 years ago, for solving projecteuler problems, and i figure rust has had significant updates in that time
is there a better way to do this yet
In the process of porting over a bunch of old #supercollider code to #commonlisp. I'm blown away by how much cleaner, more compact and elegant the resulting code is. At least 50% reduction in the amount of lines, and it's a lot more readable...