You seem to be overlooking the fact that many of these current and past years’
videos talk about Cocoa by referencing their constituent components like
AppKit, MapKit, Collection View, etc. You would benefit greatly by sitting down
and watching as many of these videos as possible.
--
Gary L.
> Either way, the chart you linked to kind of proves my point though. It
shows that the majority of users are using the latest released OS after
less than a year.
52% (in the case of peak Mojave adoption) is a very slight majority unlike
in iOS where usually 80-90% of users are on the latest
> On Nov 14, 2019, at 1:13 PM, Pier Bover wrote:
>
> > I wouldn’t be so pessimistic about macOS or even iOS update rates.
>
> According to StatCounter Mojave never went above 52% or market share, which
> means at its peak 48% of users were still on previous versions.
>
>
> I wouldn’t be so pessimistic about macOS or even iOS update rates.
According to StatCounter Mojave never went above 52% or market share, which
means at its peak 48% of users were still on previous versions.
https://gs.statcounter.com/macos-version-market-share/desktop/worldwide
I think it
I wouldn’t be so pessimistic about macOS or even iOS update rates. Its
considerably quicker than you think. IMS, they announce upgrade rates during
public earnings report conference calls typically to brag about how well a new
OS is being received by the public over previous releases or
Well about right in terms of timing if you start architecting / developing now.
Meanwhile a iPad Pro is pretty sweet for the construction/architecture industry.
> On Nov 14, 2019, at 2:30 PM, Pier Bover wrote:
>
> What if you want to support previous macOS versions older than Catalina?
>
> Well I think the point is to go SwiftUI
What if you want to support previous macOS versions older than Catalina?
I doubt the majority of users will update to Catalina for at least 1-2
years.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Well I think the point is to go SwiftUI. Go where the puck is going. Develop
for iPad Pro and use SwiftUI to gain MacOS too.
I got to believe enough of your business logic is now separated enough from the
UI.
Regards,
James Cicenia
Founder
James John Group, LLC
(+1) 773-398-4649
>> Here’s your free advice and prognostications:
https://developer.apple.com/videos/wwdc2019/
https://developer.apple.com/develop/
Neither of those mention Cocoa at all, just SwiftUI. Only slight mention
of Objective-C in a couple of video descriptions about Clang/LLVM and
profiling. That does
As a mostly silent member for years and years, I agree when the list goes off
on a complaint tangent (and when it is flagged by moderators, which is rare but
sometimes necessary), but I have found this Turtle Creek thread quite useful
and agree with many points, particularly these later ones.
> I think this gets back to the transparency issue. If Apple were more open
> about the future, it would be easier to know which cliffs are real.
That is one of my major gripes with Apple. Not only as a dev but also as a
end user. It's like riding a car in at night and only seeing what's
> On Nov 14, 2019, at 8:29 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> I think this gets back to the transparency issue. If Apple were more open
> about the future, it would be easier to know which cliffs are real.
>
Here’s your free advice and prognostications:
>> The longer you wait, the closer the train is to the edge of the cliff.
Correct. But what we have learned from many years with Apple is that some
of those cliffs disappear before you get close, or they just turn into
bumps. Waiting til 2014 rather than 2004 meant using much better versions
of
Yes, we use derez for the Windows app (still running in MS DOS!) It
flattens resources, but doesn't make them easy to parse or maintain.
Casey McDermott
TurtleSoft.com
On Thu, Nov 14, 2019 at 10:02 AM Glenn L. Austin
wrote:
> > On Nov 14, 2019, at 6:11 AM, Turtle Creek Software via Cocoa-dev
Not to create a conflict, but I like to think about it this way. I had to do
it with my parents as they approached their elderly years and we have to do it
whenever the next version of Swift and Xcode come out.
A train is moving to a cliff. The cliff is far away but eventually, if you do
> On Nov 14, 2019, at 6:11 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> Convert resources from ResEdit
>>> DUDE. This is what, 20 years overdue?
>
> Dude. Why would we change them before it was necessary? Don't fix it if
> it ain't broke. There were better things to work on in
>> >> Convert resources from ResEdit
>> DUDE. This is what, 20 years overdue?
Dude. Why would we change them before it was necessary? Don't fix it if
it ain't broke. There were better things to work on in the past 20 years.
We wrote code to go through each type of resource and convert them
17 matches
Mail list logo
