I asked it to find me soccer fields in <insert my suburb> and it showed me results but all 5 of them were misplaced. One of the fields was shown where a train station is, there are no parks nearby.
Same for my question of bars in Thessaloniki, it found 5 in the whole city and the locations were off by km. I fear that we're missing the point, though, because the good bit here isn't "it can do what Google Maps can do", but we aren't asking the right questions to show that off.
If you have a commit that doesn't compile, it should have been squashed into another commit before merging the PR. Every commit should be in a valid state. I'm not talking about a full squash merge, just `git rebase -i` to make sure the history makes sense. The final branch history doesn't have to be the same as your development one.
With Jujutsu it's not at all complicated. Sure, you may not agree with the example (and I would say its a little contrived), but rebasing into history to keep a clean progression of commits in a feature branch that is unreleased is something that many people are keen on.
Jujutsu also has a bunch of other really useful features like `jj fix` which can run a code linter over a linear commit history (in parallel) and integrate the changes into the commits that should contain the change. This avoids a litany of 'fix formatting' style commits littered through your history.
> rebasing into history to keep a clean progression of commits in a feature branch that is unreleased is something that many people are keen on
To give some specific examples, "many people" includes popular open-source projects like Linux and Git itself, as well as large tech companies like Google and Meta, which employ "trunk-based development" (see e.g. https://trunkbaseddevelopment.com).
I’m actually taking a very componentized approach with my new Rust based firmware. Wherever it makes sense, I’m spinning things off into separate crates and will be publishing them (e.g. crates for the ADS124S08 and FDC1004 used in the All-Purpose Espresso Controller.
Also, everything is permissively licensed, so feel free to use whatever you want.
In a lot of cases you find tangential dependencies on Windows in ways you don't expect. For example a deployment pipeline entirely linux-based deploying to linux-based systems that relies on Active Directory for authentication.
That extends to any and all applications. Nothing is stopping a local only Keepass installation from being exposed via a supply chain attack to start sending passwords to an attackers server. In fact, I trust 1Password's corporate infrastructure more than my own ability to lock down my personal devices.
I think you should read the 1Password security whitepaper before rambling on about things you clearly haven't spent the time and effort to learn about.
However, in their white paper they specifically have a section "Crypto over HTTPS" which outlines the risks of their new web UI. Yes, the password stays local if no one mucks with delivered js, however, 1password being compromised would allow serving of modified js.
This is a new vector only present due to their new web vault model + associated web UI features. They state it themselves in the whitepaper:
"The authenticity and integrity of the web client depends on the security of the host from which it is delivered. An attacker capable of
changing the web client on the server could deliver a malicious client
to the user"
1P could be 'compromised' and send a malicious version of their software back before they had the subscription model... I don't see how this is involves any more risk.
I don’t necessarily care about the technical details as a customer, but I do care about things like “we are prioritising restoring our PoS payment processing first, then online payments second”
After 8 hours, telling me about my patience is a slap in the face
