|
|
|
|
|
|
by aristus
6491 days ago
|
|
|
I agree about Google Web Toolkit. GWT is, at best, a way for hidebound Java programmers to feel comfortable making interfaces for the web. I have not looked at Obj-J very closely, but it seems like the same thing: a way to give Mac programmers a way to express themselves comfortably on the web. Encouragingly it looks a lot more fluid than a Java mudball. It may also be a better and more compact way to build "rich" web apps, but that remains to be seen. |
|
|
As a designer, every time I've seen Obj-J, I've thought about it being possibly useful as a bridge in the other direction: as motivation to learn Cocoa and go from the web to desktop and iphone.
I've been interested in developing native OS X apps for a while but haven't had the time or inclination to pick up a set of skills that are parallel and disconnected from web development, so finally being able to develop in a similar language for multiple platforms is very enticing.
Personally, I wouldn't mind letting go of the html/css if I could get pixel perfect precision in a different manner (can you get do that with Cappuccino?) that would also translate across platforms. I don't care about recycling skill sets - it's not like I can 1) use stylesheets on native apps today, other than for gimmicky crap like Dashboard widgets, or 2) will forget the html/css that's been hammered into my brain over the years, especially since I'll still be using it for informational and content-centric websites as opposed to web apps.