On Wed, 2 Oct 2019 10:50:19 +1300, Sam Ryan via Cocoa-dev said:
>That was a good read, thank you for passing that on. It highlights a good
>point, that Apple is itself releasing applications with non-Mac UI (News,
>Home, Stocks, Voice Memos are mentioned in that article).
Another way to look at
—Jens
> On Oct 1, 2019, at 2:50 PM, Sam Ryan wrote:
>
> In fact those applications are forced upon the user in a way that I've never
> seen before, as if they are core system components.
You mean pre-installed? There have always been plenty of bundled apps like
Mail, Calendar, Chess, etc.
That was a good read, thank you for passing that on. It highlights a good
point, that Apple is itself releasing applications with non-Mac UI (News,
Home, Stocks, Voice Memos are mentioned in that article). In fact those
applications are forced upon the user in a way that I've never seen before,
as
> On Sep 30, 2019, at 5:57 PM, Sam Ryan wrote:
>
> I tried a completely new approach - Electron. I have found Electron to be
> surprisingly quick to prototype, easy to bridge to c++, and is cross platform
> (non mobile at least). I would not have recommended a non-native approach
> until
> On Sep 30, 2019, at 4:57 PM, Sam Ryan wrote:
>
> I tried a completely new approach - Electron. I have found Electron to be
> surprisingly quick to prototype, easy to bridge to c++, and is cross platform
> (non mobile at least). I would not have recommended a non-native approach
> until
No apology necessary, I'm pained by the same problems as you mentioned!
On Tue, 1 Oct 2019 at 14:00, Jens Alfke wrote:
>
>
> On Sep 30, 2019, at 4:57 PM, Sam Ryan wrote:
>
> I tried a completely new approach - Electron. I have found Electron to be
> surprisingly quick to prototype, easy to
I have recently looked at utilising Swift to update an old Carbon based
application. I stopped pursuing this path Swiftly, in part because of lack
of good support for sockets and generally problematic use of CG* code.
I tried a completely new approach - Electron. I have found Electron to be
> Le 30 sept. 2019 à 17:16, Robert Walsh via Cocoa-dev
> a écrit :
>
>
> Swift may be the solution, but it's built on a weak foundation. It makes
> cross-platform development almost impossible. The TIOBE index shows Swift
> declining (and Objective-C increasing). So, maybe it isn't.
>
> I
> On Sep 30, 2019, at 8:16 AM, Robert Walsh via Cocoa-dev
> wrote:
>
> however, to use it to do anything other than building a desktop or IOS GUI
> application seems to result in code with messy syntax and what seem to me to
> be hacks in order to bridge between NS* and CG* code. (Lots of
Swift may be the solution, but it's built on a weak foundation. It makes
cross-platform development almost impossible. The TIOBE index shows Swift
declining (and Objective-C increasing). So, maybe it isn't.
I don't yet have a lot of experience with Swift, but I would already argue that
Swift
> On Sep 27, 2019, at 1:21 PM, Jens Alfke wrote:
>
> I was typing a lengthy answer, but it occurred to me it's basically the same
> reason why Apple didn't release macOS for generic PCs ('hackintoshes') and in
> fact actively made it difficult for anyone to port macOS. It's because it
>
> On Sep 27, 2019, at 9:20 AM, Richard Charles via Cocoa-dev
> wrote:
>
> What I wish Apple would do is release a cross platform Objective-C (and
> Swift) solution. ...
> The Mac vs Windows war is over and long gone so why doesn’t Apple help out
> the small developer and release a cross
> On Sep 27, 2019, at 6:19 AM, Turtle Creek Software via Cocoa-dev
> wrote:
>
> We used an object database called NeoAccess for our 32-bit C++ app. It had
> reference counting for objects retrieved from the database. Setting the
> ref count manually was extremely easy to screw up. It was
On 27 Sep 2019, at 14:19, Turtle Creek Software via Cocoa-dev wrote:
It makes sense that Cocoa programmers much prefer ARC to MRC. Doing it
manually is easy to break and hard to debug. However, the fact that
ARC is
not exception-safe concerns me.
Cocoa in general is not exception safe as
We used an object database called NeoAccess for our 32-bit C++ app. It had
reference counting for objects retrieved from the database. Setting the
ref count manually was extremely easy to screw up. It was hard to debug
off-by-ones on the ref count. So we made those calls private, and replaced
15 matches
Mail list logo
