Slashdot Mirror


Apple Nearly Moved to SPARC

taskforce writes "Sun Microsystems Co-Founder Bill Joy claims that Apple nearly moved to Sun's SPARC chips instead of IBM's PPC platform, back in the mid-1990s. From the article: "We got very close to having Apple use Sparc. That almost happened," Joy said at a panel discussion featuring reminiscences by Sun's four cofounders at the Computer History Museum. An account of his entire presentation can be found on Cnet."

46 of 257 comments (clear)

  1. Dupe by FTL · · Score: 2, Informative

    Here we go again.

    --
    Slashdot monitor for your Mozilla sidebar or Active Desktop.
  2. Fine dining by Mostly+a+lurker · · Score: 5, Funny
    Sun Microsystems CEO Scott McNealy had to be wined and dined at a Silicon Valley McDonald's before he gave up his reluctance to help launch the workstation maker in 1982
    History does not record which of the many fine vintages available at McDonald's was selected on this illustrious occasion.
    1. Re:Fine dining by Neo-Rio-101 · · Score: 4, Funny

      So that explains the "Happy Meal Ethernet" driver for Linux on SPARC systems....

      --
      READY.
      PRINT ""+-0
    2. Re:Fine dining by Megane · · Score: 4, Informative
      Actually, "Happy Meal Ethernet" is the 100Mbit sequel to the 10Mbit "Big Mac Ethernet".

      static void happy_meal_tcvr_write(struct happy_meal *hp,
      unsigned long tregs, int reg,
      unsigned short value)
      {
      int tries = TCVR_WRITE_TRIES;

      ASD(("happy_meal_tcvr_write: reg=0x%02x value=%04xn", reg,
      value));

      /* Welcome to Sun Microsystems, can I take your order please? */
      if (!hp->happy_flags & HFLAG_FENABLE)
      return happy_meal_bb_write(hp, tregs, reg, value);

      /* Would you like fries with that? */
      hme_write32(hp, tregs + TCVR_FRAME,
      (FRAME_WRITE | (hp->paddr ...
      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    3. Re:Fine dining by rubycodez · · Score: 2, Funny

      can I suggest the McMerlot, July was a truly remarkable vintage!

    4. Re:Fine dining by wildsurf · · Score: 2, Funny

      I think the iPod should have been called the MacNugget.

      --
      Weeks of coding saves hours of planning.
  3. almost ?!?!? by TTL0 · · Score: 4, Funny

    almost only counts in horseshoes and handgrenades.

    --
    Sanity is the trademark of a weak mind. -- Mark Harrold
  4. SPARC was the dominant chip at the time. by CyricZ · · Score: 5, Interesting

    For serious workstations, the SPARC was basically the dominant chip at the time. Indeed, it was at the top of its game. Even now we still see it used for mission-critical and high-performance tasks. So it's really no wonder that Apple would have considered such a switch.

    --
    Cyric Zndovzny at your service.
    1. Re:SPARC was the dominant chip at the time. by Frumious+Wombat · · Score: 2, Informative

      As I remember from running simulations at the time, the top of the game was IBM's Power, with DEC's Alpha close behind, then followed by SGI/MIPS. The MIPS R8000 was the first hard-core contender, but they were already having trouble keeping up with DEC/IBM. Sparc was on anyone's radar because it was cheap (relatively), and all of the software written for the previous 3/XX generation could still run.

      We used to be really psyched that the PowerMacs had a version of IBM's workstation chip inside (PPC 601/604 chips were in both PowerMacs and AIX workstations). A lot of people bought them for Mathematica as a result.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    2. Re:SPARC was the dominant chip at the time. by fitten · · Score: 3, Interesting

      Heh, the rumor was that SUN, before opening up the SPARC CPU, took it to Motorola and asked if Moto would build it. Moto looked at it and said, no, but we can make you something better, and showed SUN the 88k. Unfortunately, the 88k died but at least its bus lived on in the first PPC processors.

  5. Alternative Headline by Bloater · · Score: 5, Funny

    Sun Microsystems Boasts "We're not quite good enough."

  6. Good decision by lordholm · · Score: 5, Informative

    The SPARC V8 is quite clean and nice to work with, and is farley sane, with the exception of tagged arthmetics, the trap model and the visible pipeline, and missing standard interface to the MMU (yes I know of the ref-mmu).

    On the other hand, the SPARC V9 is a horrendeus monster thar is just plain scary when dealing with supervisor level code. IMHO the PPC64 is much nicer than the V9, in many aspects.

    But, on the other hand the PPC, has gone out of order, while the SPARC has stayed in order, making the CPU a hell to compile code for.

    Architecturally, the PPC is a slight bit nicer than the SPARC, and as a plus, the PPC64 was defined exactly the same time as the PPC32 was, and thus they (PPC32 & 64) are very similar.

    In my eye, it was a good decision to go for the PPC.

    --
    "Civis Europaeus sum!"
  7. Had the workstation vendors worked together. by CyricZ · · Score: 3, Interesting

    There has always been much speculation as to what the computing landscape would look like today had the non-Intel vendors worked together to produce a superior chip.

    Indeed, the combined talents of the Alpha crew from DEC, with the PA-RISC developers from HP, the SPARC group from Sun, those behind the MIPS at SGI and MIPS Technologies, and the PPC people from IBM, for instance, could have come up with a CPU that completely trumped what Intel was putting out at the time.

    --
    Cyric Zndovzny at your service.
    1. Re:Had the workstation vendors worked together. by dfghjk · · Score: 5, Insightful

      There's no reason to believe this at all. Adding more of the same level of engineeering expertise doesn't necessarily get you anywhere. Besides, it could be argued that all the processor groups you mentioned produced processors that were better than Intel offered at the time. They simply weren't enough better to make a difference. Odds are that combining the efforts of the competition would have made them all fail even sooner. HP joined Intel for IA64 and look where that got them.

    2. Re:Had the workstation vendors worked together. by dfghjk · · Score: 4, Interesting

      haha, Alpha had the grimmest, most threadbare instruction set imaginable. It's strength was it's ferocious clock rates that were enabled by abnormally deep pipelines and instructions that did relatively little (no integer divide!). The characteristics that Alpha had that caused it to be so loved are the same ones that cause the P4 to be so hated; relatively poor IPC, very deep pipelines, very high clockrates, huge caches to cover it's design weaknesses, and excessive power consumption. The love of Alpha was a cult. Yeah it was fast and 64-bit but it was a tremendous power hog for it's generation. No need to love Alpha. No one did but DEC.

      BTW, Intel didn't steal anything from Alpha for the x86's. It's owned the team at the time. Cutler didn't steal anything from DEC either. A person owns the knowledge and experience inside his head. I'm sure if there was evidence of theft it would have been dealt with. DEC was a dinosaur that wasn't showing any signs of interest in Cutler's continued work. He left to take up his projects at a company that was interested in pursuing them.

    3. Re:Had the workstation vendors worked together. by ACMENEWSLLC · · Score: 2, Interesting

      >>Indeed, the combined talents of the Alpha crew from DEC, with the PA-RISC
      >>developers from HP, the SPARC group from Sun, those behind the MIPS at SGI and
      >>MIPS Technologies, and the PPC people from IBM, for instance, could have come up
      >>with a CPU that completely trumped what Intel was putting out at the time.

      ROFL - that is hilarious. Can you imagine the politics in a chip like this? By the time the chip meets everyone at these companys requirements you would have a horrific chip.

      And as we all know, the chip itself really makes no difference. Look at x86 for example with all it's legacy routines that continue to haunt it. What makes the difference is marketing.

      Had any one of these chips had the proper marketing department and sales force, Microsoft would have an OS for it. I have an NT 3.5 for Alpha CD somewhere. They did write 3.51 for PPC and reportably SPARC, but didn't release SPARC.
      http://en.wikipedia.org/wiki/Windows_NT

      Novell 4.11 with NDS has features that Windows 2003 AD still doesn't have. For example, while I can mark a drive compressed on both OSes, on Netware I can configure it to compress the file only after not used after x many days. And I can tell the OS to leave a file uncompressed after use for y many days. I can mark a file as executable or not, such as with *nix. I can do bulk operations on the directory which I still find difficult with Active Directory. With some lesser known options, I can put the same user in multiple leafs in the tree to associate the same user with multiple departments leafs, applications leafs, or what have you. In AD if I put my user objects in department leafs, I can't associate GPO's to groups of users such as managers from each department. I have to create a subcontainer leaf and put managers in there and associate the GPO to each of these leafs. What a pain.

      Active Directory is still not where Netware NDS was 10 years ago. But that's not what matters. Marketing is paramount.

    4. Re:Had the workstation vendors worked together. by TheGratefulNet · · Score: 2, Informative

      No need to love Alpha. No one did but DEC.

      sgi (at the time, known as cray research) used alphas in their supercomputers.

      it kicked serious butt. and they were NOT DEC, last time I checked.

      (although sgi and cray will probably go the way of DEC, sadly to say).

      ob disc: I worked at both DEC and SGI in my past.

      --

      --
      "It is now safe to switch off your computer."
    5. Re:Had the workstation vendors worked together. by IntlHarvester · · Score: 2, Interesting

      Adding more of the same level of engineeering expertise doesn't necessarily get you anywhere

      It has nothing to do with engineering expertise -- it's FAB investment. None of the RISC companies could afford to keep up with Intel in process technology, and the enormous cost of designing and producing your own chip basically sunk DEC and SGI.

      I agree that it was probably politically infesible, but the RISC crowd invested far too much money into niche CPUs and it killed all of them (except IBM).

      --
      Business. Numbers. Money. People. Computer World.
    6. Re:Had the workstation vendors worked together. by poot_rootbeer · · Score: 3, Funny

      Indeed, the combined talents of the Alpha crew from DEC, with the PA-RISC developers from HP, the SPARC group from Sun, those behind the MIPS at SGI and MIPS Technologies, and the PPC people from IBM, for instance, could have come up with a CPU that completely trumped what Intel was putting out at the time.

      Hey, this broth isn't tasty enough! Better bring in a few more cooks...

    7. Re:Had the workstation vendors worked together. by IntlHarvester · · Score: 2, Insightful

      None of the RISC CPUs were binary compatible with the CPUs previously used by their sponsors.

      As for PowerPC, 970 wasn't that competitive with Intel's process, the chips were low-volume and ran very hot. But mainly Apple did it to themselves by creating a low-growth businss model that wasn't attractive to CPU vendors.

      > Would the joining of all the other vendors have changed that?

      No probably not, because Intel largely caught up. But it might have kept the RISC workstation/lowend server market alive.

      --
      Business. Numbers. Money. People. Computer World.
  8. Advanced Interface Design by DaveRexel · · Score: 4, Interesting

    -TFA-
    "McNealy added that he went to Steve Jobs' house to try to hammer out the user interface agreement. The Apple co-founder and CEO was "sitting under a tree, reading 'How to Make a Nuclear Bomb,'" with bare feet and wearing jeans with holes torn in the knees, McNealy said."
    ---

    From just this one anecdote one does get the feeling that Steve might have taken over Sun eventually. The disappointment expressed by Bill Joy over the failed "close encounters" with Apple does indicate that they would have followed Steves leadership.

    On a more serious note, the clash of the raging CEO egos would not have been beneficial for either company.

    --
    # ~: no sigs today
  9. Speculation that SGI would buy Apple. by CyricZ · · Score: 2, Interesting

    There was a lot of speculation in the early to mid 1990s that SGI would buy Apple. SGI was doing quite well at that time, considering they had just released their very successful Indy line. Considering that both provided workstations for the same type of applications (multimedia-related, desktop publishing, and so forth), the systems from Apple could have offered a solid low-end line to complement SGI's more powerful systems.

    What could have happened is an infusion of IRIX with Mac OS. We could have seen Mac OS on the MIPS, for instance. Not only that, but it would be a situation very similar to what we have now with Mac OS X: an excellent GUI built upon a solid UNIX-based core. Except in the SGI case the UNIX core would be IRIX, rather than a BSD/Mach conglomerate.

    --
    Cyric Zndovzny at your service.
    1. Re:Speculation that SGI would buy Apple. by jandrese · · Score: 3, Insightful

      It always strikes me that if you listen to the rumors, there is ALWAYS a company gearing up to buy out Apple for one reason or another. I don't know what it is about Apple, but people really want to see it bought by some huge conglomerate for some reason.

      I doubt SGI ever had any interest in Apple. They were positioning themselves in the server market at the time and Apple had nothing to offer them.

      Of course that was back when Apple was tanking and speculation that everybody from SGI to Microsoft to Pepsi was going to buy them out.

      --

      I read the internet for the articles.
  10. Lots of processors considered? by RetiredMidn · · Score: 4, Interesting
    I seem to recall seeing a demo of a Mac with a Motorola 88000 RISC processor running my 68000 binary code (Lotus 1-2-3) under emulation, a predecessor to the PowerPC effort.

    Oops, I may be in violation of an NDA...

    /. sure is a good place for dredging up obscure technical memories.

    1. Re:Lots of processors considered? by RetiredMidn · · Score: 3, Interesting
      Wasn't the "Star Trek" Intel port done at about the same time?

      Now that you mention it, yeah. We were given a separate presentation at Lotus about Star Trek, including a demo. (Damn, there goes another NDA.)

      To be honest, I remember thinking at the time that Star Trek wasn't really thought through. Certainly the execs at Lotus didn't get it (which says more about the execs than it says about Star Trek). DOS/Windows apps were not going to run under Star Trek (certainly not with the desired user experience). "Porting" these apps to the Mac OS APIs wasn't going to be all that easy. And converting Mac applications of the day, many of which were written in processor-dependent ways, to a new processor architecture would be much more difficult than the conversion of more modern applications today.

      It was neat technology, but it didn't solve a problem people thought they had.

      I kinda went off topic there; please don't hurt my karma.

    2. Re:Lots of processors considered? by RetiredMidn · · Score: 4, Interesting
      I always had the impression that Star Trek was dry run of their 68K emulator technology

      Interesting thought, but I really don't think so. AFAIK, Star Trek was not emulation; it was the Mac OS APIs recompiled and re-hosted on a different platform. I've seen conflicting reports about how it was really implemented, but (forgive me), Cringely's is the most credible, IMHO. It is possible they learned a thing or two that helped them with the PowerPC platform transition.

      And I suppose you could argue that if they were going to switch to Intel eventually, they should have done it sooner rather than later.

      Personally, I've never believed that. I worked closely with both the 680x0 and 80x86 architectures in the 80's, and, form my perspective as a user of the instruction set, I found the 68K vastly superior to work with; the only thing the Intel platform had going for it was the fact that IBM had made it a de facto standard.

      Architecturally, the Pentium started to close the gap, but the power consumption issues were pretty significant. My five-year-old fanless PowerBook G3 is still a pleasure to use over the Dell laptops my last employer supplied me with.

      IMNSHO, Apple's Intel switch wasn't inevitable, it just makes sense at the moment. And I harbor a suspicion that Apple won't necessarily stay mono-architectured. Mac OS X binaries, by design, can accommodate multiple (not just two) processor architectures. Apple will pursue the direction(s) that make the most sense as things play out over the next few years.

  11. Back in the day.. by turgid · · Score: 2, Interesting

    ...late '80s/very early '90s there was something called the ACE Consortium.

    This was formed by the likes of DEC, Compaq and SCO at the time when IBM had not long brought out the dreadfully underpowered, expensive and proprietary PS/2 line of personal computers running the pathetic MS-DOS and mediocre OS/2.

    Most people were running PeeCees which were essentially 16-bit with a single user, single tasking operating system running on dreadfully slow CISC (8086, 80286, 80386) processors will pitifully small amounts of RAM (512k-1MB) and nary a GUI.

    The ACE consortium was designing a MIPS-based (32-bit RISC) open specification for a replacement to the IBM-PC and PS/2 architectured which would run a UNIX SYSVR4 derivative and a nice GUI (was it with X?).

    The project died a death. I can't remember why.

    When I was 15 I longed for a RISC UNIX workstation in the house instead of the 12MHz Compaq SLT/286 we had (for business use).

    MIPS lived on in post-VAX pre-Alpha workstations at DEC and then at SGI. itanic Kool Aid all but killed off MIPS. The only two major RISC architectures from the era which survive are SPARC and POWER/PowerPC, and for a couple of years it looked like SPARC was dead too.

    The spirit of Alpha lives on in Athlon and Opteron.

    1. Re:Back in the day.. by dfghjk · · Score: 3, Informative

      First, when the ACE Consortium was formed Intel was selling 486's. The 486 was not dreadfully slow compared to RISC competition although its floating point lagged. Intel PC's also had far more memory than you suggest and Windows (even OS/2) was well established at that time. The competition for ACE was not 16-bit, single-tasking low performance DOS machines like you say.

      Second, Microsoft was a member of ACE and Windows NT was built to run on ACE machines as well as PC's. For those who wonder why NT/2000/XP boots the way it does, the reason is that PC's run special boot code that emulates an ACE bootstrap environment. It could be argued that ACE was the preferred platform for NT and MS internally built ACE workstations as reference platforms. Much of the NT code was developed on them. The ACE machines inside MS had EISA busses and used PC peripherals. ACE even included a spec that allowed ACE machines to use PC expansion cards with modified option ROMS.

      It's conceivable that ACE intended the workstations to run a UNIX derivative but I doubt MS saw it that way. It's far more likely, had ACE succeeded, that its main platform would have been Windows. ACE machines, despite their MIPS processors, ran DOS applications! Sorry, ACE wasn't a UNIX workstation, it was a PC replacement that ran MS OS'es in addition to UNIX variants.

      Now, about ARC---the PowerPC version of ACE...

    2. Re:Back in the day.. by turgid · · Score: 2, Funny

      My dad wouldn't let me have anything that wasn't "PeeCee compatible" since that's what all businesses and Right Thinking Folk(TM) used, even if it was technically inferior.

      I wasn't allowed an Amiga either (before the Archimedes came out)...

      He's still stuck on Windows and curses it every time I speak to him.

      I've been doing Linux and UNIX since 1995 (when I left home).

    3. Re:Back in the day.. by dfghjk · · Score: 3, Informative

      ACE was formed in 1991. At that time the 386 was dead and the 486 was available at 50MHz. The Pentium was introduced in 1993. It was superscalar and offered integer performance similar to the best RISC processors of that day, certainly faster than RISC from 1988! Such comparisons are silly. Incidently, the first Pentiums were 60 and 66 MHz. It took another cycle and a different pinout before the Pentium went 100 MHz.

      As for GUI's, OS/2 1.1 (the first with a GUI) was introduced in 88. Windows/386, the first fully virtual, fully preemptive version of Windows was introduced in 87. Windows 3.0 in 90 and 3.1 in 92. Windows was not the exclusive desktop at the time but it was certainly established. Compelling Windows apps that forced the PC world over to Windows started appearing around 92, not much after the creation of ACE. Word started dominating WP beginning in 92. There was still a lot of DOS use but the PC world was hardly as you describe (slow 286's and 386's).

      Memory cost the same for PC's as it did for workstations. If anything, PC's with their compact instruction sets and small footprint OS'es made better use of memory than workstations did. Don't know what your point is there. Workstations had more memory typically but they needed it and their prices reflected it. Business ppl didn't buy workstations.

      Claiming that the Athlon was substantially better than the P3 is silly. It had a slight IPC advantage and eventually a clockrate advantage, but the two designs offered similar performance. While the Athlon was introduced in 99, 8 years after ACE (not a good decade), the first of the P3 designs was introduced in 95, only 4 years after ACE.

      AMD's Opterons aren't Alpha's and it's a good thing. Alpha's sucked and the P4 looks much more like and Alpha than the Opterons do. DEC had good engineers and contributed nicely to the PC world, most notably with their PCI work, not their processor designs. They gave use PCI bridges and a nice ethernet controller.

      If we are comparing experience with these machines, my first PC was an IBM 8088 machine. I started work for a major PC manufacturer in 87. I did OS/2 1.0 and 1.1 work, UNIX systems programming and NT driver development. I did firmware programming work for that company starting in 88. My first machine there was a 10Mhz 286 and I used every type processor and most speed grades since then. I had extensive experience with the 960, Alpha, and PPC 603 in addition to all the Intel x86 processors. I worked some with the i860, the Moto 88K and the Itanium. I'm quite familiar with the history of the processors, OS'es and ACE. You can have your Slackware 486 machine. I got rid of mine long ago and wouldn't be bragging if I was still using one.

    4. Re:Back in the day.. by IntlHarvester · · Score: 2, Informative

      > There was still a lot of DOS use but the PC world was hardly as you describe (slow 286's and 386's).

      Turgid is right about this one. In 1991, there were still AT and even XT machines on the market, and 1MB would have been the stock RAM. The early 486 machines cost well over $5000 and it took a couple years for the chip to filter down to regular machines.

      --
      Business. Numbers. Money. People. Computer World.
  12. I hear.... by Slashcrap · · Score: 2, Funny

    ...that Sun are also considering switching to Sparc for their servers. You know, if things don't work out with the Opteron they need a backup strategy.

    I kid, I kid....

  13. a company of "almosts" by penguin-collective · · Score: 4, Insightful

    Sun almost created several great desktop window systems. Sun almost set a standard for web-based application delivery with Java. Apple almost picked Sun's SPARC architecture. Sun almost set the standard for server operating sytems. And then there are things that Sun achieved, briefly, and lost, like dominance of university departments.

    I leave it to others to diagnose the exact causes of Sun's repeated failures. I can say this much for myself: I won't buy another Sun product again, ever, nor will I ever trust any of Sun's promises again.

    1. Re:a company of "almosts" by Animats · · Score: 4, Insightful
      That's very insightful.

      Someone should write a book on how Sun blew it with client-side Java. They gave the product away and spent tens of millions marketing it. In a marketing sense, they succeeded; everybody has a Java interpreter on their desktop. Yet almost nobody uses them any more. Why?

      Part of the problem is that Sun's top technical people, including Joy, never really figured out GUIs. Sun went through three bad in-house window systems before finally giving up and going with X-Windows. Then in the Java era, they went through the AWT and Swing eras, both of which combine complexity with poor performance.

      So Sun ended up as a "server company", the place SGI went after they failed to survive the transition to low-cost graphics.

    2. Re:a company of "almosts" by Decaff · · Score: 2, Informative

      Yet almost nobody uses them any more. Why?

      You are wrong. Java client-side development is far from dead - it is growing, and at the end of last year overtook MS WinForms as the most popular client-side development platform in North America. There are even 'shrink-wrapped' commercial Java applications based on Swing that are amongst the best in their class (the financial package Moneydance is a good example).

      Then in the Java era, they went through the AWT and Swing eras, both of which combine complexity with poor performance.

      Easy to say, but wrong. AWT was not poor performance because it was the native GUI. Swing went through years of poor performance, but .... got better. Now it is hardware accelerated.

      It is easy to take cheap shots at a technology by on recycling common myths based on the way things were 4 or 5 years ago. However, to post facts it is a good idea to actually try the technology as it is now. Swing on Java 1.5 is neither memory hungry or slow.

    3. Re:a company of "almosts" by Hezaurus · · Score: 2, Informative

      >> Yet almost nobody uses them any more. Why?

      > You are wrong. Java client-side development is far from dead - it is growing, and at the end of last year overtook MS WinForms as the most popular client-side development platform in North America.

      Hey! You didn't count all the gazillions of mobile phones out there that all (well >95%) run java.

      > Swing went through years of poor performance, but .... got better. Now it is hardware accelerated.

      What you mean is that some of the drawing operations are accelerated. 1.5 is quite good and 1.6 will finally get rid of the famous 'gray rect' for good. Most of the components that are geared towards heavy use (e.g. JTree, JTable) are top performers already.

      The event handling framework is quite complex (you can do practically anything with it) and the fact that each java class behaves almost like a dynamically linked library in more static languages will keep the start-up performance forever behind.

      > Swing on Java 1.5 is neither memory hungry or slow.

      The memory usage hasn't shrank since I was introduced to java. The extra hit that comes from the VM and GC is major pain in small applications but negligible in bigger ones. Class data sharing for java's built in classes (introduced in 1.5) helps too little in that respect and I don't expect major improvements in that area, at least not in the near future. Speed is getting better and better with every release and I expect java 1.6 (Mustang) to finally put an end to this everlasting java is slow whining.

      --
      No matter how fast light travels it finds the darkness has always got there first, and is waiting for it. (T. Pratchett)
    4. Re:a company of "almosts" by Decaff · · Score: 3, Informative

      The event handling framework is quite complex (you can do practically anything with it) and the fact that each java class behaves almost like a dynamically linked library in more static languages will keep the start-up performance forever behind.

      You might think so, but it really doesn't. Try the following: Install a significant Java application like JEdit or Moneydance. Time it's startup. I typically get start-up times of 3-4 seconds. That is faster than most KDE apps on the same machine!

      The memory usage hasn't shrank since I was introduced to java. The extra hit that comes from the VM and GC is major pain in small applications but negligible in bigger ones.

      I don't find this. I can start up trivial Java apps in just a few megabytes, and even Swing apps like JEdit can run in 8MB. That is nothing on modern machines. As for the GC being a major pain - it can be finely tuned these days, so much so that real-time APIs can be implemented even on standard VMs.

      My impression is that performance and memory efficiency has improved significantly since Java 1.4.x.

  14. Re:Sun should port x86 Solaris to intelMac by turgid · · Score: 4, Interesting

    The main problem x86 Solaris faces is providing driver support.

    That problem is being addressed and started with the Solaris 10 project many years ago. Solaris 11^H^H Nevada will again be a vast improvement.

    Solaris 10 x86 runs better than Linux on modern laptops. Solaris 10 rules.

  15. Isn't that... by Black+Parrot · · Score: 4, Funny

    Isn't that kinda like "I almost got laid"?

    --
    Sheesh, evil *and* a jerk. -- Jade
    1. Re:Isn't that... by aztektum · · Score: 3, Funny

      In their last meeting, Apple reps. were rumored to have consoled them by saying, "Don't worry, it happens to a lot of chip makers."

      --
      :: aztek ::
      No sig for you!!
  16. Wouldn't Have Made a Big Difference by Alon+Tal · · Score: 3, Interesting

    Most probably, the only difference today would have been that we would be reading about Apple dumping _Sun_ for Intel, rather than dumping IBM for same. Reminds me of an Isaac Asimov story called "What If-", in which a newlywed couple meets a man who owns a gadget that can show them alternate realities, if key events in their past had taken a different course. For example: Would they be married had they not accidentally met on a train ride, etc. They keep going back to different points in their past: The day they met, the date of their wedding, and of course, everything is radically different, which aggravates the wife to no end ("This marriage is just based on chance, an accident..."). Right before everything gets really ugly, the husband deparately says: "Show us what we would have been doing at this very moment, had we not met on that train", and, surprisingly, they see themselves, exactly as they are right now, sitting together, happily married.

  17. More History by FrankDrebin · · Score: 2, Funny

    The Macintosh line would have been replaced by the SPARtan, leading to memorable models like the iSpart.

    --
    Anybody want a peanut?
  18. obligatory George Carlin quote by Laebshade · · Score: 3, Funny

    "here's a phrase that apparently the airlines simply made up: near miss. Bullshit, my friend. It's a near hit! A collision is a near miss." - Airline Announcements, George Carlin

  19. Abnormally deep pipeline? by argent · · Score: 3, Insightful

    It's strength was it's ferocious clock rates that were enabled by abnormally deep pipelines and instructions that did relatively little (no integer divide!).

    7 stages is not an "abnormally deep pipeline", and divide-step is absolutely conventional RISC design. The Berkeley RISC used divide-step. Sparc started out with divide-step. There really isn't a huge difference between Alpha's ISA and any other RISC, the difference is in the small details... whatever criticism you have of the Alpha, you can't in fairness leave the other RISCs out.

    Alpha also had great execution control. The memory barrier instruction (also in Power, by the way, and eventually picked up by Sparc) let the compiler control the pipeline far better than Itanium's "I can't believe it's not VLIW" design or MIPS "just guess" delayed branch. And the huge register file gave the compiler much more leeway in scheduling instructions.

    The biggest problem with the Alpha was that it jumped prematurely into 64-bit with both feet, so that even if the compiler generated 32-bit code (the -taso option) it was still moving 64-bit words around and throwing away half the result.

  20. Well if they *almost* used SPARC by alfrin · · Score: 2, Funny

    Isn't that like, "I almost got laid with man"

  21. Re:Sun should port x86 Solaris to intelMac by Zontar+The+Mindless · · Score: 2, Insightful

    What driver problems?

    I've installed it on about 7-8 different machines and it's done great on all of them.

    Solaris isn't intended as a multimedia, gaming, or use-my-latest-bleeding-edge-tech-toys OS, it's intended to provide a stable platform in order to get work done.

    If you put it on a generic workstation or server box, it pretty much kicks butt.

    --
    Il n'y a pas de Planet B.