Supertonic 3 is pretty amazing too. I’ve got time to first sound down to well under a second by streaming chunks and stitching together from CPU with goonx (non c-go onnx) - happy to upload model if any go devs interested.
moved to kobo (the nice one with colour screen) with calibre web running behind a cloudflare tunnel, getting books direct through smallest publishers/authors. Adds the tiniest bit of friction in book acquisition but reading experience, battery life, everything else shits on my kindle experience (and I’ve owned every one).
What software do you use on the device itself? I recently got a Kobo Clara HD, but software support seems to be a big issue.
On one hand, there's folks using the vendor's OS, which looks like an abandoned custom-made Linux distro, where compiling anything is a nightmare. It's not really made to be hackable, but just to read books purchased via their partners.
OTOH, there's a near-mainline kernel, which works nicely, and hacking on the device becomes much nicer, but e-reader-oriented software seems to commonly rely on kernel APIs only present in the vendor's abandoned fork, and won't work on a more mainline Linux. But this is a great target for actually developing stuff.
I'm tempted to write my own minimal e-reader-focused DE, but honestly, I don't want another project on my hands and would like to use something that's already there.
I want to use it mostly to offload reading web articles (or RFCs) onto it, so I want a simple pipeline on my desktop that renders a web page into something e-reader friendly, and then sends it to the reader. I'm using something like Mozilla's readability to extract the article itself.
I don't intend to use the e-reader to displace paper books, I have no quarrel with those. I mostly want to displace "sitting on my desk, reading a multi-page article on a computer monitor".
It's custom software but still pretty dumb, doing most of its work in the background.
Please mention that color e-ink has significantly lower contrast than black and white. I thought I did enough research, but was bitten by this caveat- I would trade basically any feature for more contrast.
On the plus side, with your setup, you can have the lowest friction ebook experience possible on planet Earth by installing koreader, and then the z-library plugin.
Color (Kaleido) eInk screens can't show pure white, because the color filter is in the way. That makes the display significantly darker, and negates the entire purpose of eInk.
I sold my color eInk device after trying it for two days, and went back to B&W.
There are some tablets with RLCD screens that have decent colors and contrast (not quite as good as 300dpi eink, but close, with color and fast updates), but most w/color screens lack proper frontlights for some reason, and they all run android so it's a bit of a mixed bag compared to a proper Kobo/Pocketbook/Linux eink tablet, but having a decent browser on a reflective display without having to cross-compile for 32-bit ARM linux is great.
The antigravity teamwork-preview doesn't work for me -- upgraded to ultra, installed antigravity 2, ran teamwork-preview, keeps failing: "You have exhausted your capacity on this model. Your quota will reset after 0s."
I’m a huge elixir fan, but imho it doesn’t solve durable execution out of the box which is a major problem that often gets swept under the rug by BEAM fanboys. Because ETS and supervision trees don’t play well with deployment via restart, you’ve got to write some level of execution state to relational database or files. You can choose persistent ETS, mnesia, etc, (which have their own tradeoffs and come with some kind of gnarley data-loss scenarios in deep documentation). But, whatever you choose, in my experience you will need to spend a fair amount of time considering how your processes are going to survive restarts. Alternatively, Oban is nice, but it’s a heavy layer that makes control flow more complex to follow. And, yes you can roll your own hot code deploy and run in persistent VMs/bare metal and be a true BEAM native, but it’s not easy out of the box and comes with its own set of foot guns. If I’m missing something, I would love for someone to explain to me how to do things better, as I find this to be a big pain point whenever I pick up elixir. I want to use the beautiful primitives, but I feel I’m always fighting durable execution in the event of a server restart. I wish a temporal.io client or something with similar guarantees was baked into the lang/frameworks.
The good thing about those, IMO, is that they’re leveraging everything that’s already in BEAM/OTP, so there’s no need to reinvent the harder parts. They “only” add some extra features (like persistence of processes/GenServers between restarts) and higher-level abstraction APIs.
Spot on. BEAM is great at surviving process crashes, but if the whole cluster goes down or you redeploy, that in-memory state evaporates. It's not magic. For agents that might hang around for days, pure Elixir isn't enough, you still need a persistence layer. The ecosystem is catching up (Oban Pro, FLAME), but in reality, we're still building hybrids: fast actors for active chats and a good old DB for history and long-running processes
- A phoenix/ecto inspired batteries included framework for Golang. Uses data-star for real time bindings (can do live view like things but my personal favorite is just real time form validation out of the box). Hot reload with templ, daisy, and tailwind (no npm required). Routes file provides metadata on routes so type safe route helpers are generated for views and handlers.
reply