On Wed, Jul 15, 2015 at 12:49 AM, Keean Schupke <[email protected]> wrote: > > On 15 Jul 2015 7:37 am, "Matt Oliveri" <[email protected]> wrote: > >> Sneaky. But if the implementation is really open source, then I figure >> it should be legal to fork both the implementation and the >> specification of the language it's implementing. In other words, the >> community can fork off a community-controlled dialect if they want. >> The tough part is convincing developers to use the community dialect.. > > The tougher part is to convince Apple to use the community dialect, > otherwise you have the same situation as with Mono on Linux and C#, always a > second class citizen. > >> So yes, a modern language, well-supported by all major platforms would >> be great. Apple and Microsoft are probably not so dumb that they'd let >> it happen. (JavaScript doesn't count. Yuck.) > > Wishful thinking I guess. But it could be smart for them, as it would give > developers more time to write better applications. They can reduce costs by > sharing some of the development. We all save time and money, the economy is > more productive, everyone is better off and we will all be able to thank > Apple and Microsoft for making it happen.
Another issue is that it seems likely that most applications are going to rely on libraries (appkit for example) which are not open source... I could in general relate this to a fork of GNUstep which i've worked on, which moved ambient authority from the openstep specification (Foundation and AppKit libraries...) out into separate libraries, even though I could bring both sets of libraries together to have a complete AppKit/Foundation implementation, it required so many changes that it was impossible to bring changes in from upstream, thus the forking off point was essentially the point of starting a parallel development... With most of the developers merely concerned with compatibility with apple, only a few people were interested in this variation and we were unable to maintain pace, nor convince the upstream that it was a worthwhile replacement for the original rather than just needless complexity. So, it's not just convincing Apple to use the community dialect, but the apple community to use the community dialect, something I rather underestimated the difficulty of. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
