←back to thread

Hosting a website on a disposable vape

(bogdanthegeek.github.io)
1386 points BogdanTheGeek | 7 comments | | HN request time: 0.427s | source | bottom
Show context
x187463 ◴[] No.45249934[source]
Re-using this sort of device is super cool. I can imagine a post-apocalyptic scenario where a city is run on a hodgepodge of random computing devices like this.

I will say, though, disposable vapes with microcontrollers inside (and even full games and screens from recent reporting) are an egregious source of e-waste. Many layers of stupid are present here.

replies(11): >>45250057 #>>45250161 #>>45250275 #>>45250310 #>>45250322 #>>45250541 #>>45250673 #>>45251121 #>>45252055 #>>45252398 #>>45254937 #
kilroy123 ◴[] No.45250322[source]
Makes me think of these:

https://duskos.org https://collapseos.org

replies(2): >>45250998 #>>45251137 #
amelius ◴[] No.45251137[source]
How do I build a 6502 from just the elements?
replies(1): >>45251268 #
vdupras ◴[] No.45251268[source]
You begin by making a pen "from just the elements", then work your way up to there.

In other words, it's a huge challenge, but 6502 is closer, in complexity, to the pen than to the, say, AMD Ryzen.

But the primary idea behind Collapse OS isn't to run from 6502 built from the ground up (although it partly is), but to run from frankenstein cobbled up machines made from scavenged parts.

replies(3): >>45251639 #>>45251649 #>>45255751 #
mm263 ◴[] No.45251649[source]
If I scavenge any machine today, how likely would I be to find a 6502 vs something more modern? I’d argue that some people might have a NES at home and one could get a 2A03 from it, but in a hypothetical scenario where I need to scavenge some computational power, I’d find an Android phone
replies(2): >>45251800 #>>45252209 #
1. tlavoie ◴[] No.45252209[source]
DuskOS apparently runs on ARM, so one of these vape boards running FORTH would likely feel very roomy indeed.
replies(2): >>45252389 #>>45252598 #
2. vdupras ◴[] No.45252389[source]
Even for a Forth, 3KB of RAM is rather tight. Dusk OS intentionally de-prioritize compactness and it couldn't run on that amount of RAM. It can get a C compiler loaded in about 100KB of RAM, but 3? not enough to boot.
replies(1): >>45252888 #
3. BogdanTheGeek ◴[] No.45252598[source]
I have ported zForth to an even weaker chip, the famous 10c risc-v micro ch32v003 (16k flash, 2k ram) so no issue running on this: https://github.com/BogdanTheGeek/zForth
replies(1): >>45257232 #
4. tlavoie ◴[] No.45252888[source]
OK, so we'd play with zForth then, as BogdanTheGeek notes here. That reminds me, I have a Scamp board sitting here on my desk that I really should play with more. https://udamonic.com/what-is-a-scamp.html
replies(1): >>45253726 #
5. vdupras ◴[] No.45253726{3}[source]
"we'd", you mean in a collapse scenario? Forths are, by nature, "collapse-friendly", but one particularity with Collapse OS and Dusk OS is that they are fully self-hosted. This includes the tools necessary to improve upon themselves.

From a quick glance, it looks like BogdanTheGeek's Forth is written in C, which means that it's not self-hosted. If all you have is that disposable vape with this Forth in it, you lack the tools to deploy it on another machine or to improve it in place.

One could also port Collapse OS to ARM. I guess it wouldn't be a very big effort.

replies(1): >>45254015 #
6. tlavoie ◴[] No.45254015{4}[source]
Good points! Really, I should start with learning Forth on the devices I have first, before getting to concerned about others. ARM does seem like a useful target though, given that they're basically everywhere these days.
7. romforth ◴[] No.45257232[source]
Allow me to brag about romforth (https://github.com/romforth/romforth) which I ported to the "3c" Padauk and can run on really small rom/ram microcontrollers. Caveats: - tested only on an emulator SDCC/ucsim_pdk, not on real hardware - given how small the ram is, there is no user dictionary but new words can be defined and tested using what the Forth folks refer to as "umbilical hosting".