> Years ago, they changed the behavior of the green button to be "fullscreen into a separate space."
Not quite. It has the old behavior (grow to as large a window as supported) if the app does not support full-screen. For instance, the Settings app cannot grow wider, so it grows to full screen height.
The icon that appears when you hover over the green button reflects whether it is full screen or zoom behavior. If you hold option, you will always get zoom behavior IIRC. However, due to the green button being overridden to be a menu in Tahoe, the button icon may or may not reflect zoom/full screen behavior if you press/release option and may instead show the optional modifier on the options in the pop-up menu.
I do not believe there is a way to disable full screen behavior completely, nor spaces. However, I don't think I'd be able to survive working on a Mac without both so I haven't done a lot of investigation there.
It is legit - with some pretty severe caveats. I am pressed to come up with an example that has more formal specification, published source implementations, and public unit test coverage than a C compiler.
It is not feasible that someone will use AI to tackle genuinely new software and provide a tenth of the level of guide-rails Anthropic had for this project. They were able to keep the million monkeys on their million typewriters on an extremely short leash, and able to have it do the vast majority of iteration without human intervention.
If you can figure out a good way for Apple to eliminate the revenue model used for the most profitable games on the platform without getting slapped by regulators, I'm sure they would love to hear it.
They don't have to eliminate it, that wasn't my complaint. They need a competitive ecosystem with real-world stakeholders (a-la Epic) and third-party community support like emulators.
iOS is so far behind in this regard that even uttering it in the same sentence as "gaming" almost exclusively implicates gachapon titles or microtransaction slop. Other platforms don't suffer as much.
It's important to understand the timeline of the Steve Jobs open letter on Adobe Flash - at that point the iPhone had been out just shy of three years, and before the first public betas on Android. So for nearly three years, Apple had been investing in HTML5 technology because Flash wasn't in a form where it was deployable.
Additionally, Flash required android phones with 256MB ram as a minimum (which would have precluded two of the three shipped iPhone models at the time) and at least initially only supported software video decoding. Because of the difference in screen dimensions, resolutions and interaction models (plus the issues with embedding due to RAM limitations), the website was still basically broken whether your mobile phone had Flash or not.
My understanding (based on the timing) was always that when Adobe was finally ready to push its partners to bundle mobile Flash, Apple looked at it and decided against it. Adobe made public statements against their partner and so Jobs did so in kind.
In addition, there is a clause added (IIRC because of the patent shield licensing deal between Novell and Microsoft) that third party patent licensing needs to cover downstream GPLv3 usage. You cannot simply license a patent for your binary distribution.
So it is possible Apple's lawyers read this section as meaning an injunction against GPLv3 code may be infeasible to solve with licensing the patent, and instead require Apple to make changes on a time-table they would not be happy with.
Sticking to GPLv2 lets Apple control the time table it has taken to license, reimplement or remove components which had moved to GPLv3.
I can't tell you why it took them until El Capitan to remove the Emacs install though.
Supposedly when Michelangelo was asked about how he created the statue of David, he said "I just chipped away everything that wasn’t David.”
Your work is influenced by the medium by which you work. I used to be able to tell very quickly if a website was developed in Ruby on Rails, because some approaches to solve a problem are easy and some contain dragons.
If you are coding in clay, the problem is getting turned into a problem solvable in clay.
The challenge if you are directing others (people or agents) to do the work is that you don't know if they are taking into account the properties of the clay. That may be the difference between clean code - and something which barely works and is unmaintainable.
I'd say in both cases of delegation, you are responsible for making sure the work is done correctly. And, in both cases, if you do not have personal experiences in the medium you may not be prepared to judge the work.
Something is different. Right Click->Open With->Other->Always Open With 100% did not have any effect when I needed it in the past. Not sure what current behavior is. This was a huge thing for me.
I have noticed something similar. I feel like I have done that so many times for XML files. Perhaps it is re-establishing the settings when any kind of update gets installed.
It isn't a dietary heuristic, because there's little advice provided. The extreme is that it is advising people to seek treatment if they suffer from pica or bulimia.
By heuristic, I just mean “a rule used in decision making”.
Under that usage, the fact that the rule doesn’t provide fine-grained advice doesn’t disqualify it from being a heuristic. Eating mostly plants is a rule used in decision making when considering what to eat.
> The extreme is that it is advising people to seek treatment if they suffer from pica or bulimia.
Not quite. It has the old behavior (grow to as large a window as supported) if the app does not support full-screen. For instance, the Settings app cannot grow wider, so it grows to full screen height.
The icon that appears when you hover over the green button reflects whether it is full screen or zoom behavior. If you hold option, you will always get zoom behavior IIRC. However, due to the green button being overridden to be a menu in Tahoe, the button icon may or may not reflect zoom/full screen behavior if you press/release option and may instead show the optional modifier on the options in the pop-up menu.
I do not believe there is a way to disable full screen behavior completely, nor spaces. However, I don't think I'd be able to survive working on a Mac without both so I haven't done a lot of investigation there.
reply