351–360 of 373 posts
Earlier quoted context omitted.
In that statement it wasn't 1) acknowledged that this is indeed an issue and 2) the word workaround was not used.
See my above statement. If someone reports issues with software you don’t immediately say it’s definitely a bug unto you fully understand it. Hardware is no different. We do not know if they were in a position to say either way at the time.
Earlier quoted context omitted.
See my above statement. If someone reports issues with software you don’t immediately say it’s definitely a bug unto you fully understand it. Hardware is no different. We do not know if they were in a position to say either way at the time.
They simply said it's not a bug at first, then after the backslash, went back and admitted that it is.
It’s a shame as I think it is interesting to see how people perceive things with hindsight specifically related to apple and how engineers who presumably work on similar problems cannot apply the same logic to apple but I am forced to stop the conversation. This will be my last comment on any thread related to this and I am rethinking my contributions to HN.
Earlier quoted context omitted.
Could you explain what JIT would allow? Would sideloading allow this to "work" or would it need OS support?
JIT (Just-In-Time) compilation is a technique that allows certain programs to run significantly faster by compiling code at runtime, rather than ahead of time. Apple enabled this for iOS 14+, but killed it again with iOS 17. It's basically the reason why we currently don't have full speed VM's on iOS / iPadOS devices. While Sideloading / Altstore / Sidestore allows you to install any IPA, this still doesn't enable JI…
> but killed it again with iOS 17
Aah, this explains why UTM (iirc) allowed VMs on iOS 16 on M1 macs but not on 17.
> There are currently some workarounds that involve running certain software on your local network (search SideJITServer on Github).
If I understand right this requires another computer to run some code, right?
Earlier quoted context omitted.
Yep, I've got one and don't use too much. Too big for scrolling, too limited (software) for work. But Apple knows iPad might cannibalize mac and limit it's uses on purpose
> But Apple knows iPad might cannibalize mac and limit it's uses on purpose Felt the goal was to overtake Mac during the 2015-2019 era, all the real engineering focus was on iPad, the Macs were underpowered and not really fit for purpose. Why would Apple choose a platform where they don't get 30% of every Creative Cloud sub when they could have had that. Only reason they backtracked was because Mac sales didn't fall…
Do not think it's possible. Traditional Mac computers can win in so many ways