> I hadn't heard of the Pinenote before looking at your comment, so I looked at the site and saw some things that made it seem unfit for purpose as an ereader. I made my comment because I was interested in hearing your impressions if you were using it as a daily driver.
I updated my original comment to include some more personal blogs with first-hand accounts. They're not mine but worth linking to for others!
I haven't bought a PineNote yet, but it's probably going to be my choice for that size of Tablet. I opted for a Xteink instead and have been very happy with it.
> Personally I view stuff like this as a nice-to-have, not a must-have. If it means I can't have an interface where I can buy books and then download them to my ereader, or I can't have an iphone app where I can read books and have my progress synced between my ereader and my phone, or it's unstable, or the battery life isn't good, then I would rather go with the Kobo. I understand that different people have different priorities, but those are mine. Stuff like this is why I'm interested in hearing more detailed information about what exactly the tradeoffs are for going with something like the Pinenote.
I agree that there are certainly a lot of sharp edges to less supported platforms. I just think I'd rather get a Boox (and deal with Android/Graphene) or PineNote over the Kobo over the long term. Then again, my usage of very simple -- maybe I just don't read as much/depend as much on the ereader to the extent that others do!
> I think you can still sideload KOReader on them, but that's a shame that they're making it harder to replace the stock OS entirely. I hadn't heard about that prior to now so thanks for bringing that up. I only have a Sage I bought a few years ago.
Ah yes, AFAICT what you're saying is correct -- sideloading apps is not an issue as far as I could find, it was just the inability to have custom firmware/OS.
I was very disappointed in this, and I generally see it as a step towards locking down that will only continue. Would love to be wrong though as I was very very convinced I wanted a Kobo Libra Color earlier).
People that are happy with the Kobos as they are (and the bundled software/services) I'm sure will be happy to keep buying though, I think the market is certainly big enough for that!
> More expensive and less out-of-the-box software, but straight to the point on device ownership/what kind of software you can run, fewer strings attached.
This note was in the original comment, did you read it? The fact that it is $400 (more expensive) and has less out of the box software is literally mentioned to alert people to that.
> The Kobos don't limit what you can do with them either, you can sideload alternative e-reader software like KOReader that improves on the built-in reader functionality.
This is patently false, the latest Kobo Libra Color is using secure boot which completely locks out custom development:
The point is to buy hardware that is built for you to freely modify and fully own, from the start.
My post was to make sure everyone knew the PineNote was an option, because I certainly did not know it until someone on HN made me aware.
Could you maybe make your point more concrete? Are you attempting to completely dissuade people from using the PineNote because it may not be easy to side load apps to it on hacker news?. Obviously different people have different propensities to do hacking, and some may not be able to afford the PineNote due to how expensive it is, but it's not clear what the goal of your comment was.
If your goal was "invest in Kobo instead of PineNote", I disagree with that. I'm not interested in investing (whether money or time) in an ecosystem that is just going to rug pull me eventually, over nickels and dimes.
BTW for those who agree, another great option is XTeink -- very hackable, and I've bought one myself:
More expensive and less out-of-the-box software, but straight to the point on device ownership/what kind of software you can run, fewer strings attached.
This is a great point. Back when I was checking I think I was underwhelmed by the customization ecosystem for kobos but now I’m not sure what was stopping me/made me reconsider.
Upon further inspection there is also the Pine Note!
That’s a great question and something we’re going to have to figure out going forward on the JS side.
What I can say now is that the first version will probably be single threaded stack switching coroutines, and the model that seems to fit most naturally in my head is virtual threads mapping to some worker thread n in a premade pool.
This is awesome! How reliable are kindle jailbreaks/avoiding updates, etc?
Have opted for other devices like the xteink (or a boox in the future) due to what seemed like a relatively small ecosystem around “aftermarket” kindle modifications.
The kindle would be a great option if it could be reliably jailbroken and loaded with custom software
That’s right — I’m assuming you mean OS threads when you write “actual threads”.
Stackless Coroutines are currently supported for p3, stackful coroutines AKA “virtual threads” are coming (which I assume is what you mean by green threads), and “actual threads” as in OS threads are not currently a goal for the ABI AFAIK —- would you mind explaining some uses you were thinking of?
It seems we're at a bit of a crossroads. It seems like the world both needs:
- Permissionless email (i.e. for agents, empowered users who can program now)
- Pervasive email allow listing
Wonder if these can both exist at the same time, i.e. having a "public" email that is read first by AI (let's imagine we're in a world where prompt injections weren't so possible) and heavily filtered, along with one that is private and allow-list gated (via some easier-than-gpg-to-use identity marker).
You can't have it all, forever -- the tech is there for anyone to fork and improve, build new businesses (!), inspect, etc. F/OSS is basically a miracle as-is.
If we compare the current state of the world to one in which they were acquired and then continued to put out more F/OSS, things look bad (which I assume is your implication). I choose to instead make the comparison to the world where we never see this tech and it stays proprietary. Sure, eventually someone in F/OSS might have gotten around to building this solution, but they pulled forward the future and we get to see and build on the result for free.
This is essentially a re-explanation of Neon’s architecture as a blog post.
Amazing that the Postgres ecosystem got this software for “free” (as in at least a basic version of it is F/OSS, IIRC there wasn’t any core bits held back), and the extremely engineer-heavy company got to make money, AND they got bought out in true acquisition style by a larger player that truly benefits from the tech.
The Postgres ecosystem is pretty unique in its ability to produce a “boring” stable product, innovate, stay F/OSS, and create financial outcomes for participants.
Wow HN really does have a problem with commenting on anything to do with Mozilla.
Anyway, awesome to see this from the team inside Mozilla — hope this can become a new revenue stream over the long term.
Really excited to see some tight integration with Firefox and Thunderbird in the future.
People are going to hate this, but if someday Mozilla expands to being a productivity suite I’d be pretty happy to give them my money. ProtonMail is doing it and I trust them as well.
I skimmed the code and it looks reasonable, but I have to assume it’d vibe coded (which doesn’t mean it’s bad).