| Model Colors | https://apps.apple.com/app/model-colors/id1200319954 |
| https://www.linkedin.com/in/janekholm/ | |
| https://twitter.com/jan_ekholm |
Case in point. I have a couple photos I want on my Mac that I took yesterday. Still have not synced to Photos on the Mac. There's nothing I can do to get things to sync, nothing to tap, click or poke, nothing to kill or restart. Apple in their hubris think that Things Just Work as they maybe did 20 years ago before they started doing networked stuff.
Alas, things don't work and it's bloody annoying.
The best UI framework to get stuff done is still Qt after all these years. There may be something that lets you do simple stuff easier, but nothing comes close to the power of this fully armed UI toolkit. Coupled with Python it becomes a lot of fun too.
That said, a five-six year old app that's only been quickly added to and never rewritten nor cleaned up does get a bit ugly. Maybe time to take a few days at some point and fix it up and make the networking side better.
I guess Xcode still doesn't have a way to catch these errors? I load assloads of data asynchronously via operations and putting breakpoints/logging in each is not a fun task. Why can't I set a breakpoint where this error happens or force Xcode to throw an exception? This "you have an error but we're damned will not going to help you find it" attitude from Apple is so tiring.
#xcode #publishingvaluesfrombackgroundthreadsisnotallowed #fsck
Updating the Sentry package in Xcode seems to never work. The update doesn't give any error, but it also never works and just shows a red icon. Apparently it failed but Xcode is so damn stupid that it refuses to tell me what went wrong. Also Sentry is the only package that fails. So the repo is somehow "special" in a bad way and/or Xcode is its usual brain dead developer hating self.
/cc @getsentry
Seems Graphviz creates graphs in 3D. Not too readable when everything is a mess for my dead simple graph. Fortunately there's only about 6500 properties to go through one by one to check. Not too impressed.
Weird stuff. I use an older Raspberry Pi Zero W as a logger machine. It's connected to a serial port and basically just receives logging written to the UART. Worked fine for many years to ssh into it and check logs. Now for some reason ssh just freezes at this point after entering the password. Restart the Pi and it may work. Maybe 1 out of 10 attempts works. After logging in everything looks fine, the connection is snappy and nothing weird in the logs.
I am quite happy about these numbers for my crappy little app. I was fearful that all users would abandon it when I enabled mandatory subscriptions in August. Been performing better than expected. Will probably not last though.
My subscription price is really low at 6€ for a year. Basically a tenth of what an average user would spend in a day on the hobby this app caters to.
