Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
X GUI

X11R6.4 And Apache On Mac OS X Beta 121

Posted by Hemos from the getting-x-to-work dept.
Adam Attarian writes: "Tenon has released public betas of two new products for Mac OS X, XTools, an X-Window Server/Desktop based on X11R6.4. They integrate it with Aqua using both Cocoa and QuickDraw, with OpenGL support planned (the screenshots are cool, very cool). Also out in public beta is iTools, an Apache Port, that looks to have all the goodies like sendmail, DNS, and SSL. Now, if only we could get an AltiVec dnet client for X..." I should have been more clear - you can order this stuff right now - but their site so slashdotted, you can't really get through.
This discussion has been archived. No new comments can be posted.

XFree86 and Apache for Mac OS X Beta More

XFree86 and Apache for Mac OS X Beta

Comments Filter:
  • The X Server doesn't magically Aquify your X apps.
    You will still get plain old X apps running in an
    Aqua window manager.

    Now, they could Aquify the GUI toolkits (ie: GTK+ or Qt) and allow you to port apps to MacOSX (as opposed to just using an Aqua theme XClient-side).

    They could Aquify the Athena widgets too.

    Could they capture Xlib calls and output PDF based on that?

    Could they provide optional Anti-Aliasing of text and line-art on a per-program basis (in case its screws up some programs)?
  • Rapid porting of all existing X11-based apps ?
    --
    The world is divided in two categories:
    those with a loaded gun and those who dig. You dig.
  • No, its a requirement for a lot of people. The biggest use for a computer I've got is to work from home. In order to do that I need to be able to run as a terminal for X applications. There are many others in a similar position.

    I do other things with computers, but the main one is to save me from dragging myself into work on a weekend or after hours.

  • I'm sure Bill Gates is laughing his ass off.

    Where do you get your acid?

    If there's one inconsistent platform out there, it's certainly Windows. Even in the same version (ommit the pletora of conflicting UI from their pletora of versions of Windows), applications are always different.

  • Price? (Score:1)

    by djweis ( 4792 )
    That's pretty steep, they must be working with Xig (see yesterday) to set prices. It bothers me that Apple didn't include an X server, since it is Unix underneath all the fluff.

    This would be a good project to put up on cosource.com [cosource.com].

  • There was an NeXT-savvy (as opposed to merely friendly) version of GNUEmacs, I believe. It should pretty easy to take that code and make it work with Cocoa, avoiding the need for an X server to do the GUI integration.

    Until then, most folks will just run it in Terminal.app.

  • All X applications still have to formulate their drawing commands into X drawing commands and pipe them through the high-speed local socket. The local X server then has to read the command from the input, decode and interpret them, and then call its API calls to draw them.

    Actually, no, that doesn't need to happen. What happens is this:

    The application code uses the API to put a call to an X11 library's code, and the library takes implementation-specific steps to get carry out the application's drawing requests.

    All of the overhead that you've mentioned is really an implementation issue; there's no reason that an X library can't be written that will forgo X11-protocol-usage and just draw to the screen.
  • ... Mac OS X will eventually displace Linux and *BSD and GNU and other Free Software that chooses to duplicate rather than evolve....
    As we can see, the Free Software groups just attempt to reimplement what's been done in commercial software.

    Have you read anything about the HURD?
    GNU really isn't just a reimplementation of any OS that I've ever seen--it may be POSIX-compatible, but it sure as hell isn't unix.
  • Good lord, man, have you used X11?

    Long enough to make me wonder why, to this day, Microsoft and Macintosh haven't implemented something as useful. X may not have a lot of pretty client apps or great games, but it's one of the most useful things I have on my boxen. Being able to use graphical apps from my laptop by displayed on my desktop or vice-versa is such a godsend that I don't want to live without it. That's one of the main reasons I use UNIXen at home rather than Windows or MacOS.

    It really is neat stuff.

  • Do I need to display remote apps? Not often. Even then, most of the time a terminal will do. I would like to see something for Linux much more Win/Mac like - a fast, no-network-bullshit display system. If I want to run remote apps, I'll start an X server similar to X-Win32 or MacX.

    Which brings us full-circle again, because that's exactly what this app is: a sort of "MacX for Aqua". It doesn't replace the existing MacOSX desktop, but merely allows X11 clients to display on it. I'm sure we all agree something like that is handy.

    There's room enough for both sorts of displays, I think.

  • As I recall, all program linking does is pull a copy of the application over the network and run it locally; it doesn't run on the remote machine.

  • the fact is you still have a video server on OS X

    Yes, you do. No, it has no compatibility whatsoever with X11.

    Unfortunately, there isn't mention of compatibility issues with "X" applications

    That's because there isn't any.

    it would seem that since Apple is claiming "Unix-savvy" for this OS, there would be at least some level of compatibility

    For someone who nitpicks other people's grammar, your own grasp of the English language seems a little...lacking. Anyway, Apple isn't claiming that OS X is "UNIX-savvy" (whatever that's supposed to mean), but rather that it is (reasonably) POSIX-compliant, which comes from the BSD-based bottom layer of the system (Darwin), which has absolutely nothing to do with what variety of graphic interface they provide with it. Their implementation has ZERO support for X.

    But please, don't let your lack of clues stop you from posting...


  • Program Linking allows a server to run on one machine, and a client to connect to that server. The client application is running on your Mac, the server application is running on the other Mac, and they talk.

    There is no MacOS equivalent to the "Run on one machine, but display on another" model that the X Window System uses.
  • Are we going to be able to compile (and therefore have MacOS X targets) these niffy tools like we can on our Linux boxen? I'd really hate it if we had to wait on someone else for new versions of this stuff. Maybe I'm too used to having my niffy Linux box and upgrading with every new release of Sendmail. :)

    Pope Felix the Scurrilous.

  • An excellent counter-analysis!

    Given SGI's bargain-basement price, do you think that it would be cheaper to buy SGI outright and get the SGI Origin-class hardware outright or do the R&D yourself?

    What it mostly comes down is what is Apple going to do to grow their business? Regardless of how cool OS X/Aqua/Carbon/Insert-Buzzword-Here is, they cannot compete on price with x86 and will not get back into suit-n-tie type businesses anytime soon, barring an unexpected MS implosion.

    Apple has a hole in its product lineup -- they cannot expect to grow a niche market much beyond what they already control. They may grab the odd x86 Unix workstation in some environments, but without serious hardware support for servers and storage, they will remain a niche product.

    Buying SGI would give them an immediate entree to the high end and enable them to fast-forward the Macintosh platform as a low-to-mid server market where vendors like HP, IBM and Dell dominate as well as giving them scalability on the same (long-term, anyway) OS *across* the entire product line.

    It's not a perfect marriage. SGI is in tough shape. Apple's business is much more focused than it was, and adding high-end Unix to its traditionally low-tech userspace may be tricky.

    But unless Apple are willing to get into more than just selling new boxes to the people that already own Apple boxes, their growth will remain rather stagnant.

  • On the one hand you have the definition of the API or protocol, this may be well thought out or not. On the other hand you have the implementation of the protocol or API and this may be well done or not.

    A good protocol can feel bad if nobody has taken time to write good code for it. At the same time a bad protocol can feel good if it has been optimized to the point of perfection.

    This also goes to explain why one implementation of X11 is fast compared to another implementation on the same machine. If you aren't happy with the implementation improve it.

    Also as long as it doesn't effect the specification an implementation can always be optimized with causing too much grief. Now try optimizing the specification and just watch who screams!
  • I guess it would depend: do X apps run unmodified on OS X? (My guess would be probably not.) So if you wanted to run X apps, you would need an X server, right?

    Only Mac people would think it would be silly to run non-Macintosh apps on a Mac.

  • I got the screen shot to load finally. They're running GIMP and EMACS on OSX. This will definetly increase the usefullness and power of OS-X, because now X apps won't have to be rewritten to use the Aqua interface.

    Its making the machine much more workstation like. Its good to have all that scripting power like perl etc on a box. Scripts and remote control are the biggest failures of non unix OS (I know applescript , visual basic, etc.. but they're weak)
  • "Also out in public beta is iTools, an Apache Port, that looks to have all the goodies like sendmail, DNS, and SSL"

    Not quite. Apache, sendmail, dns, OpenSSH; it's already there in the OS X public beta standard installation. iTools is merely a configuration tool for the aforementioned software.

  • And besides... this isn't 1975 anymore. I think we can do better than blasting bitmaps across the network using a broken security scheme.

    Where did you get your information? The X Protocol sends raw bitmaps only in the case of a client server bitmap x-fer request (seminal transfer of an XPixmap, or an XImage XPixmap copy). Otherwise it uses other primitives like lines, rects, font glyphs, and server-side bitmaps (XPixmaps).

    The ratio of people dogging X11 to people who actually understand X11 hovers around 100:1. There is so much uninformed drivel regarding X11 floating around that zero productive criticism of X11 can actually be accomplished, these days.

    X11 would benefit from a new imaging model, something akin to SVG or PDF, much like Quartz or Display Postscript. Unfortunately, the bulk of graphical computing applications on *all* platforms is adapted to the old, limited model of the original X11. What you don't seem to recognize is that X11 survives precisely because of the abominable state-of-the-art in GUI technology (again, on all platforms).

    Your precious Quartz might have changed that, except that it's owned and developed by Apple Computer. That, in itself, is a death warrant for promising technologies.

    MJP
  • when i typed 'where perl'

    goodbye Sherlock, hello Grep !!

    Now i just gotta hijack those Darwin tools.
  • i've been tooling around with OSX at work for the last few days, and i've noticed something distressing which i have heard no news or indignation about: gcc is missing, gone, completely not there. as far as i can tell, there is no way to compile on this thing. why has there been no press about this? has no one noticed this besides me? comments? thoughts? death threats?

  • Or like saying "Linux runs on Intel", and "Windows runs on Intel", so that implies "Linux runs on Windows". Except that's actually sort of true, since there is VMWare...

    To really confuse things, now you can (theoretically) get MS Office on MacOS X by running it under Wine under X under MacOS X. An interesting alternative to simply running the native Mac version of Office. To confuse things even more, just add SoftWindows and VMWare somewhere in the above chain. :-)
  • Oh, I never thought MacX for Aqua was a bad thing...I was arguing the "goodness" of X...I just think it can be done better ;-)
    --------------------------
  • And since X is a protocol, it is neither slow, buggy or holding anything back any more than HTTP is slow, buggy or holding the web back.

    Good lord, man, have you used X11?
    --------------------------
  • X has a cool concept. But if it ever wants to be used by the masses, in needs some reworking.

    Windows and MacOS are significantly better (IMHO, YMMV, yaddah yaddah yaddah) than X because they simply do things faster. X with all its networking overhead makes an inefficent desktop.

    Do I need to display remote apps? Not often. Even then, most of the time a terminal will do. I would like to see something for Linux much more Win/Mac like - a fast, no-network-bullshit display system. If I want to run remote apps, I'll start an X server similar to X-Win32 or MacX.
    --------------------------
  • Yes, I have used it. Aqua is pretty, but I'd prefer a different theme.

    But I'm wondering what the point of your comment is....
    --------------------------
  • VNC (there's a java client which should run under MacOS X as well)

    Actually, it runs suprisingly well under Mac OS 9 with IE5.

    - Scott
    ------
    Scott Stevenson
  • You have your facts backwards La-Z-Bastard.

    Tenon actually had their iTools product BEFORE Apple introduced their iTools shwack.

  • Why not the Macintosh (OS X) Foundation Classes ?
  • Yeah, that was the joke. I had a <g> written in, but forgot it was HTML formatted.
  • You can EASILY recompile apache under MOSX. YOu can either just drop your version into /usr/sbin/apache or you can work for it a little and compile it so it exactly replaces the built-in installation (the target directories are a little different than in the stock install). Neither option is particularly hard if you're worth your paycheck as a hacker.

    As for adding mod_perl and php support: it's trivial for the first option I described and it should be *fairly* trivial for the second option (I am doing it this afternoon, if all goes as planned)
  • You mean like Gimp? I guess there is truth in some advertising...
  • An Altivec GCC is available from here [altivec.org]. It works, but you may need to put your own headers in place in some instances. You have to sign up for a mailing list to get access to the archives.

    but - don't bother buying a G4 just for Linux. I have a G4 Cube at 450MHz. Although the system is good, reasonable video, silent except for the hard disk, the much-hyped G4 is at most 60% of the speed of my 800MHz Athlon, and of course cost more. Also, unless someone knows of a driver, the cool speakers it comes with don't work except under MacOS. Great keyboard though.

    Apple's much-quoted benchmarks may be true for Photoshop, but not for compiling a kernel.
  • You can compile Java natively on Mac OS X, can't you? And do something to it (Swing?) to get it to use Aqua? I think when you do this it looks and acts just like any Mac OS X native app.

    I'm not that into Java, but I keep seeing things about Mac OS X's Java support that sound like it goes above and beyond the call with Java. Maybe that's what Tenon is referring to.

    Also, there may be Mac users who want to run this stuff, but are happier to pay Tenon a modest fee to deliver it already working, rather than have to mess with anything themselves.
  • Apple developers have had their CD's for about a week now. It's a two-CD package: one is Mac OS X Public Beta (same as what users get when they order from Apple) and the other is all of Apple's development tools and some documentation.

    The Apple Select developer program is pretty good. For $400 (used to be $500) per year, you get 5 "seed keys" which you can pass on to free-membership developers, so you get 35 CD's a year and access to streaming video of WWDC and such, while your four friends get all the beta software and developer tools mailed to them. You and four other people could have been running Mac OS X since DP2 for $100 each, basically. Most people see the $400 or $500 and don't realize you're really signing up a workgroup.

    And yes, you can continue to develop for Linux or whatever for free, but you can charge more for your Mac software, so $400 per year is not that much. Also, you get a coupon for $100 off CodeWarrior as well, and discounts on hardware and software, and access to Apple's testing labs and things like that. If you have Mac OS X titles, Apple also has all kinds of cross-promotion things, where they'll feature you on their Web site or whatever.
  • The previous poster is right - Aqua is just a theme. But if you substitute MacOS X for Aqua...you're still wrong.

    It's kinda like saying Netscape Navigator runs under Windows, and Microsoft Office runs under Windows, so that implies Microsoft Office on Netscape Navigator.
  • Actually, all that good scripting power is already there in the default install. Well, at least TCL is for sure, I beleive Perl is as well. Even if it isn't, you can install it with very little hassle and run it from the included terminal window. And the remote control (ie: telnet, ftp) is disabled by default, but is extremely simple to activate. Voila - both of your "biggest failures" removed. 'Course, MOSX isn't a non-unix OS...it's a non-XWindows OS.

    You don't need XWindows to run the overwhelming majority of these scripts. About the biggest limitation I've found so far is the inability to run TK. It'd be a bear for someone to port,
  • Why would X running under MOSX be any more of a threat than Linux running on the PowerPC? I think the previous poster hit the nail on the head - there is a significant difference in skill set.

    The majority of Mac users don't give a damn about the techy details slashdotters hold so near and dear - they just want to get their email, surf the web, print pictures of their newest nephew, and maybe edit a newsletter or two. Without crashing. Whatever gets them that is fine.

    I can't see masses of Mac users suddenly moving over to a platform that requires so much more of them simply because python is available. Remember - MacOS 9 already offers power tools (perl, AppleScript, Webstar server) - but *very* few Mac users ever delve into them.
  • Um....nothing runs on Aqua. Aqua's just the name of a theme. A very deep, well integrated theme, but a theme nonetheless.
  • Anyone in need of some karma?

    Tenon is being /.ed, someone mirror the d/l's please 8^)
  • Well, that's a perfect opportunity to create a new a/c and start whoring all over again! Isn't it?
  • Comment removed based on user account deletion
  • *Real* Mac Crumudgeons barely accept the novelty of OS 7.1 and have no intention of moving beyond it!

    Some part-real part-synthetic Mac Crumudgeons accept 7.5. Only simulated Mac Crumudgeons accept OS 8.1 and/or 8.6. *NO* Mac Crumudgeons of any stripe accept OS 9!

    I don't diagree with the general tone of your statement, but please get your facts straight! OS 9 is the up-to-date latest and greatest release OS from Apple. Crumudgeons wouldn't touch it with a ten foot pole.

  • Mac OS X already has its own GUI framework, and there is absolutely no way that X could improve upon that. After all, the Mac GUI has always been its main selling point, whereas X is roundly, and deservedly, slated as being slow, buggy and holding back Linux on the desktop.

    I honestly don't see the point in this. Surely it's not progress, it's going backwards?

    The point is to give OS X users the ability to run legacy X11 apps, and to display X11 apps that are running on remote machines.

    Just to make it nice and sparkling clear: This is not a replacement for Aqua. This X11 server will run under Aqua, and allow you to display X11 apps side by side with normal Mac applications.

    X11 is nasty compared to a real GUI, but the network transparency is damned nice when you need it, and there are a few decent X11 apps around.

  • Scripts and remote control are the biggest failures of non unix OS (I know applescript , visual basic, etc.. but they're weak)

    Actually, Windows and the Mac are both way ahead of Unix when it comes to scripting of graphical applications. Unix makes it easy to glue together a lot of little command-line tools. Windows and the Mac both have systems that make it relatively easy for graphical applications to expose interfaces so that they can be scripted (without having to include a whole scripting language interpreter and system). Unix doesn't really have anything comparable, yet. Gnome and KDE are working on it, but neither is as mature or as ubiquitous as the Windows and Mac solutions.

  • As one can imagine, this is both good news and bad news for Apple They undoubtedly welcome this product as it gives the connectivity they so sorely need; particularly in their important scientific research market where they're already fairly popular. On the other hand there is likely a fear that developers might 'port' to MacOS X by simply running their apps in a X term session (possibly a cut-down server licensed from Tenon) and not go native.

    I'm not so sure that Apple has much fear that this will happen. The reason? Apple isn't including the X Server with OS X. If you try to sell software to someone and require a 3rd party product (especially one from a fairly small company) you're asking for trouble. First, people are hesitant about installing more stuff on their computer (maybe OS X will make this better, but I doubt it), second, their support department will be driven crazy by compatibility/version problems (are you running Tenon X? XFreePPC? Which version?) and third, companies worry that the 3rd party might go out of business leaving them in a bit of a bind. It's hard enough to deal with the foibles of different versions of an OS (and, yikes, MS makes it truly annoying by upgrading the OS everytime you install a new browser or word processor).

    I'm not saying that there won't be companies that take this route, but that the vast majority won't and this is enough to make Apple not worry so much about this.

  • I got the "Unix-savvy" quote right off of Apple's web site. Check it out here: http://www.apple.com/macosx /te chnologies/inside.html [apple.com].

    Anyway, I admit that I stand corrected regarding the X server; I mistook "X server" to mean "video server," which is (now that it's been pointed out to me) obviously not the same thing. My apologies to any I offended; I'll go flog myself with a wet noodle now. ;)


    Your Friend,

  • Or does this seem a bit silly to port Xfree86 to OS X?

    Apple did a lot of work to get their X server working, and from what I've seen at a couple of expos (don't have a Mac at home to test it myself, yet... :( ), it's damn smooth.

    If Apple would only open the source for their video server... Now that would be cool.


    Your Friend,

  • Umm... You can still open a terminal and run in that mode under OS X. Xfree86 doesn't mean "ability to use a terminal;" it's an X-session driver/server.

    If Apple already has included such a driver/server, why is it a "requirement" to port another? Of course, as I said, I haven't had the chance to fully test it, so I can't speak for the compatibility of X applications. If, for whatever reason, you can't run X apps on OS X (which seems highly unlikely from all I've read), then I can see a reason to bring on Xfree86. Otherwise, I can't see much point (not counting the "free software/open source" argument; which is valid for some people who feel strongly on those issues).


    Your Friend,

  • Apple DOESN'T HAVE AND X SERVER!!!! MacOSX has NOTHING TO DO WITH X WINDOWS.
    I know that OS X doesn't mean "X-windows," and that, in fact, the "X" is the Roman numeral "10," which is what release the Macintosh OS will be. And I am positive they don't have "AND X SERVER," whatever that means. As always, don't let your lack of English grammar prevent "u" from posting...

    But... the fact is you still have a video server on OS X (which, I admit, I may have incorrectly referred to as an "X server"), and the ability to run a CLI (a first for Macs).

    According to the info available at apple.com [apple.com], OpenGL will be supported, along with built-in support for PDF. Unfortunately, there isn't mention of compatibility issues with "X" applications (or at least, not that I could find). However, it would seem that since Apple is claiming "Unix-savvy" for this OS, there would be at least some level of compatibility, even if you had to compile your applications yourself.


    Your Friend,

  • Actually the name of the app on the mac is Network Administrator. You can do screen sharing, it comes bundled with Appleshare IP v6. Works on 0S 9. Pretty speedy lil thing. Connect to Machine #1 and run the program from machine #1's hard drive. All memory and processor req's are from machine#1 Microsofts version of spirituality. ---------------------------------------------- "Double-click on the lifestone to attune your spirit to the lifestone."
    Microsoft's version of sprituality:
  • Umm... You can still open a terminal and run in that mode under OS X. Xfree86 doesn't mean "ability to use a terminal;" it's an X-session driver/server.
    I'm not talking about using a terminal. I'm talking about using a computer as an X terminal. There is a difference. A terminal is something you type commands or letters into. Maybe you want to run vi or something. An X terminal allows you to display X applications, such as a gui interface to it. MacOS X as released by Apple does not have this ability. It has a GUI but it is not compatible with X.

    If you're going to be condescending to people at least try and have a clue.

  • Windows and MacOS are significantly better (IMHO, YMMV, yaddah yaddah yaddah) than X because they simply do things faster. X with all its networking overhead makes an inefficent desktop.
    X has no networking overhead on your local host. Communication between the X client and the X Server is either handled through the loopback, or more commonly across a UNIX domain socket. This is very fast. Also, other protocols (such as GDI on Windows) also serialize their data stream -- so, the only difference between X and GDI (in terms of performance) is really protocol overhead, not the communications architecture.

    That said, X protocol is pretty brain damaged. NeXT had it right with Display Postscript, and now Apple has it right with DisplayPDF. Let's hope the GNUStep team completes their Display Ghostscript X server extension so we can all enjoy the benefits of DPS, for free. GNUStep is probably the most important and underappriciated Free Software projects around...
  • Er, insert the phrase "is faster" between LinuxPPC and Mac OS X server up there. I had a greater than symbol in there, but I should've realized that it's an HTML symbol. My bad.
    Haaz: Co-founder, LinuxPPC Inc., making Linux for PowerPC since 1996.
  • This is from Macworld Magazine's November 1999 review of LinuxPPC 1999 Q3. They did seem to miss the point in general, but found it (or part of it) in this line: >P> "The graphical interface was crisply responsive, and a informal test of the Apache Web server showed it to be considerably faster than Apache running under Apple's OS X Server."

    Now. This is not oS X final or the beta. Apple is probably going to spend a fair bit of money on the theoretical optimizations for the Mach microkernel that can (theoretically) make it faster. But, as far as the public knows, Linux holds the speed record right now.

    The review is at:

    http://macworld.zdnet .co m:80/1999/11/reviews/linuxppc.html [zdnet.com]

    That said, I am not against Mac OS X. I wish it the best of luck. I also would like to sell Linux for the Mac. ;-)

    Haaz: Co-founder, LinuxPPC Inc., making Linux for PowerPC since 1996.

  • "albeit slipping somewhat" ? Is that like "a little bit pregnant" ? Lets go for words like implode, power-dive, collapse, crash-'n-burn, etc. SGI has at this point been plundered, passed over, beaten-up, and now being sold off to anyone who wants some of the meat left on it's picked-over bones.

    Why would Apple, fresh from it's own brush with death want to purchase another ailing company, particularly one with such poor prospects?

    Apple has finally gotten it's hardware habit somewhat under control. The original lean line-up has now ballooned but at least almost everything is being based on common motherboards. SGI would bring in a completely different set of technologies with almost no common elements.

    Apple has also pared down it's software holdings. No longer does it try to compete with it's own applications but has spun off/shut down/de-emphasized most of those distracting and ultimately non-profitable lines of business. SGI would pull it back into those markets in a big way.

    Finally, Apple is once again focussing on profitable markets, one where it can sell either enormous quantities of hardware (iMacs) or fewer but highly marked up ones (Cubes.) SGI doesn't fit into either category particularly well, nor does it's own category seem much longer for this world.

    This appears to be a case of looking-for-a-buyer-for-SGI & not what-could-Apple-spend-it's-bucks on. Sure if gifted with SGI I'm sure Apple would be happy but $ for $ they'd be a lot better off spending their money on R&D to extend their own stuff into what's left of SGI's market.

  • Actually I was talking to the owner of a small software company that makes software for a niche market & this is exactly what was considered.

    Their application runs under BSD & 'till recently they've been requiring their customers buy a standard distribution. They've now expanded their support to the various free BSDs and are now considering MacOS X.

    As their customer base is non-technical folks with limited support resources something like MacOS X would seem a logical step. However they're unwilling to commit resources and fork their product until MacOS X has been out in the market awhile, appears successful & enough customers seem willing to adopt it.

    One interim strategy we discussed was simply continuing to run their application under an X Server and pretty-much ignoring the whole MacOS X-side of things until they've determined how far they want to go with this.

    Generally one can get a significant discount from MSRP if one licenses only the required parts of a product, limits it's use to running the licensed application, handles product support & is willing to include an upgrade offer in the packaging. If the X Server vendor is open to licenses like this then the cost per unit could be acceptable.

    Thus their product could ship almost immediately and with the exception of the added X Server install and some other "MacOS-X-ifications" (graphical installer, file locations, frameworks, icons) would be the same as their other releases. Indeed we guesstimated it would take 2 or 3 days to modify the unix side of things and another 2 or 3 to produce the MacOS X side.

    This is exactly the sort of thing Apple probably worries about. Ultimately it might be a win for them but in the meantime they'll have a quasi-ported-application runnning on their shiny new OS.

    As to concerns regarding the supplier, well, yours aren't new ones. Generally one can request an audit of the company to determine it's health, invest in things like a code-escrow policy, have alternative strategies in place (I expect there won't be one X Server vendor for MacOS X forever), etc.

    Finally these concerns are less strong then they might be otherwise as this would intended as an interim step. Should the product prove popular then the full port to Mac OS X would take place with the Aqua GUI etc. and then the licensed X Server could be dispensed with.

  • What exactly would buying SGI bring to Apple? Are these things Apple couldn't develop for itself just as cheaply yet apply across it's entire product line?

    Software-wise they're not a particularly good matchup. Sure they overlap in some ways but then almost everyone in that part of the market does.

    Hardware-wise they've very little in common. Where SGI does have 'kewl stuff' it's not particularly applicable towards Apple's current hardware base (that I'm aware of.)

    Customers, contracts, service & support, development engineers - SGI is hemmoraging all of those and again, none of them are very good matches for Apple's business model.

    What Apple needs now is to improve it's hardware and solidify MacOS X.

    In hardware Apple needs faster, more flexible motherboards. Faster CPU's would be great too but they can get away with dual (or more) PowerPC's as long as they're competively priced. Should PowerPC truly be stuck at a roadblock Apple could consider moving to Alpha. In no case are they going to succeed (ie profit) competing in the consumer or workstation x86 market - at least not in the near-future. Once the transition to MacOS X is complete and it's established Apple would do well to consider a Darwin-based x86 subset specialized for server duty, much like the MacOS X Server release of two years ago is used today but on a x86 hardware platform. I expect they'd treat it much like they do their '486-based AirPort today - the CPU is x86 but they don't make a big deal of it.

    OS X needs to get out in the market and establish itself as a Unix peer. Once it gets some creditability as a stable Unix vendors can start porting over Unix-apps to it and customers can start weaning off of the Classic/Carbon codebase. With this transition Apple could begin to move into some of the server market making the same arguments MS makes for NT: one OS scalable for desktop / workstation / server. They'd be able to come up to speed rather quickly in the server space as the developers would be simply performing another Unix port with some added UI work.

    Were I Apple i'd be looking to spend my money on a few things:

    • Improving the motherboard architecture. 100 MHz motherboard, ATA 100 drive connects, AGP 4x or 8x graphics, better built-in audio, etc.
    • Faster CPU's. 500MHz+ PowerPCs'. Two, four, even eight CPUs on a board. Possibly add Alphas to the mix.
    • Wooing developers to Darwin & MacOS X. Seeding hardware & software. Providing technical support where useful. Encouraging widespread adoption of MacOS X as at least an alternative for unix applications if not a preferred environment.
  • Damn - posted instead of previewing. Well, there it is, warts & all - you get the idea. Honestly I'm not terribly interested in pursuing this discussion much futher anyway. Apple buying SGI seems extremely unlikely IMHO and 'what ifs' aren't particularly engaging.
  • This is all well and good, but this program costs quite a bit of money, and for, say, educational and other use, I think it'd be really nice for a free X Server to be available for OS X. Does anyone know if there are any efforts out there to create one? (Afaik, John Carmack's project is for a complete X environment on top of Darwin, and not one that meshes with Aqua, which would be infinitely more useful.)
  • There is a major difference between implementing something clean and simple and something that is a complex mass of special cases. Yes, you still want X for a Mac, just the same as you want SAMBA for Unix boxes, but don't go thinking it's not a flawed system. X is an albatross hanging about the neck of the Unix world. It's a great example of how superior products can be crushed by flawed but free alternatives.

    Where, exactly, have I or anyone stated that X11 is without flaws? As I've said in another post, it has its share of warts but that's just the way life is. But the fact remains that it still just a protocol that anybody can implement with varying degrees of success. Perhaps one day a better windowing protocol (Berlin?) will supplant it like HTTP did to Gopher, but that day isn't here yet and the work continues.

    And even when something better comes along, X11 may persist just like Gopher sites can still be viewed with web browsers. Network transparency guarantees non-exclusivity, and that's also a Good Thing.

  • My main gripe is with those who parrot the same old "X is bad" line with the reasoning that "it doesn't look like Windows", "it has all sorts of things I don't understand" or "it doesn't work like the MacOS". I likely would've saved myself a bit of explanation simply by acknowledging that X is a system with warts aplenty but that it has benefits lacking in the current systems as well. But that was my mistake. X11 has its drawbacks, but it's not the root of all evil, either.

    As I recall, NeWS and Display Postscript were not open standards. That, more than anything, likely accounts for why neither is around any longer. Berlin is an open standard, but I'm discouraged by the slowness it's progressing and the lack of running client apps. A better "Kept Simple Stupid", network transparent, open, windowing environment would be a good thing to have, but it would have to be substantially better than X11 (probably not too difficult) and easier to use (both user-side and developer-side) in order to catch on. Unfortunately, we're not there yet.

  • that is why HTTP *has* been improved, persistent connections, etc, because as things scale it *does* hold back the web

    HTTP has been improved. So has X11. When the need calls for it, protocols get improved. If HTTP really were in need of dire replacement, there'd be a call for FOOTP to replace it. As of yet, I haven't seen such a desire.

    And besides... this isn't 1975 anymore. I think we can do better than blasting bitmaps across the network using a broken security scheme.

    Nobody's saying X11 is perfect. But it's here now, has *lots* of clients and it does exactly what it's supposed to. And since it need not replace an existing GUI, there's no reason not to implement it and enjoy X11's benefits on top of an existing GUI scheme.

    Perhaps Berlin will do an even better job, but it's not here yet and remains unproven. And in the meantime, X11 still works. To me, it seems like most of the "X11 is bad!" cries are from people who don't understand what it is and when benefits it has over the current schemes, which is unfortunate because neither Microsoft or Macintosh offers some of its greatest benefits. I'd hate to see the standard free graphical display replaced by something prettier but less featureful until the benefits of network-transparent GUIs are rediscovered all over again.

  • Tenon wants $199 for the product during the beta phase, and apparently plans on increasing the cost significantly thereafter. (The $199 will give you the release version at no extra charge if you pay when receiving the beta).

    Now, $200 is a healthy chunk of money. Even at OEM discounts, I don't think it's going to be attractive to port many applications relying on this type of support. So I don't think Apple has anything to worry about there.

    The big question is "When is carbonized Photoshop arriving?" - because until we get it, I think there will be at least some doubt surrounding the platform.

    Incidentally, I'm posting this from my Mac running OS/XBeta. If it weren't for the keyboard dropping characters all the time, I'd say it's darn near perfect other than non-support of video editing applications.

    D

    ----
  • As one can imagine, this is both good news and bad news for Apple They undoubtedly welcome this product as it gives the connectivity they so sorely need; particularly in their important scientific research market where they're already fairly popular. On the other hand there is likely a fear that developers might 'port' to MacOS X by simply running their apps in a X term session (possibly a cut-down server licensed from Tenon) and not go native.

    As I've already said [slashdot.org] and further explained [slashdot.org] this would dovetail nicely with an Apple purchase of Silicon Graphics, who already have a very strong presence (albeit slipping somewhat) in the high-end scientific/visualization environment that even the glorious G4 hardware cannot compete in.

    Mac interface zealotory aside, the ability to more-or-less seamlessly integrate MacOS & Unix X applications would make such a marriage an ideal thing -- high performance SGI enterprise-grade hardware for bigger jobs, iMacs or towers on desktops for local jobs and talking to the larger-scale machines.

    I think Apple should rush to support this. I agree they might be a little scared of people just running Mac apps over X and not going native, but without a high-end server lineup in their product mix this is going to happen anyway.

  • You add them just like you do with RedHat's installed apache under linux....

    (open terminal)
    cd php-4.0.2
    ./configure --with-apxs
    make
    make install
    apachectl restart

    and you're done. Of course, you can always reinstall, just specify --with-layout=(whatever layout they're calling it these days) if you want the same layout as apple's (which you probably don't because it puts stuff all over the place)

  • So I don't have to fire up VNC to get a remote display for my linux box when I work on my powerbook. I don't even have a monitor on my linux box, it's tucked away in a closet, and if I ever want a GUI there, I use VNC. It would be nice to just be able to export my display to my powerbook...
  • >. To me, it seems like most of the "X11 is bad!" >cries are from people who don't understand what >it is and when benefits it has over the current >schemes, which is unfortunate because neither >Microsoft or Macintosh offers some of its >greatest benefits Don't get me wrong.... no 'X11 is bad!' cries here. X lets me get a lot done..... BUT at the same time i refuse to agree with the standard ./ mantra that if you have X (specifically Xfree86) then life is complete. Nonsense. X has some huge holes in it, or at least limitations due to the era in which it was conceived. I don't advocate just throwing it away immediately, but the status quo isn't something that interests me.
  • >And since X is a protocol, it is neither slow,
    >buggy or holding anything back any more than
    >HTTP is slow, buggy or holding the web back. So
    >can we please stop with the "X is bad" rhetoric?

    huh? So a protocol in and of itself can't be good or bad? Come on.... (that is why HTTP *has* been improved, persistent connections, etc, because as things scale it *does* hold back the web)

    And besides... this isn't 1975 anymore. I think we can do better than blasting bitmaps across the network using a broken security scheme.

    (I'm not trying to upsell MacOSX by any means... but lets quit worshipping at the altar of X11. I mean, it gets the job done {mostly}, but it is LONG overdue for a replacement.)

    j
  • >Apple did a lot of work to get their X server >working,

    (I'm sorry but i just can't help the flame, but this is /.)

    Apple DOESN'T HAVE AND X SERVER!!!! MacOSX has NOTHING TO DO WITH X WINDOWS.

    But as always, don't let knowing nothing about the topic stop u from posting.
  • Or does this seem a bit silly to port Xfree86 to OS X?

    XFree86 was ported to Darwin, not Mac OS X. The difference is that Darwin had no graphics layer controlling the screen, much like Linux itself has no graphics layer controlling the screen.

    Tenon's solution is very different. It goes through Mac OS X's drawing APIs, while XFree86 controls the screen directly. The XFree86 port was to give people running Darwin, and not Mac OS X, a GUI (of sorts).

    Geez. This is only brought up in every single discussion thread about Mac OS X or Darwin since Carmack announced his intention to port XFree86 over a year ago.

    Apple did a lot of work to get their X server working...

    This X server is not made by Apple. It's made by Tenon. Also, Apple's current Display PDF system is not the same as an X server, if that's what you meant.
  • X11 is a protocol

    Why, yes. X11 is a protocol. So is Windows' SMB protocol.

    Being a protocol doesn't mean that it isn't inherently flawed. X11 and SMB are very much alike in the fact that they are a series of hacks, forced inconsistencies, and special cases for backwards compatibility. They are both dangerous to run in kernel mode because there is no clean way to implement a broken standard. You may eventually reach stability, but there will still be occasional "gotchas," and your code will never be clean and well designed.

    If you don't believe me, try actually reading some of the ICCCM standard sometime.

    Try reading some of the sections of the Unix-Hater's handbook dedicated to X, like this [catalog.com] one.

    If you honestly think that just because X11 is a protocol that it's not inherently flawed, then you obviously have never tried to implement someone else's protcol before. There is a major difference between implementing something clean and simple and something that is a complex mass of special cases. Yes, you still want X for a Mac, just the same as you want SAMBA for Unix boxes, but don't go thinking it's not a flawed system. X is an albatross hanging about the neck of the Unix world. It's a great example of how superior products can be crushed by flawed but free alternatives.
  • Yes, there is an overhead. All X applications still have to formulate their drawing commands into X drawing commands and pipe them through the high-speed local socket. The local X server then has to read the command from the input, decode and interpret them, and then call its API calls to draw them.

    The alternative is to have the application go straight to the graphics APIs and do it itself. There may be no network slowdown, but the above is a major slowdown. Even DPS had a slight slowdown on the local machine compared to straight rendering. Personally, I hope GNUStep takes off too. It would be good to see the UNIX world with a free, well written, exportable graphics layer.
  • Where, exactly, have I or anyone stated that X11 is without flaws?

    "And since X is a protocol, it is neither slow, buggy or holding anything back any more than HTTP is slow, buggy or holding the web back. So can we please stop with the 'X is bad' rhetoric?"

    That sounds an awful lot like you're saying X is good, which it blatantly isn't. X is bad. It's incredibly bad.

    Perhaps one day a better windowing protocol (Berlin?) will supplant it like HTTP did to Gopher, but that day isn't here yet and the work continues.

    What, you mean like NeWS or Display Postscript? Both lost badly to X in the days before it became a standard. Superior code does not equal inevitable domination. Just look at Windows. Just look at X. I really hope the Berlin project takes off, but don't hold your breath. X has shown an amazing ability to crush better written competitors because of its wider adoption and better availability. We'll see.
  • Sure, as long as you don't want to run Mac apps and Unix apps at the same time. Might as well dual boot into Linux at that point.
  • Duh. Why pay when you can get the crappy x-window interface for free?

    You can't run it at the same time as the Quartz graphics layer. This means you can't run Carbon, Cocoa, and Classic Mac OS X apps at the same time as X apps. You might as well dual-boot into Linux at that point. What's the point of having Mac OS X at that point?

    Duh. <g>
  • Apple's version is the modlules it comes with - while webdav is there, there's no mod_perl, no php, and no mod_ssl. God knows how you'd add them

    I'm pretty sure there is a mod_ssl, actually, but it's disabled by default. OpenSSL, along with OpenSSH, are preinstalled on the machine.

    Anyway, you add modules via Apache's DSO mechanism. If you're not famliar with this concept, the idea is that you only compile the module without recompiling apache. Only problem is, you still need compilers. This is why I putting up a page [mac.com] for people to download DSO modules precompiled for Mac OS X/Darwin. All they have to do is drop the file in and modify /Library/WebServer/Configuration/apache.conf.

    - Scott

    ------
    Scott Stevenson
  • And since X is a protocol, it is neither slow, buggy or holding anything back any more than HTTP is slow, buggy or holding the web back.

    Actually, some people do believe this to be true. Who says a protocol can't be bad? And who says there isn't room for a better protocol than X?

    - Scott

    ------
    Scott Stevenson
  • It bothers me that Apple didn't include an X server

    That would be a huge, huge mistake. The current Mac people would be expected to run X11 apps instead of Aqua apps. That would be a UI disaster. Very, very bad.

    - Scott

    ------
    Scott Stevenson
  • Apple is probably going to spend a fair bit of money on the theoretical optimizations for the Mach microkernel that can (theoretically) make it faster. But, as far as the public knows, Linux holds the speed record right now.

    Mac OS X public beta is considerably faster than even DP4, both of which run Mach 3.0. OSX Server has Mach 2.5 and display postscript, amongst many other differences. Mac OS X public beta and Mac OS X Server can't really be reasonably compared in terms of performance.

    No doubt that LinuxPPC is fast, though.

    - Scott

    ------
    Scott Stevenson
  • Actually, all that good scripting power is already there in the default install. Well, at least TCL is for sure, I beleive Perl is as well.

    Perl, TCL, Java, tcsh, all preinstalled. Along with OpenSSH, OpenSSL, Java2, WebDAV and the newset version of Apache.

    - Scott

    ------
    Scott Stevenson
  • I have Tomcat running under OS 9

    But Mac OS 9 doesn't hava Java 2 support, which is required for JSP 1.0+. How'd you do it?

    - Scott
    ------
    Scott Stevenson
  • And why the hell can't Apple ever name anything that gives you an idea of it's purpose instead of giving it some cute nickname?

    Like GNOME?

    I'd rather have a cute nickname than a widly out-of-control buzzword fest like:

    Java 2 and Objective-C API Set for Mac OS X

    ...

    Pro Enterprise Edition.

    - Scott

    ------
    Scott Stevenson
  • Is webdav there? How do you turn it on?

    Apparently, you can mount WebDAV volumes on the desktop by just entering the address (http://webdav.company.com) in to the "Connect to server" dialog under the Go menu in the Finder. As far as turning on your own WebDAV server, I suppose you can turn it on by just uncommenting these two lines in /Library/WebServer/Configuration/apache.conf:


    #LoadModule dav_module /System/Library/Apache/Modules/libdav.so

    #AddModule mod_dav.c


    Save the file, restart Apache. I haven't tried it, but assume it will work. All the appropriate files are there.

    - Scott

    ------
    Scott Stevenson
  • Why not the Macintosh (OS X) Foundation Classes ?

    MFC is already taken. ;)

    - Scott
    ------
    Scott Stevenson
  • Good question; here's the answer. Any networkable machine can *run* applications that are located on another networked machine. You're right, it's as simple as filesharing.

    However, only X (to my knowledge) allows you to *display* applications that are being run on another networked machine. The distinction is that, while the application is running on my Intel-based system, it can be displayed on my Macintosh machine 1000 miles away. The benefits for remote-administration are substantial.

    -----------

    "You can't shake the Devil's hand and say you're only kidding."


  • You could always just run straight Darwin (by typing ">console" at the login window) and install XFree on top of that. Darwin binaries of XFree are at www.stepwise.com/Softrak, and FVWM2 and AfterStep have been ported to Darwin. Of course, you wouldn't be running Aqua underneath, but it's still cool, and it's free.

    I think it's only a matter of time till there is a free X Window Server for Aqua.

  • It's just you and a bunch of other /.'s.

    I use a mac. I use *nix. Being able to use both seamlessly on the same desktop is pretty freakin' cool. I can finally stop switching over to my linux box to run remote *nix apps or local *nix apps.

  • Now, if only we could get an AltiVec dnet client for X...

    The latest clients from distributed.net have Altivec support in both the OS X and OS 8/9 versions. 3.4 Mkeys/sec on my G4/400.

  • It's based on X11R6.4

    X opened up X11R6.4 a while ago. XFree86 4.0 is based upon it, so there is no reason why they couldn't port XFree86 4.0 to MacOS X.

    That said, it may be easier for them legally if they used the X.org's reference implementation.


    --
  • Yeah, LordDracula, try it sometime you have two X capable machines. Log onto machine one, type DISPLAY=host2.mylittlenetwork.net:0.0;export DISPLAY. Log onto machine two, become root, and type 'xhost +host1.mylittlenetwork.net' Then go back to machine one and run something. 'xclock &' and watch it either appear on machine two, or break horribly and display lots of horrible messages. And that's just the beginning of the KeWl ThInGs (tm) you can do with X....
  • Take a look at the info about iTools. Tenon has claimed to have ported Tomcat to OS X. The funny thing is that Tomcat has been running on OS X since it had Java support. Also consider how odd it is to have "ported" a Java program to another platform. I have Tomcat running under OS 9 and I also had it running under DP 4 back in June. Now I'm sure that Tenon has created a nicer interface to Tomcat, but to call it a "port" is wrong. Does anyone know if this violates the license that Tomcat is released under?
  • The majority of Mac users don't give a damn about the techy details slashdotters hold so near and dear - they just want to get their email, surf the web, print pictures of their newest nephew, and maybe edit a newsletter or two.

    A few of us also actually make a living with our Macs. But we do all those other things too. :P

    I imagine that the people disgusted enough with Aqua to even consider the kind of thing proposed by the original commentator will instead hold onto OS 9 until they drown with it. It won't be pretty, but so far it looks like they will be few and far between.

  • I thought the whole Open Source business model was "Sell the Support". It seems as if they are doing nothing more than that. Think of the word "port" as nothing more than something to mollify Mac users.

    Tenon has been selling Unix-on-Mac environments for a long time. Now that the Mac IS Unix, they obviously need to adapt their business model. One way is to adapt their GUI configuration tools to help protect the poor Mac users from the scary BSD layer. The question is, will Apple just beat them too it?

  • Mac OS X already has its own GUI framework, and there is absolutely no way that X could improve upon that. After all, the Mac GUI has always been its main selling point, whereas X is roundly, and deservedly, slated as being slow, buggy and holding back Linux on the desktop.

    I honestly don't see the point in this. Surely it's not progress, it's going backwards?

  • The letter 'X' (Score:4)

    by AstroJetson ( 21336 ) <`gmizell' `at' `carpe-noctum.net'> on Tuesday September 26, 2000 @03:31AM (#754465) Homepage
    This one article has caused the letter 'X' to move from the 24th most frequently used letter (in the English language) to the 22nd spot, surpassing 'J' and 'K'. If this keeps up, Huffman encoding will have to be completely re-written.

  • Your knot getting it write... (Score:4)

    by American AC in Paris ( 230456 ) on Tuesday September 26, 2000 @03:10AM (#754466) Homepage
    Attention, /. Editors:

    I have avoided a flame such as this for as long as I reasonably can, because I'm well aware that you are all human beings, that geeks are stereotypically bad in the grammar department, and it's generally not that big of a deal anyhow. However, the headline:

    XFree86 And Apache Or Mac OS X Beta

    is so wildly different in meaning than the proper headline of:

    XFree86 And Apache On Mac OS X Beta

    that it merits a bit of a slap on the back of the wrist.

    You, the /. Editors, run a much appreciated and much used online web service, and I am extremely glad that /. exists. I do not deny that you all have a whole lot of stuff that you need to tackle, and I do not think for one second that you are anything less than intelligent, inspired and driven individuals. However, the fact that single paragraph, front page articles regularly have the most basic of typographical and grammatical errors is cause for some embarassment, IMHO. Slashdot is recognized as one of, if not the premiere online geek news source. It's readership has grown to the point that only the strongest of web clusters can survive a fully-blown Slashdot Effect. Major international news sources (AP, Reuters) have begun referencing quotes and threads from Slashdot. Slashdot is now in the Big League(tm). Please, please put in that extra three miunutes of reading, re-reading and re-re-reading front page stories for typographical errors. Think of them as bugs in your code, and each front page post as a final version release.

    I know that you're proud of Slashdot, and you should be. It's an amazing website. But please, take the next step and start making the content delivery a bit more professional. It's easy to do, and it'll help make Slashdot a better news source.

    Trolls: If you must, go ahead and attack this post for typos and grammatical errors. I'm still in the process of learning this danged AZERTY keyboard, and there is in fact a difference between an editor-approved front page article and a comment in the attached thread.

  • Oh for goodness sakes (Score:5)

    by maggard ( 5579 ) <michael@michaelmaggard.com> on Tuesday September 26, 2000 @05:02AM (#754467) Homepage Journal
    How hard is it to look up something before posting? I mean, it's not like all of the relevant info isn't on the web or anything...

    Apple's MacOS X does not come with an X Windows server. Apple has no intention of developing or releasing such a beast. Apple instead chose to develop a PDF-based display system called "Quartz" upon which runs their UI named "Aqua".

    Tenon, a respected developer of Mac software, has developed an X Server that runs on MacOS X. This is significantly different from John Carmack's port of X to Apple's open-source OS Darwin (upon which MacOS X is based.) Tenon's X Server is driving the Quartz PDF-based display and utilizes the Aqua toolkits to produce a fully MacOS X-integrated display. In short anything run under Tenon's X Server is immediately available to the rest of the MacOS environment as just another PDF (cut-'n-paste, etc.) as well as appearing as Aqua-like as possible.

    Thus with Tenon's X Server one can run a generic X application and it will appear as simply another Mac OS X application obeying as many of the Aqua UI principals as possible. Indeed with many X applications trivial changes will be required to make them appear to be native Mac OS X applications (mostly menu placements, dialogue boxes, etc.)

    As one can imagine, this is both good news and bad news for Apple They undoubtedly welcome this product as it gives the connectivity they so sorely need; particularly in their important scientific research market where they're already fairly popular. On the other hand there is likely a fear that developers might 'port' to MacOS X by simply running their apps in a X term session (possibly a cut-down server licensed from Tenon) and not go native.

    As to Tenon's other 'ports' - are they ports? Likely yes. Getting a unix application, particularly one already native to BSD to run under Mac OS X isn't much effort, if any. Constructing a native user interface for it, while not very difficult, does take time and some (presumably) skill. Since we already talk of ports to other such brother/sister OS's the same would seem to apply here. The argument is strengthened with the added effort of creating an Aqua UI and integrating other Mac OS X conventions which Tenon has done.

    -- Michael

    No affiliation with any Mac developer currently, nor have I ever purchased any Tenon product. However I do look forward to running their OS X Server.

  • Re:Errm, why would you want X? (Score:5)

    by tuffy ( 10202 ) on Tuesday September 26, 2000 @02:51AM (#754468) Homepage Journal
    Let me make this very clear:

    X11 is a protocol

    By implementing an X server on top of MacOSX's GUI, X clients can connect to it. This allows all our current X apps to work, network transparently or even from the Mac itself. That is a Very Good Thing.

    And since X is a protocol, it is neither slow, buggy or holding anything back any more than HTTP is slow, buggy or holding the web back. So can we please stop with the "X is bad" rhetoric?

Slashdot Top Deals

FORTRAN is not a flower but a weed -- it is hardy, occasionally blooms, and grows in every computer. -- A.J. Perlis

Close