Yep, a lot of these policies seem to come from some random person scrolling through a list of supported options and arbitrarily making up values that are enforced on people.
One of our policies enforce that screen savers must start after 20 minutes, and it’s not possible to reduce it (I have my personal on 3 minutes). Or the fact that it will constantly reset the UI notification volume to 100% and speaker output, even though have headphones almost always.
I agree it's not necessary, but i like having it because it lets me separate what's going to be added before i actually commit.
I still commit small, frequent. But i like `git add -p` to skip debug lines, hardcoded conditions, etc. I don't want to mistakenly auto commit a whole pile of lines and then have to remove debugs/hacks/etc from things i've committed.
Stage + Unstaged is my working area, and the two live together quite nicely to me personally. I could live without it, definitely.. but i'm not sure i'd want to.
> Stage + Unstaged is my working area, and the two live together quite nicely to me personally. I could live without it, definitely.. but i'm not sure i'd want to.
You can just use the tip as your staging. Use interactive amending to move changes from the working copy to the commit, and when you want to "commit", finish up the message.
hg actually has an "unamend" command (part of the "uncommit" standard extension) which... reverts the last amend. Rather than having to remember how to contort reset into the right shape to move changes back out of staging without destroying everything.
`git reset HEAD~` doesn't feel like that much of a contortion to me. It's the destructive change that requires more contortion (`--hard`) which feels fair. Maybe this is stockholm syndrome though.
The way I think of it, there's basically three copies of the file in play: in HEAD, in staging area, and on disk. I cannot trust my memory to remember which variant of "git reset" copies the file in HEAD to the staging area, which variant copies staging area to disk, and which variant copies HEAD to disk (in all cases, the third copy remains uninvolved). Getting it wrong potentially creates unrecoverable data loss. And, unfortunately, this is one of those cases where reading git's documentation is less than helpful.
Combine this with the case where "I want to break one commit into two commits," where now I have to worry about making sure I know if the command is going to change the revision HEAD points to. At least there, the old commit will still exist as backup in the invariable scenario I screw something up.
In those cases, I find it best to either 1) use the interactive commit tool to not commit debug junk, or 2) put the debug junk in its own commit, which I'll later discard (and, plus, that means you can't accidentally include it in a real commit).
I’ve never used one of the source control systems at these big companies but I use the staging area along with your git-branchless just fine for now. I’m not sure if it’s any less efficient this way.
It's not a big deal either way, but the staging area interacts worse with some operations. For example, if you have staged changes and then get a conflict with `git checkout --merge`, AFAIK there's no way to undo to before the conflict in Git. When using commits, all of the standard merge and undo tactics apply.
I guess each to their own. I want to stage my commit with regular commands, and then have the staging area work with (diff, add/remove etc).
I don't care for an interactive tool, IMHO I prefer using commands that are repeatable and learnable instead of stepping through some interactive workflow all the time.
You `sl commit` that half-done work anyway and then iterate by running `sl amend` many times until your commit is finished. In case you want to amend just part of changes us `sl amend -i`
It stems from the original Mercurial implementation. The goal here is that every operation leaves the repository in a good state that can be pushed/pulled. That's why Mercurial and Sapling rely on commit/amend/uncommit, etc and for example usually discourage the use of interactive rebasing in favor of restack and other operations that add another "state". It facilitates the mental model for developers without actually removing workflows (they are just different).
With noise cancellation I find I never have to crank up the volume above low-medium. This is great as I also try to avoid damaging my hearing more.
The iPhone also has a widget in the control center that displays the current decibel number that the AirPods are outputting. I never go above the “green zone”. The volume is tracked in the Health app where you can see all historic data.
Finally the iPhone has an accessibility function where you can use apps to create perform a sound test, and then generate a specific frequency curve for your phone (maybe boost some frequency that you struggle to hear or increase the volume on one side etc).
Firefox for Mac has been more or less unusable up until the most recent release where they actually started using the Core Animation libraries in macOS. Now it won’t drain all the battery in no time, and it’s actually quite snappy. I’ve tried to run Firefox so many times in the past, but eventually always go back to Safari because it’s more native, fast and unobtrusive.
The issue has been the power draw and heat on newer MacBooks with a Retina display.
Older Firefox versions are redrawing the entire window even if only a tiny portion of the window was changing.
With advent of high resolution windows, the amount of work needed to redraw the whole window for every frame became significant.
The last version of Firefox moved to breaking the window into large tiles and only redrawing the tiles that have changed.
This is still less optimized than Safari (which uses Core Animation to only redraw the items on the page that are changing) but it is still a large improvement over prior versions of Firefox if you have a high resolution display.
You can also run in on-demand mode and exclude your home WiFi, which is what I do. Then you'll be connected to the VPN at all times except when you're on the home WiFi.
If the value rises considerably in a few years for you to make a decent profit, then its mostly a headache (and operating costs, wear and tear etc) to have tenants .
Algo (another commenter mentioned it[1]) allows you to set this up to be the default for the VPN, very nice feature. I use it on my phone since I often connect to random wifi APs. More and more of the web is moving to HTTPS but a disturbing amount of unencrypted traffic abounds.
Yep, Algo uses the same approach. It's generating device configuration profiles with the necessary settings. I'm generating mine in the same way but slightly different to allow toggling Ethernet and to support the OpenIKED ciphers etc.
> The only way to configure this however is using the Apple Configurator tool and create a custom profile.
'Activate on demand' is just a checkbox in WireGuard app settings on iOS, so apparently it's only the built-in VPN types that need Apple Configurator. Since IPSEC/IKEv2 are overengineered and L2TP is outdated, you're better off using wg anyway.
On a very high level ZFS main thing compared to APFS is currently data integrity features such as checksums of the data to detect bit rot (silent corruption) and the ability to automatically heal the data (with enough redundancy in place).
It would be good to at least have the checksum capability in place to make one aware of bit rot silently destroying data. Hopefully there has been some improvements to the capabilities since the announcement last year.
Yes, bit rot happens all the time. Normally the drive its self catches and repairs these errors, but sometimes they slip through and become the filesystems problem. It doesn't really happen super often, but the fact that it happens at all mandates that filesystems that care about data integrity handle it.
One of our policies enforce that screen savers must start after 20 minutes, and it’s not possible to reduce it (I have my personal on 3 minutes). Or the fact that it will constantly reset the UI notification volume to 100% and speaker output, even though have headphones almost always.
Infuriating.