In one of those “duh” moments for today… I’ve been wrestling with an oddity in my git repositories with vscode. Sometimes when I open a git repo, it will just suddenly duplicate all of the files in the repo. It seemed to happen most of the time when I was opening a large git repository with vscode. Turns out that iCloud is to blame - something about vscode and iCloud Drive synchronization doesn’t get along. Solution: move your development directory out of ~/Documents or iCloud Drive. All will be well. They didn’t need to be there anyway. Duh.
I’ve noticed that my M1 Max Macbook Pro battery has been getting hammered lately, and I wasn’t entirely sure why. Activity Monitor was confirming some of my greatest fears: Safari was actually using significant energy. I didn’t know why. The lesson? Beware of new features.
This thing is flat-out amazing, and I’m sorry I waited so long to get one.
Apple has a knack for building things under our noses over the course of years… actually, even decades. They’re really good at building onto their technology when it works. When it doesn’t work, they throw it out and start over, only to build it up in the way that matches their final vision. We saw this happen with the M1 chip. It took them more than a decade, but they finally cashed in on their vision. I think we’re about to see that happen again at WWDC 2021.
Many years ago, I embarked on a home automation hobby that has drained my budget. Home automation is a horrifically expensive hobby (like most of them). There’s a lot of trial and error. You’ll almost always buy stuff that doesn’t work or integrate well. It’ll be expensive. You’ll want to replace it because it’s not perfect.
I started off with the center of my universe on Amazon Alexa (like most people). I am also an Apple-holic, so I often employed hacks to make third-party gadgets work in the HomeKit space. Homebridge has been quite successful at filling in the gaps where necessary - the glue to the Alexa and HomeKit ecosystems. Alexa was my “home’s personality” according to family and visitors and for the most part, that was ok.
Apple never announces hardware updates at WWDC. They only talk about the software and things that developers care about. The new hardware always comes in the September/October timeframe. I don’t understand why the press continues to think Apple will release new hardware at WWDC.
Yes, they talked about Apple Silicon, and they gave you a good guess about when it’s coming out - but they didn’t announce anything that you can buy, yet.
How is it that Apple has followed this formula for more than a decade and people still don’t get it?
I really want to use my iPad to write code. It shouldn’t be this hard. I don’t know why, but it really is. Today, I’ve been playing with round-tripping through Working Copy and Code Editor by Panic (formerly Coda). I think I’ve almost gotten it worked out, but man is it painful. I shouldn’t have to run a webdav server on my own iPad to edit documents and save back to GitHub.
I guess the good news is that I’m able to ssh into a local copy of my git repo without leaving this window. I sure have put down a lot of money on text/code editors just to experiment and find out which ones aren’t working out.
This should be so much easier. I feel like iPadOS has been band-aided to death so that it can avoid being a Macbook when people want to use it like a Macbook.
My series on whining about macOS Catalina continues today as I tried to use AWS Cloud9 in Safari. It doesn’t work. You have to enable third-party cookies to make it work. Apple has apparently removed the ability to re-enable third party cookies in Safari 13.
Want to use it on iPadOS? Nope. Can’t enable third party cookies in iPadOS on Safari or Chrome. No more Cloud9 for me. Just deleted the environment.
I managed to get a fresh install of Google Chrome working under Catalina. But it wasn’t easy to unravel. Apparently, if you have spctl enabled on first launch, Chrome will create a jacked-up profile folder that it can no longer access. I discovered this by running the binary from inside Terminal, where the story was told.
To fix, here’s what I did:
WARNING: Unfortunately negative post.
This has been an interesting year in the Appleverse. iOS 13, iPadOS and macOS Catalina were all dropped on us. This new software “regime” has been quite the challenge for me.
iOS 13 and iPadOS haven’t been that troubling. They generally work and do what they promised to do. I did find it curious that iOS 13.1, 13.1.1 and 13.1.2 all dropped in pretty rapid succession. That’s usually a bad sign that things weren’t up to standards and had to go through some quick resolution. There were either fixes or outright removals to get things out the door. I don’t like it when that happens, but I get it. I’m glad they stay on top of things well enough.
Catalina and Apple TV on the other hand… have been a complete shitshow.
Update: I resolved the Google Chrome issue. If you’re just interested in the resolution, please go here.
