Yeah and Vela Maps does it even better

I already have Vela Maps for those lookups, thank you for the suggestion tho

By whom? I don't even have a license and still I'd say it's a must have for longer trips

yes Vela Maps, typo

it works great and I use it whenever OSMAnd isn't enough or just simply unsuitable (finding restaurants e.g.).

It's up to you if you'd rather use GMaps directly or just pass on important information like that OFC

Vela Maps is the best way to get accurate information about traffic and opening hours while interacting with Google only as little as you have to

It's like NewPipe but for GMaps

Isn't it moreso Vinyl?

Hopefully not, as it is an insecure hot mess

Then the Framework Laptop 13 Pro might be for you, but it's quite expensive.
Though it's repairable nature and easy upgradeability (you can buy a new motherboard when you want to upgrade your CPU, while keeping the same chassis e.g.) might save you some money in the long run

They never vibe code though:

This process is fully transparent and open for anyone to see, and it does not change with AI. We take no shortcuts. At KeePassXC, we use AI for two main purposes:

As an additional pair of “eyes” in code reviews.
In this function, AI summarises the changes (the least helpful part) and points out implementation errors a human reviewer may have missed. AI reviews don’t replace maintainer code review, nor do they relieve maintainers from their due diligence. AI code reviews complement our existing CI pipelines that perform unit tests, memory checks, and static code analysis (CodeQL). As such, they are a net benefit and make KeePassXC strictly safer. Some examples of AI reviews in action: example 1, example 2.

For creating pull requests that solve simple and focused issues, add boilerplate code and test cases.
Unfortunately, some people got the impression that KeePassXC was now being vibe coded. This is wrong. We do not vibe code, and no unreviewed AI code makes it into the code base. Full stop. We have used Copilot agent to draft pull requests, which are then subsequently tweaked in follow-up commits, and reviewed by a maintainer, openly for anyone to see, with the same scrutiny as any other submission. Good pull requests are merged (example), bad pull requests are rejected (example).

That's on corporate sites just saving work or intentionally obstructing and restricting Firefox because Google basically a monopoly.

For me personally Firefox (and it's engine Gecko) work fine for 99% of websites I visit.

It uses Google's browser engine base called Chromium, which Chrome is based on (the used engine is called "Blink"). A lot of websites are made to just function well on Chromium and maybe Safari

For normal usage and actually using a messaging app for what it's intended (contacting people in your life), it's far too obscure and non-streamlined tbh. Signal is more than good enough for the thread model of chatting with friends and family, and ppl you got to know online