AppCode: Objective-C IDE from JetBrains goes public • Hacker News Board

Re: AppCode: Objective-C IDE from JetBrains goes public

#51

Post by chrismsnz » Fri, Apr 08, 2011, 10:10 AM UTC

pilif wrote: post #42

I know the GUI might not look nice due to being Java, but if AppCode will get as much polish and as many features as IDEA or the smaller language specific IDEs got, then AppCode is something to really look forward to. Even after a year of constantly using PhpStorm (yeah - still no time to rewrite that huge app I'm maintaining) I'm still finding little things that show that the IDE was really made by developers. It's…

Absolutely.

PhpStorm is simply the best IDE I've used for our very large PHP application. And I've tried almost all of them.

Re: AppCode: Objective-C IDE from JetBrains goes public

#52

Post by chrismsnz » Fri, Apr 08, 2011, 10:14 AM UTC

msbarnett wrote: post #20

spullara wrote: post #13

Earlier quoted context omitted.

In the worst case scenario you should keep it around for refactoring. The support in Xcode is far behind the state-of-the-art, those features alone should pay to have this around.

> The support in Xcode is far behind the state-of-the-art, those features alone should pay to have this around. Assuming AppCode's refactoring support ends up being even as good as Xcode 3's hit-or-miss heuristics, which remains to be seen. "AppCode is from JetBrains and ReSharper/IntelliJ IDEA have great refactoring, so AppCode will too" isn't a valid line of reasoning, because the limiting factor here isn't the aut…

I know what you're saying about AppCode's ability to understand the language, but after seeing first-hand the refactoring support of Jetbrains products for dynamic languages like Python, Ruby and especially my enormous PHP project - I don't think there's anything to worry about.

Re: AppCode: Objective-C IDE from JetBrains goes public

#53

Post by callumjones » Fri, Apr 08, 2011, 10:18 AM UTC

afsina wrote: post #49

callumjones wrote: post #37

Earlier quoted context omitted.

Chrome and Firefox seem to do a good job of going cross platform.

İt is just far easier with java.

Being 'easy' is irrelative when it results in a terrible user experience. There's no way to explain to the user: "oh this would look a lot better but we wanted to use a different language so it's not our fault".

Re: AppCode: Objective-C IDE from JetBrains goes public

#54

Post by rlmw » Fri, Apr 08, 2011, 10:35 AM UTC

callumjones wrote: post #15

I'm excited to see more additional development solutions for Objective C; but why are we taking a step backward with these awful Java like GUIs that have plagued Eclipse and NetBeans? Why in 2011, are people still building UI heavy applications with Java?

I think you've made a bit of a misconception here in confusing the underlying programming language (Java) with the UI library. Assuming you want a program to act and function naturally, like an OS X application - in which your problem is really down not to the programming language used. It is down to the libraries that are being used to develop the UI. Were people to be using Java as the language, but building from a Cocoa binding then you'd be able to have the same UX as a native app. Netbeans uses its own library, which is based on top of Swing. This doesn't feel native at all.

It is also worth noting that there's a big difference between the Gui Libraries that Eclipse and Netbeans depend upon. SWT, the library that eclipse depends upon is actually using native widgets /most/ of the time underneath. Unfortunately it does a lot of its own UI stuff on top of those widgets, and doesn't really follow Mac OS guidelines. I still feel its an incredibly well designed UI though in many regards.

Re: AppCode: Objective-C IDE from JetBrains goes public

#55

Post by afsina » Fri, Apr 08, 2011, 12:27 PM UTC

callumjones wrote: post #53

afsina wrote: post #49

Earlier quoted context omitted.

İt is just far easier with java.

Being 'easy' is irrelative when it results in a terrible user experience. There's no way to explain to the user: "oh this would look a lot better but we wanted to use a different language so it's not our fault".

Jetbrains producsts has a good reputation. It does not apply here.