moshetanzer

Starting January 2026, Gmail is removing support for POP3 and Gmailify. This means millions of people who rely on Gmail to consolidate emails from other accounts will suddenly lose features like spam protection, inbox categories, and advanced search on their third-party emails.

If you manage multiple email accounts, how are you planning to keep all your emails flowing smoothly to Gmail or elsewhere? Are you switching to forwarding, using other clients, or something else entirely?

Would love to hear how the community is adapting to this change.

It drives me crazy the amount of noise there is on all the PR ai code reviews. There is so much that could be caught by reviews before - maybe at commit time? Is this just me??

Ask HN,

Code reviews are essential, but I keep seeing the same pattern: PR reviews are full of comments about trivial bugs, lint issues, and convention mismatches that could have been caught before the code ever left the developer’s machine.

With AI-assisted coding becoming the norm, this seems worse, not better. AI is fast, but it happily produces subtle bugs, inconsistent patterns, and sloppy edge cases. By the time a PR is up, reviewers are debugging noise instead of reviewing architecture, correctness, or intent.

Why isn’t pre-commit review (automated or otherwise) the default place to catch these issues? Is there a real downside, or is this just inertia?

I built a small pre-commit review tool to experiment with this idea and genuinely can’t imagine going back, but I’m curious why this isn’t already standard practice.

Would love to hear how others think about this.