Alaska’s land is pretty rugged and hard to build on. It would be interesting to hear from someone who works in the industry why the Northern Interior states like Montana, North Dakota, and Minnesota have fewer data center buildouts than Texas though.
Sure, but it seems very reasonable to expect some co-hosting of latency sensitive tasks, especially with some low hanging thin client fruit, like cloud gaming and the like. I've been very happy not burning a thousand watts of $0.45/kWh power locally, for my AC to force out of the house, to run blender.
They’re also just more user friendly in general. I have a nearly decade old Kobo that still serves its purpose well and I love how it shows up as a mass storage device when plugged into my computer. No clunky management software (Calibre may be functional, but its UI is godawful) or file conversions required, you just manage plain old epubs in your file browser. That functionality can’t randomly vanish one day, either (unlike e.g. Amazon’s email-to-Kindle service). It’s great.
As a side effect of its openness I’ve bought more books through the Kobo store than I would have otherwise. A perfect counter example is my Oculus Quest 2 which I go out of my way to not buy games from its associated marketplace on; as long as that device is hard-tethered to Facebook and its software, I’m better off as using it as a “dumb” headset with VR purchases going to PC marketplaces like Steam.
Kobo devices ship two different rendering engines: the obsolete, appallingly bad Adobe Reader Mobile SDK (RMSDK), and their own, bespoke, WebKit-based renderer. By default, files with an .epub extension are rendered with RMSDK. Consequently, you'll get all sorts of weird issues. Some of the ones I've encountered: I've had cover images not displaying in the library, misbehaving internal links (footnotes), inability to override typefaces/text size.
Easy fix: rename the file to .kepub.epub[0].
Slightly more involved fix: run the file through Kepubify[1] first. This tool makes further tweaks to the books to enable a few other features, like remaining read time estimation.
I had no idea! I'd switched from Kindle to Boox because Boox runs Android, which is more hackable, but if Kobo supports SSH, I'll have to give it another look!
I have a Poke since 2022 because amazon deleted my library from my Paperwhite. Same functions, better format and I can buy my books directly via browser from Kobo. No more perpetual airplane mode. Also, tons of formats, not limited to awz or epub.
I've had a Boox Page for about two years now as a Kindle Oasis replacement (current model is Boox Go 7 B&W). I get a bit more than a week of battery life typically which is good enough for me. And most valuable is using the same third party/self hosted apps for sync with my other devices. I've haven't used the Boox native store/reader even once.
reply