As a ultra noob in the art of knotting, I liked this when I stumbled over it a few weeks back. I agree that for newbies it would be even more instructive with smoother flows, I guess they're held back by the animations being photos and not, well, animations.
I also have read their backstory/naming thing [1] several times but I still don't quite get it. I first thought they were related to the historical Grog, but that was a misunderstanding. I think.
Meta: This is a very messy title, it should just be "The minichord: a pocket-sized musical instrument" or something like that. We have the github info in the auto-generated blurb right after the title, after all. Thanks.
I couldn't quickly find a comparison table or similar, to see what parts of Python are not supported by MicroPython. So I asked an LLM and it listed quite a substantial amount of modules of the standard library, that are a shame not to have. No logging module? No multiprocessing? No json, no xml? And the list goes on, including many very useful modules. One can probably somehow get by, installing third party libraries, but then what is the point of being MicroPython, if you need to install tons of libraries to do basic things like reading a JSON file? And as I am currently working on a tkinter application, tkinter being on the list also makes me think: "What a pity, cannot port that to MicroPython."
This is just my first superficial look at it and it is also based on LLM info, which doesn't have to be correct, but if it is correct, then it feels a little disappointing.
Perhaps for more serious app development, it would be good to have real Python and interface with MicroPython for the hardware controlling stuff.
Specifically: JSON is built-in, logging is available. There's no multiprocessing (it is designed for a micro, after-all - and note that thread is available on some ports), no built-in XML lib.
Be sure to check micropython-lib, the MicroPython Awesome List and mim for others.
MicroPython is primarily for embedddd devices with on the order of 1 MB of RAM and FLASH. And applications which makes sense with such constraints. If you have hundreds of MB of RAM, better to just use CPython.
Just a few months back I worked in embedded development on a project and there was a physical dongle to unlock the compiler, which was surprising during on-boarding as I've spent years doing commercial embedded work relying on GCC. :)
“The historical significance of JUMPSEAT cannot be understated,” said Dr. James Outzen, NRO director of the Center for the Study of National Reconnaissance.
I'm no native speaker but that is backwards, right? Shouldn't it be overstated if it was a success?
Native here: you’re correct it’s a weird sentence and turn of phrase in English.
That said, can/cannot is a flexible word in English and we could take it to mean “Anyone discussing the significance of JUMPSEAT [accurately] [should never] understate it.”
But I think he meant overstate in this case. Or maybe he hated JUMPSEAT, thought it sucked and put that right out there in the press release.
I love seeing new games for "retro" machines, it's awesome that people keep pouring time and love into them after all these years.
I'm not super familiar with 8-bit Atari machines, and found the designation "classic unmodified 8-bit ATARI XL/XE" a bit imprecise. Tried looking up specs on Wikipedia [1] but was unsure what to settle on. Perhaps the original 1200XL would match? Or the 800XL which seems to improve on the 1200XL even though the naming suggests the opposite ... Or the 65XE, or both then I guess since the latter is compatible with the 800XL, but in an updated case?
There are a great many modern modifications available for the 8-bit Ataris, many of them from Poland where the machines saw good sales quite late compared to the US.
Using modern electronics (FPGAs etc.), processors, and high-density memories, you can imagine the processing, graphics, and I/O improvements that can be made for relatively low cost.
Many hobbyist machines at this point are highly modified, with much new software taking advantage of the new features, so specifying "classic unmodified" pretty much means a system into which you could have slapped a ROM cartridge purchased at your local computer store back in the day. XL/XE sounds like it rules out the original 800 and 400 models.
> I love seeing new games for "retro" machines, it's awesome that people keep pouring time and love into them after all these years.
Same here, which is why I have more games to play than I care on my lifetime, without bothering with whatever subscription services, or games measured in GB/TB.
[1]: https://en.wikipedia.org/wiki/Mars_trilogy