In my opinion (which may be worth little), by using "git" in your product's name today you are also locking onto that technology. So if an another or better VCS comes along (like jj) that you want to embrace it could be harder. (Kind of like how Bitbucket betted wrongly on hg, then later added and switched to git).
More issues generally arise from supporting/qualifying older OS versions than supporting specific architectures in my experience, so developers keep around older hardware or VMs for that purpose. In some other circumstances Rosetta may not be sufficient for testing older Intel hardware (one example is work on GPU)
For updating bookmarks I've found like half a dozen variants of `tug` alias the community has come to using which is just a slight improvement (bit daunting to newcomer to pick 'best' one and not fan setting up aliases on all my working devices).
It would be nice if jj was better than git for the fundamental workflows like this out of the box overall.
Just my feedback - I've personally found jj more complex for simple projects. Like if you have a non-collaborative repo where you push to main most of the time after making a series of commits, in jj you have to keep updating a bookmark before pushing it and there's no one command to do both.
If you have another machine on main without any outstanding changes and you want to pull the latest changes that is probably also two steps (git fetch + new?)
That said, I've been liking jj quite a bit for more mature / collaborative projects. It has been a learning experience. (don't enjoy updating bookmarks for PR branches though; jj encourages rewriting history which is not my favorite choice for code review branches; I often work in repos that squash-on-merge).
Applications may have permission to access files/services that other apps and even root (I believe) would need user-prompt access to, gated by TCC (potentially including sandboxed game’s data).
Code signed games that opt into enabling library validation should prevent the issue of loading arbitrary code, however many games likely don’t do this.
While I was learning a new keyboard layout (Colemak) I went from > 100 WPM to starting from ~20 WPM. I think I got pretty productive when I reached 60/70 WPM and was surprised how much tab completion and computing assistance I relied on anyway. After that experience I think fast typing speed is overrated. (Now I’ve a somewhat useless skill of being able to type > 100 WPM on two different keyboard layouts.)
Edit: note if you are a typist and transcribe a lot of text for long periods of time without break, typing speed is important. But that’s mostly not any of us. But hey maybe I don’t write enough documentation and comments..
I've been typing in both qwerty and colemak around the same speed (>=100 WPM) for almost a decade. I ultimately ended up deciding to use qwerty at work and colemak at home. At least for me the comfort difference between layouts is marginal.
Modern versions of Sparkle are a less random in when to show the update alert (lots of software, iTerm including, use ancient versions of Sparkle)
DND is not properly/reliably detectable for 3rd parties. Support for Notification Center is not well designed for a framework to control and works as an auxiliary/supplemental (not primary) functionality for 3rd parties, so apps themselves would have to opt into using it along with adding a lightweight UI indicator which may need to be tailored to the app in question.
I buy whole wheat bread with very little sugar, although it is easier to find wheat bread with lots of added sugar and even more so in restaurants. I guess I would consider it as a good part of my balanced nutrition, not so much healthy by itself.
Personally (on desktop) this design strains my eyes. I want to look in the center where there's nothing to grasp, and there's the official statement, black banner, time boxes, time zone titles in highly varying colors/fonts competing with each other. Also I notice the page auto-refreshing in the background.
As a side note, the forums aren't the best place for that; the post could just be unseen by the people that matter. The appropriate channels are through Feedback Assistant and/or a technical support report (https://developer.apple.com/support/technical/) which has bit more visibility.
As someone that's written a game "cheating" tool there's good technical / reverse engineering value from modding or cheating games. Plus it's fun to just be able to change a game (I fondly remember the days playing with Game Genie).
It is indeed a bit immoral when one tries to cheat in a way that unfairly puts themselves ahead of other humans.
This website needs to scale text better on mobile (on an iPhone) so it's not hard to read. Especially for a post advocating on using vanilla HTML and how nice and powerful it is.
I don't think I particularly disagree with any of the post, but I found it a little long-winded.
It's a misconception that layout switchers are relearning to type, especially if they were proficient qwerty touch typists. The better typists in qwerty have a significantly easier time learning a new keyboard layout. Most of the typing skills positively transfer over, even though there's still an initial hurdle.
Furthermore, I think there's significant bias when typists learn a new more ergonomic layout. For example, they may have incidentally fixed their typing posture when learning Colemak, they want to justify their investment, or they overestimate the efficiency/comfort gains in respect to how much they need to type daily. Performing frequent typing tests (something alternative layout typists like to do!) is furthest away from reality for most people. Many switchers also forget how to type in qwerty well; improving typing speed while learning feels "really nice" and it's easy to wrongly associate this with "qwerty is uncomfortable."
They also downplay the importance of living in a qwerty world, having to share a computer with another, or being able to proficiently type in qwerty (which many of them do not retain), or dealing with software not accounting for other layouts.