coffeeenjoyer

Thanks for clarifying. It's interesting because most programmers I know who dream a lot about making stuff and are the "get things done" kind, they liked plumbing and glueing code together, and are now of course AI enjoyers...

If I understand correctly you'd much prefer your ideas to materialize, and be spared of the implementation effort.

So we should each do that then? You know, a few people dedicated their lives to invent and advance farming, electricity and perfect your sewage system... Maybe they should've sticked to foraging, hunting, and burying their crap in holes, so that others don't feel left behind... Or maybe I don't see the point the commenter was making.

Do you think mastering something is not a form of work, which usually results in advancing a field for the betterment of society? Just because one might enjoy that process more compared to maybe someone maintaing sewages, I don't see this as entitlement, but as merit and role fitness. No shade to sewage workers, I hope we all appreciate the work they do, and I hope they can have pride in what they do. Saying you don't have sympathy for anybody really losing their role in society/life is such a soulless take...

> I like building cool shit. Code sucks.

Do elaborate. I feel I'm getting this idea, but maybe not the same way you meant it...

> In this society, mastery (hyper-specialization) means that someone is picking up the slack for you in other areas of your life. This can be material need, psychological support, social connection, education access, and more

Citation needed...

Sounds like you are bitter you failed to achieve said mastery, and now are glad that those who did might be also getting pushed aside. If you think that success only depends on initial external factors and personal effort is something to be frowned upon and by striving for mastery you strain the society or drag others down with your lifestyle... man I don't know what to say to you...

If you think AI as currently lead by it's owners will equalize the field for the unfortunate ones... Well you might be right in some sense, but it might not be the way you envision it.

Thanks for clarifying and wish you all the best with the project! I'll see what watch I can get my hands on.

Wow, this looks pretty cool! It seems you have quite a few features going... The main reason I haven't gotten a smartwatch yet is because of privacy concerns. But now seems like a good time to experiment with one of the watches you support.

I also still dream of one day daily driving a Linux smartphone, but that feels a bit more unrealistic to me, as I have more expectations from a phone, like being able to use bank apps and having a good battery life. But for a smartwatch, which I only expect to show me some biometrics and pass notifications from my phone, this seems perfect.

On this note: aren't JavaScript and QML/Qt too heavy/bloated for a device so small? I expect them to constrain performance and battery life quite a bit, but I admit I don't have a clue and would love to be proven wrong...

> If you're a software engineer, you know not to depend on these kind of things, and there's no way to expect the library / framework author to reason about how people are using it.

Libraries and frameworks, I assume you meant open-source here, are a different thing.

A phone for which I paid a good amount of money, now doesn't let me use a different operating system anymore while maintaining the same (or arguably better) high level of security. Something which was possible thanks to the hard work of the GrapheneOS community, for the past ~looks at wikipedia~ 6 years... But that is no more, because the binary blobs cannot be forked like you would normally do in the case of FOSS libraries.

> What if someone else came up and said I'm using Pixel as a doorstop, and now that Pixel has a camera bump, it doesnt work anymore - I hate the company. Strange indeed.

Well luckily they can't physically alter the phone which I already own. If I didn't like the looks of the new Pixel, then I simply would not purchase it.

What Google can do though, is (indirectly) stop me from using it the way I envisioned before I bought this nice computing device, the way many others have been enjoying before me.

Anyway, I wasn't just talking about whether Google are wrong or not to do this. They understand what the consequences of their action are, and that just makes it shitty in my opinion. Am I upset? No, just disappointed.

> This is such a strange position. "I rely on an undocumented behavior, and I'm upset that things changed".

I view your position to put up a snarky defense based on weak analogies, for Google nonetheless, equally strange. "I'm on the internet where people can have different opinions, and I'm upset".

Judge me if you must, but the only reason I recently bought a Pixel was because of the intention on sticking GrapheneOS on it the second I got it out of the box. And it really worked great for me so far... Unless it's something to do with work, I don't (intentionally) touch anything that has to do with Google, as I dislike too many things about them.

And yes, they're not obligated to provide those binary blobs, but since they've been doing it for such a long while, not announcing it well in advance, like they do with the so many services they choose to discontinue, just adds to that list of things I dislike about them.

Yeah, yeah, it's a bit more work to publish those binaries and make sure they work. But they still kind of have to do that, for themselves. So I think it's fair to assume why they did it. Because they made a choice to take a small loss on the devices they would sell for the few GrapheneOS users, and cash in on the walled garden, data mining, ads serving, yada yada, whatever brings the extra money after the initial phone sale.

I assume most of that 2PB network traffic was not egress, right? Otherwise how did it "only" cost you $8k on Google Cloud? Even at a cost of 0.02$ per GB, which is usually a few times lower than the actual prices I could find there, that would still result in an invoice of about $40k...