roesel

As someone who uses their personal Gmail account to forward emails from custom domains to (via MXRoute and other email providers), losing the ability to "Send as" from the given adresses from Gmail means I will have to find an entirely new "home base" for email (and paradoxically start forwarding my peronal Gmail emails these instead?), right?

Similarly to losing Inbox many years ago, this really sucks.

Until the micro/nano-patterned surface gets dirty at least.

No one wants _buggy slop code_ for their game, but ultimately no one cares whether is has been hand crafted or vibe-coded.

As proof, ask yourself which of the following two options you would prefer:

1. buggy code that was hand-written 2. optimized code that was vibe-coded

I'll bet most people will choose 2.

Except in Slow Horses, most of them are exceptional at least in some way. Many of them are too difficult to work with, yes, but they do excel at _something_. That is very different from being _all around mediocre_.

It might have to do with the fact that (at least on iOS), you can participate in a Google Meet call with just the Gmail app, as well as authenticate sign-ins, and who know what more.

Could the main issue be Google is shipping apps within apps?

Have you tried Ctrl+Enter?

I would love to do: - set aperture priority (fully open for most cases) - set shutter speed to AUTO with a limit (never open for longer than 1/100 s) - set ISO to AUTO with a limit (never go above 6400)

If there is insufficient light, then by all means, the camera should adjust the shutter speed past the limit, but not until it has used all the available "reasonable" ISO range.

It's a shame I have to wrestle my Sony a6400 to get something even remotely close to this.

If I set aperture priority to "maximum possible light in", I often have an issue that when there is insufficient light, the camera decreases shutter speed instead of cranking up the ISO (to the set upper limit), which would be much more desireable. This results in blurry images due to the longer exposure. I would much more prefer a grainy image over a blurred one in this case.

Do you know if there is any option of setting a limit on shutter speed while in aperture mode?

(I understand I can go full manual, but that just doesn't allow for the same point-and-shoot experience in changing light conditions.)

The pixel 4a battery life saga was what made both me and my entire extended family never even consider buying a pixel phone again (and move to Samsung or iPhones).

Google denied the issues existed forever, then shipped a fix that somehow made them even worse, and made the phone unusable for years. I hope we were not the only ones.

Cool to see the growth. I have a minor suggestion: while the spinning counter showing "Estimated growth: 123.5 users since last update" is cool, it would make more sense to only show an integer here, since users can presumably only join in increments of 1 and not fractions.

I still miss the icons for items in the hamburger menu, this was one of the worst changes ever for me personally.

> More streamlined menus that reduce visual clutter

If this means the same as for Thunderbird, I'm going to have to switch after 20 years...

I realize my experiences are anecdotal to the two Pixel 4a phones in my family, but the numerous reddit threads about the Adaptive Battery issue (4a) and the later unexplained stand-by battery drain (4a & 7) seem to show that I have at least not been the only one experiencing this.

This is a laudable effort, but maybe the Pixel team should first focus on feature updates not completely messing up their phones for months at a time?

Owning a Pixel 4a has been great until the first major Android update, which made the "Adaptive battery" feature discharge the phone within two hours in standby. The fix didn't come for more then a year (!). A very similar thing then repeated with the next major update. One would think buying a phone from the main developer of the OS would come with more stability, reliability, and attention to detail, considering the argument of "oh, but it has to support a hundreds of thousands of phone models, not just 3 a year like Apple" is moot.

What good does 8 years of support do if the phone is borked after 3?

3500 is way too much when trying to introduce a new platform. I guess that's the cost of the display (two apple watches) and the chips (a Macbook and a half). But still.

Doesn't Jackett still need trackers such as Rarbg to function?