Incidentally, there exists now a functional analogue - complete with scavenged BB keyboard - sporting an ESP32 and a backlit screen in place of the Pi0 and memory LCD: the Liligo T-Deck. I don't need one, and I won't write software that runs on it, but I still want one because cute LoRa thing.
uC - ESP32/nrf Display - Memory LCD Keypad LoRa GPS LTE (optional) And yes - opensource firmware
Will happily drop the smartphone for such an above device.
I'd love to see it integrated with Arduino, so we could finally have easy to make, loadable, sharable apps on small devices.
i think the display is fucking awesome
just. not for this
for applications where its lack of backlight and grayscale mean you get a significantly longer battery life, or smaller battery, or no battery at all
being able to maintain the display on 50μW means you can run it off a cr2032 coin cell for 17 months
if you pair that with a cpu that's using some similar amount of power, probably due to being in a low-power deep-sleep mode 99+% of the time, you can get a month or two of interactive computing out of a coin cell. a sleeping esp32 is supposedly around 10μW, and at full speed it's about 200 32-bit mips at 1 watt. microcontrollers are typically an order of magnitude lower energy per instruction. ambiq's microcontrollers are two orders of magnitude lower, like 30 picojoules per instruction, so 100 μW should give you 3 mips
400×240 is half the screen resolution of the original macintosh, and the same as the vt100, though with a different aspect ratio
so you can get a vax in your pocket that runs off a coin cell for six months
that's motherfucking amazing
but that is not this product
which reminds me, i'm late for a pairing session on a jit compiler targeting the ambiq apollo3 ultra-low-power 48 megahertz cortex-m4f
I mentioned this last time as well; I hope someone makes this device like that. I would be happy with it. The apollo3 is nice and I enjoy working with it. I would implement a little OS for fun for a device like this if it existed.
On the form factor; a clamshell would be better.
my current plan is for my nascent jit compiler to implement paged virtual memory using bytecodes for paged-load-byte, paged-load-halfword, paged-load-word, paged-load-multiple, paged-store-byte, paged-store-halfword, paged-store-word, and paged-store-multiple, so that i can compile existing c to its bytecode instruction set; these will be implemented by calls to millicode subroutines
i think, and i might be wrong about this, that this will be sufficient to run things like libpng and pcc at useful speeds
if not, i might have to lean harder on making the jit compiler smart
i very much agree about the clamshell; that would also make it possible to include a keyboard big enough to touch-type on
its energy efficiency per instruction is not the best but is certainly acceptable
But I hate using it inside. I almost want like one of the gameboy worm lights adapted to this.
I also don’t regret buying this at all.
I think an "alpha" version cases should be basis for PCB, and both should co-develop. The "case will be available later" approach is only acceptable for benchtop prototypes.
When the device was announced some naysayer here on HN said, hey, that display is lame and the raspberry pi is a bad choice for battery applications, mcus with better options for deep sleep could make this a device with a battery life measured in days, not hours. And despite calling them a naysayer I’d say they are completely right.
I don’t regret buying it anyway, though.