That Cocoa training class was, as I’ve said before, one of the biggest eye-openers of my career. It was so damn easy to build beautiful, functional applications that I walked out feeling like I’d climbed into some giant mecha robot and could now lift huge girders with a wave of my pinky.
That Cocoa training class was, as I’ve said before, one of the biggest eye-openers of my career. It was so damn easy to build beautiful, functional applications that I walked out feeling like I’d climbed into some giant mecha robot and could now lift huge girders with a wave of my pinky.—In Which I Think About Java Again, But Only For A Moment — Thought Palace
Not that I think that there’s anyone who’s reading my blog and NOT convinced Cocoa is the best thing since sliced bread and that GUI Java is horrible-horrible-horrible, but still, a good read.
Noodlesoft writes about the history of the hideous thing we now know as Swing, and Swingdown on talblog follows up on the same subject. Sun really killed an AppKit-like Java toolkit just because it wasn’t built in-house? And when AWT was deemed too horrible and a new toolkit had to be built, they gave the job to the AWT guys? How could they not see the mistake in that? I guess that explains why Swing is so bad. (more: zefhemel)