• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cocoa/Windows parallel dvlpmt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa/Windows parallel dvlpmt


  • Subject: Re: Cocoa/Windows parallel dvlpmt
  • From: John Stiles <email@hidden>
  • Date: Tue, 3 Feb 2004 09:03:12 -0800

On Feb 2, 2004, at 12:54 PM, Alex Perez wrote:

While these goals may ultimately be achieved by the GNUStep project, it
seems to me that noone is really working on the Windows port right now.
This is too bad because it would make a wonderful porting base (a lot
of their code is mature).

I get real sick of people saying this. It's an open-source project! If
you're not part of the solution, you're part of the problem. Whiners
really ought to either (A) keep their opinions to themselves, or (B)
Contribute.

Oh please. Not all of us have the time to reimplement Cocoa from scratch.

I appreciate that open source doesn't write itself, but most of us are looking for stuff like GNUstep because we DON'T want to reinvent Cocoa by hand--we want something that already works! You can't fault us for that.

I'm a GNUstep user and know there's active development on the
win32 backend. The goal is "Stability First", so I think the old "put up
or shut up" adage rings true here. If Mac developers spent half as much
time contributing to GNUstep as they did whining about how much it sucked,
it'd be a world-class product!

Mac developers have no need to contribute to GNUstep. We have a better version already.

I think most cross-platform developers, like me, would rather just re-roll their interface code as native Win32 instead of investing the time in a second-class solution that will never look as good as a true Win32-native rewrite. If a goal of GNUstep were to mimic the l-a-f of the target OS instead of looking like Xwindows or something, then I think it would have a lot more appeal to developers of production-level applications. But most of us right now just write native code for each target platform, because that's what end users prefer. If the app you're writing is very GUI-intensive, you may make an abstraction layer or mini-framework that lets you spend more time in cross-platform land, but even that tends to cause little rifts where end-users occasionally get behavior that they wouldn't normally expect from their platform of choice.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Follow-Ups:
    • Re: Cocoa/Windows parallel dvlpmt
      • From: Alex Perez <email@hidden>
    • Re: Cocoa/Windows parallel dvlpmt
      • From: Philip Mötteli <email@hidden>
References: 
 >Re: Cocoa/Windows parallel dvlpmt (From: Alex Perez <email@hidden>)

  • Prev by Date: TableViewSelectionDidChange and Drawer Problems
  • Next by Date: Re: PROBLEMS POPULATING A POP-UP MENU IN A WINDOW
  • Previous by thread: Re: Cocoa/Windows parallel dvlpmt
  • Next by thread: Re: Cocoa/Windows parallel dvlpmt
  • Index(es):
    • Date
    • Thread