For me the benefit is that I can revert or cherry-pick things one entire PR at a time, and I don't have to care if the author implemented their PR with a bunch of small "work in progress" commits.
And GitHub at least sets the author of the squashed commit as the one who opened the PR, not the one who merged it.
I can definitely see where it wouldn't work well for other workflows but I've had it work well on several teams and it seems easier than trying to get everyone to clean up their commits into nice, clean, well-titled histories before putting up a PR.
What for? It was a mandatory step but my wife and I will manage the credit through an app on her phone. Minimally, I should have the option to waive it.
You’re both signing up and aren’t one singular entity. She might be the one actually using the app and whatever line of credit but you’re still signing up with the bank. They need a way to do 2FA for you and not just her. If you divorce, how are they going to do 2FA when you’re separated? If it was her phone number then she could imitate you and get more credit or do whatever.
Etc. etc.
Genuinely no idea why you’re not considering this.
Annoyingly "Android Auto" and "Android Automotive" are completely different things.
Android Auto is where you can connect your phone to the car and your phone projects onto the car's display with apps and navigation.
Android Automotive is when the car itself is running Android Automotive for its infotainment OS, meaning it has access to a limited Android App Store to install apps natively into the car's infotainment system and you can sign in with your Google account.
Some cars with Android Automotive also support CarPlay and Android Auto on top of it, but GM has decided to disable those features, meaning you have to use the built-in Android Automotive system to manage your media streaming apps and pay GM for the data access plan.
The main difference there is that with an HDHP your employer is still the one choosing the insurance provider, and the insurance provider views your employer as the customer. There's no risk that you as an individual will switch to another provider as long as the employer remains with this one.
Removing that layer of indirection would make it your own choice to pick a provider, and the provider is then incentivized, at least a little bit, to provide you with a good outcome or else you may freely switch to another provider.
There's also the component that, right now, you lose the discounted group rate insurance premium as soon as you lose or leave a particular job. Putting the purchasing power with the end consumer means that you can keep your provider at the same premiums even if you switch jobs. All that might change is your employer contribution.
My understanding is that some US states have regulations against selling power by the kWh unless you are a registered power utility. This is an old regulation meant to be about landlords marking up electric rates to tenants etc.
Most states have updated their laws to account for EV charging providers, and in those states we pay per kWh.
This product effectively cuts the entry price for a new model Mac laptop in half. The cheapest current-generation MacBook has been $999 or above for a very long time, even back to the iBook days.
Yes, Apple has offered discounted prices by continuing to sell older models or offer straight discount sales via third party retailers. But I expect that will continue here too. This is $599 MSRP at Apple but will probably be $499 via the usual retailers by the end of 2026.
That's a bit different than continuing to sell a 5-year-old model at a discount.
I think assuming that this is a disposable, non-serviceable machine is a bit premature. Yes the RAM and SSD are soldered to the mainboard, but otherwise it looks like this might be Apple's most serviceable computer in a long time.
TBF my friends who were getting business degrees struggled with their 8 gigs pc. When they need to run something like SPSS next to a chrome instance, their ram got tight pretty fast.
And GitHub at least sets the author of the squashed commit as the one who opened the PR, not the one who merged it.
I can definitely see where it wouldn't work well for other workflows but I've had it work well on several teams and it seems easier than trying to get everyone to clean up their commits into nice, clean, well-titled histories before putting up a PR.
reply