Hi all
In a couple of months I'll be starting a macOS Swift 5 project and if
possible I'd like to separate as the business networking logic so that it
can be reused in a Windows app in the future.
Ideally I'd want to statically link the library but I've also considered
using dynamic libraries,
Another option I've found is using Kotlin Native.
https://kotlinlang.org/docs/reference/native-overview.html
It compiles Kotlin code directly to Apple frameworks for perfect
interoperability without the need of a JVM.
On Mon, Aug 26, 2019 at 6:41 PM Pier Bover wrote:
> Hi all
>
> In a couple
> I had a similar dilemma in 2015 but went with C++, despite earlier bad
experiences with it. I've been happy with my choice; C++11 improved the
language quite a lot and C++17 even further
Hmm I might consider it. I did a couple of small C++ projects some years
ago before C++11 but I would be
file back to OS X. I guess it depends on how
> complicated your network logic is.
>
> The Windows guys also did the same with the Windows version.
>
>
> If you have to write a C bridge to Go you might find doing it all in C
> works.
>
> Regards, Rob.
>
> > On
I much prefer the Microsoft approach here. I guess the lesson to be learned
is to depend as less as possible on Apple or either be forced to go through
all the frequent SDK and language changes.
I'm planning on working on a desktop project and looking for solution to
use Cocoa/Swift as less as
> That’s more open than Obj-C, because Apple never open-sourced Foundation.
AFAIK no Apple frameworks for Swift have been (or will be) open sourced
either.
> MSVC and .NET are both fully closed, as far as I’m aware.
.NET Core is fully open source:
https://github.com/dotnet/core
AFAIK Core is
> 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
> It’s better for Apple as a company, but personally, I’d rather be able
to upgrade my devices.
It's also extremely bad for the environment.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
amp; half Cocoa. It took a couple releases for
>> it be all Cocoa. Not to mention Carbon was officially deprecated in 10.8
>> (back in 2012) and is only now dead in 10.15 (2019). So I think Cocoa
>> still has a good number of years of life left before it is deprecated and
>&g
> 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)
before it is deprecated and
> even more years before it is dead.
>
> —Rob
>
>
> > On Nov 14, 2019, at 12:30 PM, Pier Bover via Cocoa-dev <
> cocoa-dev@lists.apple.com> wrote:
> >
> >> Well I think the point is to go SwiftUI
> >
> > What if you w
I won't respond each of you one by one but here are a couple of
observations.
Metal is not a cross platform technology hence why so many projects still
rely on OpenGL in macOS (eg: Firefox).
I don't understand those "the writing was in the wall" type of comments.
Even if you think something was
>
> I, for one shuddered when I saw “if let x = y” being something that people
> are expected to use and that damn, “you must unwrap this optional”, simply
> ends up making things that were simple in Objective-C, completely
> cumbersome in Swift.
>
Totally agree... I've only used Swift on one
>
> These days, Cocoa is pretty much the only tool that creates native
> software for Apple hardware.
There's iOS too which has a lot more devs (outside from Apple) than macOS.
No wonder Apple is "merging" the two SDKs (SwiftUI, Catalyst, etc).
___
>
> This is how you move towards a solution.
>
> https://developer.apple.com/account/#/feedback-assistant
>
> https://developer.apple.com/account/#/forums
Good luck with that. I've been using OSX/macOS since the Panther days and
quite frankly I don't think Apple cares.
I've submitted dozens of
> When/if Apple decides to deprecate Cocoa they will announce it many years
ahead of time
Like they did with 32 bits and OpenGL deprecation?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments
> Its not Apples fault if you were not aware. They were both highly talked
about during their respective WWDC events.
The vast majority of developers do not go to the WWDC and do not have time
to watch the dozens (hundreds?) of hours of videos to maybe find something
relevant about the future of
> Perhaps Apple does not want to give away the Crown Jewels.
Indeed.
There is some stuff in there that AFAIK no one has been able to replicate.
For example Imagix is a company that does image transformation in the cloud
and uses macs because of the high performance of CoreImage (
> But once you get experienced with Cocoa and Objective-C, you can build
applications or rewrite them fairly quickly, IMHO.
Yeah but Objective-C is slowly being phased out. Someone from Apple already
said in a previous e-mail newer APIs are only available for Swift.
As for Cocoa it seems like it
>
> Builders are mobile, and would love access to the accounting file in the
> office. Those apps will each do just one thing (e.g. enter a purchase or
> check an estimate).
I know this is the Cocoa devs list... but why not make a website?
It would be easier to develop, completely
Yeah I think Apple saw Obj-C as a barrier for developer adoption. I don't
think that's too far from the truth considering the emphasis on teaching
Swift to young devs, Playgrounds, the marketing about teenagers making
their first app, etc.
Swift has its quirks but most people around me prefer it
21 matches
Mail list logo
