←back to thread

172 points fsflover | 2 comments | | HN request time: 0.403s | source
Show context
ge96 ◴[] No.45054041[source]
Kind of sad, I had both PP and PPP

When they were "new" the tech was old already and then the lack of drivers for the camera for example which I can't talk, I'm not a driver developer. I thought it would make me get into developing drivers but I never did.

Or writing Qt/C++ apps vs. cross platform/web that I was used to.

For some reason I was obsessed with the thought of Dex/your phone being a computer if connected to a big monitor, it was cool using VS Code on the PPP but there would be problems. The external monitor I think was capped to 1920x1080 (if connected to a 1440P display a huge chunk was just static)

I had my fun with it

I was interested in the Pine 64 eInk tablet but that seemed to not be in stock at the time. I had the Remarkable 2 at one point, I want to get it again.

edit: looks like the PineNote is in stock right now

my consumer brain is getting tickled, might get a PineNote, what I liked about the RM2 is I didn't have to charge it for like a month was crazy, unfortunately PineNote doesn't seem to have that, and no tilt support on pen but ehhh. I don't know if RM forces you to have a subscription now, I didn't have it on mine when I got it in like 2022.

replies(4): >>45054158 #>>45055323 #>>45057488 #>>45071523 #
cosmic_cheese ◴[] No.45054158[source]
Yeah for these kinds of things to work the hardware has to be at least somewhat competitive and the overall device reasonably usable. It doesn’t need to be a flagship or anything, just relatively recent, and the experience doesn’t have to be perfect, just actually suitable as a daily driver. That’s what gets people interested, inspires devs to contribute and fill app gaps. This kicks off a virtuous cycle where less technical family of those devs see the device and want to try it, which in turn creates more demand for apps pulling more dev interest and so on and so forth.

It’s critical to be good enough to clear that initial hurdle, though. Without that, the device is relegated to the most curious of tinkerers which just isn’t sustainable.

As far as dev experience goes, from my limited dabbling I think GTK+Adwaita might actually be overall nicer for mobile development than Qt, due to furnishment of a full set of widgets without having to pull in anything else, as well as bindings to way more languages. It’s considerably more comparable to UIKit and Android Framework at the very least.

replies(2): >>45055651 #>>45058998 #
1. codedokode ◴[] No.45058998[source]
GTK uses a C emulation of OOP, and the code gets very verbose (and functions have names like "gtk_event_controller_get_current_event_device", so you cannotfit more than one call in a line). I do not recommend to use GTK (or anything from Glib) with C, use bindings for a better language, and you save 2x-3x in code size.
replies(1): >>45059796 #
2. cosmic_cheese ◴[] No.45059796[source]
Makes a lot of sense and explains the proliferation of Vala and Rust among other languages in the GTK ecosystem.