[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> A lot of people would answer (and did) comparing to Apple and missing > features. I would to stress some pain points which we need regardless, What does it mean to say that something is a "pain point" and we "need it"? In general, I think of pain as something we would rather not have. > especially since it is my opinion that Apple is diverging and either we > get e.g. Swift in GCC or Clang or it makes little sense to pursue that > road too wildly, the future of Cocoa might be uncertain. It sounds like you are saying that GNUstep is good in its own terms, but without the compatibility we with recent Apple systems. Is that right? I have nnly the vaguest idea of what Swift and Cocoa are, so I can't really grasp the significance and implications of this. > 1) Continued GCC support, with (gradual?) adoption of features missing > in the runtime as well as bug fixes and certainty of support. This is an > important issue for GNU, or, as you know, we can only use clang for > them. We still support GCC, but it is not acceptable that it is stuck in > time. I consider it unacceptable that we depend on Clang for _anything_. But I don't know how to find anyone who wants to work on Objective C. To work on that part of GCC is not terribly hard. You need to learn only a small part of the compiler and a few of its data structures and interfaces. Would you like to give it a try? It sounds like GWorkspace has reached a good resting point, I can probably find a GCC developer to explain the data structures and how to operate on them. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
