News for hackers. Stuff that matters.

A comment on Synchronous Messaging at Mozilla: The Decision. Parent comment

Re:Synchronous Messaging at Mozilla: The Decision by swiley on Thursday December 19, 2019 @11:23AM (#21836276)
Native development on OSX and iOS both kind of suck unless you completely embrace objective C and coaca. I think that’s what’s turned so many people off to it.

It’s comparatively easy to write complex portable applications with tk (or even just strait win32 and whichever X11 widget toolkit is your favorite.)

[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by shd4 on Thursday December 19, 2019 @01:51PM (#21837913)
https://github.com/neilalexander/seaglass looks promising.
[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by swiley on Thursday December 19, 2019 @11:11PM (#21841666)
That’s exactly what I’m talking about; you can’t reuse code on OSX and more or less have to start from scratch.
[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by saagarjha on Thursday December 19, 2019 @07:43PM (#21840800)
> Native development on OSX and iOS both kind of suck unless you completely embrace objective C and coaca.

You can try all-Swift development with SwiftUI.

[ Parent | on HN ]
Re:Synchronous Messaging at Mozilla: The Decision by swiley on Thursday December 19, 2019 @11:10PM (#21841660)
Well yeah that gives you an OS X app and you get to reimplement it completely from scratch for all the other platforms. So it’s exactly the same problem as objective C (except you can at least compile objective C on other platforms you just don’t get the GUI stuff.)
[ Parent | on HN ]