3 ms·
BBEdit was an essential component of not having to deal with the terrible editor & even worse runtime stability of CodeWarrior for a spell in a past life of min
by im_down_w_otp 3y ago
BBEdit was an essential component of not having to deal with the terrible editor & even worse runtime stability of CodeWarrior for a spell in a past life of mine.
Thank you, BBEdit.
Also, you’re low-key responsible for my lifelong unrealized quest to give my Linux workstation sane keyboard shortcuts.
- girvo 3y ago> CodeWarrior Oh heck, you've just dredged up some absolutely horrific repressed memories of that pile of junk. It was impressive how unstable it was. It's funny too, these days I'm in embedded development again, and it's a markedly different experience to those days, though still amusingly unstable at times too.
- im_down_w_otp 3y agoBack in the good ol’ days of no memory protection on the Mac and the fun of trying to figure out if it was you or your dev environment that just unrecoverably hosed the system state.
- rvense 3y agoInteresting. Do you remember which version (or approximate year) you're referring to? I've recently been writing my first real app for Mac OS 9, using C++ (MacZoop framework) and Codewarrior Pro 5 on a G4. There's some features I miss from my modern developer environment (decent version control!), but other than that it's been a thoroughly enjoyable experience. Certainly I've had no stability issues at all with the IDE.
- girvo 3y ago2004-2005! Couldn't tell you the version though I'm afraid. I had nothing but issues with it, man it frustrated me haha. It's possible my memory has made the experience worse than it actually was however
- rvense 3y agoI've no reason to doubt your experience at all, I'm really just idly curious. Was that on Windows though? 2004-2005 I think it was all but gone from the Mac, and people had moved to Project Builder (later Xcode), but maybe you were still working on some older project. AFAIK the current CodeWarrior is based on Eclipse, if they're still updating it.
- girvo 3y agoI think it was, yes, and specifically for some embedded toolchain that required it. It would regularly lock up, crash, and lose my work. Though it’s quite possible the toolchain was at least partially the problem, and I wish I could remember which one it was. I might go digging through my old backups, I’m curious myself now
- rvense 3y agoAfter Freescale bought Metrowerks (1996? '98?), there were versions of CodeWarrior made for many of Freescale's embedded chips, which were obviously very common. Again, in spite of my current experience I don't doubt for a second that you had a lot of issues. Software was just a lot worse back then, and having now dipped my toes in the frameworks and languages used in the circa 2000 period, I'm not really surprised why. There's 0 references to automated testing in any of the programming books or documentation I've looked at, and as far as I can tell absolutely no support for it. Version control is extremely rudimentary. I didn't programme professionally until early last decade, and some of what I can infer to be have been normal is just baffling for me.
- cat_plus_plus 3y agoReally? I though CodeWarrior for PalmOS was a champ compared to Visual C++ for embedded platforms. Lets start with a fully functional and bug free compiler with standard library and all features working.