CodeWarrior

» see metrowerks.com as it lived, on the wayback machine

~ the last words ~

codewarrior never reached the windows-side dev tools i grew up with. by '06 when i started using compilers in earnest at university, the ide on every windows machine in ankara was visual studio. codewarrior was already a sunsetted mac-only tool by then, and the only macs in my orbit were the ones a couple of design-student friends owned, none of them with a developer install. i learned the name of codewarrior the same way i learned the name of hypercard, from reading old mac retrospectives years after the events. it was the ide that compiled the mac through most of the powerpc decade and i had no occasion to ever open it.

metrowerks was founded in 1985 in montreal as a tools-and-libraries shop. the company shipped its first compiler in '89 and started getting attention in the early-90s mac developer community for delivering compilers that were faster than the apple-blessed think c that everyone else was using. codewarrior shipped december 23 1993 as the bundled ide product that wrapped those compilers, with a project window and an editor and a debugger in one workflow that did not exist in the same form anywhere else on the mac at the time.

the timing was a gift from apple. apple was transitioning the mac line from motorola 68k to powerpc in 1994. apple's own mpw toolchain (macintosh programmers workshop) was still working from 68k assumptions, and apple's own compilers were slow to produce native powerpc binaries. codewarrior shipped powerpc-native compilers six months before apple did, with a register-allocator implementation based on gregory chaitin's coloring algorithm that produced output competitive with what the powerpc chip designers themselves were tuning for. for the apple developer community in '94 and '95, codewarrior was not the alternative to mpw, it was the only thing that could ship a powerpc app on time.

the brand value of being the company that saved apple's transition stuck. by '98 metrowerks had something like 90 percent share of the mac ide market by its own claims, with apple itself licensing codewarrior for internal builds at one point. motorola bought metrowerks in 1999 for 95 million dollars, mostly because motorola wanted the embedded-systems tools that metrowerks had quietly built on the side around the same compiler infrastructure the mac product used.

~ the record ~

~ the early days ~

codewarrior's developer experience in '96 was substantially better than what was available on windows at the same price point. the build cycle was fast, the in-editor symbol navigation worked, the debugger could step through powerpc native code with source-level information at a time when most cross-platform tools were still struggling with that. metrowerks shipped a bsd-licensed standard template library that ran ahead of what the gcc-based toolchains had at the time. for a developer community that had been used to apple's mpw being slow and obscure, codewarrior felt like a real ide that respected your time.

the embedded sibling that drew motorola's acquisition interest was the dragonball mc68k embedded toolchain plus the powerquicc network-processor compilers. metrowerks had been quietly selling those into motorola's own customers for years before the acquisition, with the desktop mac codewarrior being the visible product and the embedded codewarrior being the high-margin one underneath. that pattern of "the consumer product gets the brand, the embedded product gets the revenue" defined the next decade of metrowerks's life inside motorola and freescale.

~ how it actually ended ~

the apple intel transition announcement at wwdc june '05 was the event that ended the desktop codewarrior. apple shipped xcode as the free apple-blessed ide on every mac, with an intel-native gcc toolchain inside it, and the value proposition of paying metrowerks for a mac ide dropped close to zero. metrowerks announced july 29 2005, less than two months after wwdc, that pro 10 would be the final mac desktop release. the cited reason in the freescale press release was that metrowerks's revenue share from the desktop product had fallen from 22 percent to 5 percent, with the embedded side absorbing the rest of the company's focus.

freescale itself had been spun out of motorola in late 2004 as a semiconductor company specializing in embedded chips. the corporate path for codewarrior after that was a sequence of embedded-focused parents that cared about the compiler-and-debugger infrastructure but had no consumer-developer product in the catalog: freescale through 2015, then nxp after the freescale acquisition. the embedded codewarrior is still shipping in 2026 as a tool for nxp's microcontroller customers. the brand survives, but the codewarrior most people remember is the mac product that ended in 2005.

~ what came after ~

the engineering lineage of codewarrior runs into a couple of things that did stay important. the register-allocator implementation the codewarrior compiler team built was one of the early production implementations of chaitin's coloring algorithm, which had been an academic paper until codewarrior shipped a real compiler using it. that work fed into the later llvm register-allocation work indirectly through people who had been at metrowerks and moved on. the codewarrior project model of a tree of targets per project was one of the patterns later mac and windows ides converged toward, even if the specific ui choices did not survive.

the human inheritance was that the metrowerks engineering culture of fast compilers and tight ide workflows seeded a generation of compiler engineers who ended up at apple, at google, at jetbrains, at the gcc and llvm projects in various forms. that diaspora is where codewarrior had its real long-tail impact. the product itself is a 2005 artifact, but the ideas about how to ship a developer tool that respects the developer's time outlasted the product by a comfortable margin.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »