They have a whole page dedicated to it [0]. To be fair, I mean it with a bit of sarcasm. How can you collect so much data and call it privacy. I definitely believe they do a better job than most companies though, even though I dislike how aggressively they are pushing sync features.
For anyone considering buying the Pixel Watch 3, please keep in mind that Pixel Watch 2 has some long-standing issues where the GPS completely cuts out during runs or walks.
Some users believe it to be a hardware issue but it's still unacknowledged by Google and the forum thread where people have been discussing it has just been locked recently. Just mentioning it for awareness and visibility.
Genuinely don’t understand why Google continues to produce these products and refuse to support them. Do they just know there’s a contingency of anti-apple users who will buy their devices regardless of extreme usability issues?
Apple has its own issues. And if I'm not mistaken, you need an iPhone to use an Apple watch, but you can use a Pixel watch with either an Android phone or an iPhone. Of course, Samsung, Garmin, and others also make campatible smart watches, so if I were in the market, I would certainly be comparing alternatives.
Oh, looks like you are right... that stinks. But at any rate, a non iPhone owner such as myself can't use an Apple Watch no matter how I feel about Apple.
I guess if I need a smartwatch, I'll dust off my old Garmin. Several other recomendations in this discussion I could look into too :).
It's not just the watches. Chromecast/GoogleTV devices have been missing an audio sync adjustment for ages. That feature is being asked about/requested all over the related discussion boards. Amazon Fire has it built in. Google doesn't care across so many product lines.
Anti-Apple users have plenty of places to get their hardware and firmware updates from, few users are going to look this deep into getting a device though.
FWIW, I had a Pixel Watch 2 with this issue every now and then in the first couple of months when it was brand new. I've not had this issue in 2024 essentially (fixed as part of monthly updates).
No WM at all is less nice, but can work. A bit over a decade ago, we shipped a kiosk/appliance that software-wise only had kernel, X, and firefox. All starting directly from /etc/inittab, something like this:
...where /etc/rc-∗ are few lines of shell that set up environment variables, and end with "exec chroot --userspec=... / /bin/firefox ..." - this way X and firefox run under same PIDs that sysvinit knows about, so they get restarted after a crash.
I was also looking for a successor to the PC Engines APUs and came across https://teklager.se/en/ that lists some possible alternatives that you might find interesting.
Personally I was looking to build a router so I ended up buying a fanless N100 based mini PC from Aliexpress (e.g.: search term is "N100 firewall appliance") and have been very satisfied with it so far (Proxmox homelab with OPNsense running as a VM).
I've been using VSCode with devcontainers and podman for a couple of months now and everything seems to work fine for me. Is there a particular issue you're hitting?
Honestly, it's been a long time; I should probably just try again. The last attempt I made was on windows before WSL2 existed. At the time I assumed the issue was with podman on HyperV/WSL.
For what it's worth, most (all?) the comparisons in that phoronix article [1] compare the performance of apps running under XWayland (in a Wayland session) versus an Xorg session. That's because most steam games use SDL 2 which still uses XWayland by default (the default has been changed in SDL 3 though [2]).
So using the data from that article to conclude that "[Xorg] still generally outperforms Wayland" seems wrong. A comparison between native Wayland apps vs Xorg apps would have been a lot more relevant though.
For what it's worth I'm an Ionic developer and I find the grand-parent's description pretty accurate. I do like Capacitor though, but I think that's mostly because I've had to deal with Cordova before.
I feel like I'm having a deja-vu. I remember having a similar discussion in the past and it turns out it happened exactly one year ago when Flutter 2 was released: https://news.ycombinator.com/context?id=26336657
Every framework has bugs and feature requests that are fighting for resources. And the ones affecting you _always_ seem more important than the ones that don't.
That being said, the fact that memory leaks in widely used components (e.g.: `<ion-img>` [1]) go mostly unnoticed both by Ionic developers and by the community [2] just doesn't give me confidence in Ionic being a framework used to build quality apps.
[1] - https://github.com/ionic-team/ionic-framework/issues/19242#issuecomment-556182556
[2] - the issue linked above has 5 upvotes in 3 years and no one even bothered to report a separate issue for the memory leak in `<ion-img />`, which seems even more serious and the developers have been made aware of it
> the issue linked above has 5 upvotes in 3 years and no one even bothered to report a separate issue for the memory leak in `<ion-img />`
It looks like you answered yourself, this issue does not seem to affect people.
Either it is a rare intermittent or only happen in very specific configurations, either there is a leak but it is negligeable, or shortlived.
OR maybe this leak cause suboptimal performance but it must not be "feelable" although you did a great find, this issue has been overlooked and its severity should be better investigated. I'd like to remind you that Ionic is not the point, Ionic is simply a packaging of good practices and optimized components (because yes ion-img implement important optimizations over a normal img tag). Some might have leaking issues but the point is that you can trivially use a standard img tag, or a regular react/angular image lazy loading library or even better https://chromestatus.com/feature/5637156160667648
The web BTW will probably be the first ecosystem to provide support for JPEG XL images, which are a significant evolution in performance.
Compare the discussed underinvestigated suboptimality with e.g. this 50% CPU increase over a trivial GIF, and mostly ignored/delayed https://github.com/flutter/flutter/issues/88858 or even https://github.com/flutter/flutter/issues/94205
> Every framework has bugs and feature requests that are fighting for resources.
relativism has its limits, chromium has thousands more human resources than flutter and react native devs combined
welcome back,
about the issue you mentioned, one of the original author wrote a blog in how to address it and how the issue is related to angular.
https://github.com/ionic-team/ionic-framework/issues/25283
It does make a significant difference in profiling though
[citation needed]