Writing Apps in Go and Swift

Re:Writing Apps in Go and Swift by Matthias247 on Tuesday January 29, 2019 @08:56PM (#19031902)

> Cocoa is incredibly fragile about the main thread

That basically applies to all UI framework. At least I'm not aware about one which provides good support for accessing it from another thread.

There is obviously a reason for it, which is that UI frameworks are incredibly stateful, and trying to manipulate lots of state from multiple threads at once rarely works out well.

[ Parent | on HN ]

Re:Writing Apps in Go and Swift by pjmlp on Wednesday January 30, 2019 @02:54AM (#19033427)

I think BeOS tried to and it did not went well with common threading issues poping up on BeOS apps.

Not sure if Haiku has any improvements regarding it.

[ Parent | on HN ]

Re:Writing Apps in Go and Swift by waddlesplash on Wednesday January 30, 2019 @01:59PM (#19038091)

Not sure what you mean when you say "common threading issues"; the entire point of the Be design was to force all threads to use message-based communication instead of shared memory for virtually all uses, and mandatory locking otherwise. It's extremely effective.

[ Parent | on HN ]

Re:Writing Apps in Go and Swift by pjmlp on Wednesday January 30, 2019 @02:30PM (#19038411)

It was quite common to see BeOS apps crashing due to not handling the threads communication properly.

Having the whole OS being so multithreading heavy was a novelty for the large majority of developers and quite easy to make mistakes.

[ Parent | on HN ]