Comments for Alex Ruiz's Blog http://alexruiz.developerblogs.com Having Fun with Java! Tue, 21 May 2013 23:19:46 +0000 hourly 1 http://wordpress.org/?v=3.4.1 Comment on Android Studio: our new, shiny Android IDE by Joe http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124840 Joe Tue, 21 May 2013 23:19:46 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124840 I work in a Java dev shop for more than a decade and we evaluated various Java IDEs. IDEA was the first preffered IDE. Because of lack open source edition at that time, we ended up going with Netbeans. Eclipse never worked for me. It was fine for small adhoc type projects. When you have 100s of thousands of lines of code, Eclipse is pain to use. It puts the burden of project dependencies on each developer. Poor project management system in Eclipse is the main culprit. I always felt Eclipse was built by folks who never used an IDE. I am glad smart folks at Google finally realized this and fixing it. I work in a Java dev shop for more than a decade and we evaluated various Java IDEs. IDEA was the first preffered IDE. Because of lack open source edition at that time, we ended up going with Netbeans. Eclipse never worked for me. It was fine for small adhoc type projects. When you have 100s of thousands of lines of code, Eclipse is pain to use. It puts the burden of project dependencies on each developer. Poor project management system in Eclipse is the main culprit. I always felt Eclipse was built by folks who never used an IDE.
I am glad smart folks at Google finally realized this and fixing it.

]]> Comment on Android Studio: our new, shiny Android IDE by Android Studio: Googleの新しく、輝かしいAndroid IDE | サムライズム #Samuraism http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124754 Android Studio: Googleの新しく、輝かしいAndroid IDE | サムライズム #Samuraism Tue, 21 May 2013 05:08:03 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124754 [...] 本エントリはGoogleのAndroidチームのソフトウェアエンジニア、Alex Ruizさんのブログエントリを翻訳したものです。 翻訳版の公開を快諾いただきましたAlex [...] [...] 本エントリはGoogleのAndroidチームのソフトウェアエンジニア、Alex Ruizさんのブログエントリを翻訳したものです。 翻訳版の公開を快諾いただきましたAlex [...]

]]> Comment on My contribution to Eclipse CDT: external-tool-based code checkers by Some good resource for CDT development | zhongyinzhang http://alexruiz.developerblogs.com/?p=2231&cpage=1#comment-124563 Some good resource for CDT development | zhongyinzhang Sat, 18 May 2013 18:52:14 +0000 http://alexruiz.developerblogs.com/?p=2231#comment-124563 [...] My contribution to Eclipse CDT: external-tool-based code checkers [...] [...] My contribution to Eclipse CDT: external-tool-based code checkers [...]

]]> Comment on My contribution to Eclipse CDT: external-tool-based code checkers by Integrate an external code checker into Eclipse CDT | zhongyinzhang http://alexruiz.developerblogs.com/?p=2231&cpage=1#comment-124562 Integrate an external code checker into Eclipse CDT | zhongyinzhang Sat, 18 May 2013 18:51:21 +0000 http://alexruiz.developerblogs.com/?p=2231#comment-124562 [...] My contribution to Eclipse CDT: external-tool-based code checkers [...] [...] My contribution to Eclipse CDT: external-tool-based code checkers [...]

]]> Comment on Android Studio: our new, shiny Android IDE by Alex Ruiz http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124541 Alex Ruiz Sat, 18 May 2013 15:48:33 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124541 Absolutely! To me, the main benefit of working with the JetBrains folks, besides IntelliJ's well-thought architecture and clean code, is the JetBrains folks themselves. Any change that we needed in their platform was implemented in a matter of hours, if not minutes. Questions and bug fixes were addressed right away. This kind of support allowed us to move really fast. Absolutely! To me, the main benefit of working with the JetBrains folks, besides IntelliJ’s well-thought architecture and clean code, is the JetBrains folks themselves. Any change that we needed in their platform was implemented in a matter of hours, if not minutes. Questions and bug fixes were addressed right away. This kind of support allowed us to move really fast.

]]> Comment on Android Studio: our new, shiny Android IDE by Dmitry Jemerov http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124539 Dmitry Jemerov Sat, 18 May 2013 15:31:47 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124539 Android Studio built under the umbrella of Eclipse already exists, and is called ADT for Eclipse. The dark theme is part of IntelliJ Platform; it's not something that the Android team at Google worked on. If someone wants to reimplement it for Eclipse, they're welcome to do so (and I think Fabio Zadrozny plans to work on it as part of his LiClipse project), but I don't see how this has anything to do with Android Studio. And I guess a key difference is that JetBrains is able to implement the changes Google needs in a short timeframe and without asking Google to lend a hand with the platform development. Which lets Google focus on developing the Android plugin specifically, not improving the underlying platform. Android Studio built under the umbrella of Eclipse already exists, and is called ADT for Eclipse.

The dark theme is part of IntelliJ Platform; it’s not something that the Android team at Google worked on. If someone wants to reimplement it for Eclipse, they’re welcome to do so (and I think Fabio Zadrozny plans to work on it as part of his LiClipse project), but I don’t see how this has anything to do with Android Studio.

And I guess a key difference is that JetBrains is able to implement the changes Google needs in a short timeframe and without asking Google to lend a hand with the platform development. Which lets Google focus on developing the Android plugin specifically, not improving the underlying platform.

]]> Comment on Android Studio: our new, shiny Android IDE by Dmitry Jemerov http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124538 Dmitry Jemerov Sat, 18 May 2013 15:21:21 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124538 Scott, As Alex mentioned, the compilation in Android Studio is entirely driven by Gradle. So the degree to which it will be incremental, and the speed of the edit-build-deploy-test cycle, is entirely determined by the feature set of Gradle, not Eclipse or IntelliJ. And for non-Gradle-based projects, recent versions of IntelliJ IDEA do fully support incremental on-the-fly compilation. As for the window dressing - well, if you say that, then I'd say that most of the features of Eclipse and IntelliJ are unnecessary. You can do everything in Notepad, after all. Scott,
As Alex mentioned, the compilation in Android Studio is entirely driven by Gradle. So the degree to which it will be incremental, and the speed of the edit-build-deploy-test cycle, is entirely determined by the feature set of Gradle, not Eclipse or IntelliJ. And for non-Gradle-based projects, recent versions of IntelliJ IDEA do fully support incremental on-the-fly compilation.

As for the window dressing – well, if you say that, then I’d say that most of the features of Eclipse and IntelliJ are unnecessary. You can do everything in Notepad, after all.

]]> Comment on Android Studio: our new, shiny Android IDE by Alex Ruiz http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124495 Alex Ruiz Sat, 18 May 2013 03:07:04 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124495 I appreciate your concern, Erdal. I can take care of myself pretty well, thanks :-) I appreciate your concern, Erdal. I can take care of myself pretty well, thanks :-)

]]> Comment on Android Studio: our new, shiny Android IDE by Alex Ruiz http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124486 Alex Ruiz Fri, 17 May 2013 22:25:22 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124486 Gunnar, I hear you. I appreciate your good intentions. I'd suggest you to check with the Eclipse folks if such conversations ever happened. They may have happened before you and me got involved. Peace. Gunnar, I hear you. I appreciate your good intentions. I’d suggest you to check with the Eclipse folks if such conversations ever happened. They may have happened before you and me got involved.

Peace.

]]> Comment on Android Studio: our new, shiny Android IDE by Gunnar http://alexruiz.developerblogs.com/?p=2700&cpage=1#comment-124484 Gunnar Fri, 17 May 2013 21:57:53 +0000 http://alexruiz.developerblogs.com/?p=2700#comment-124484 Alex, seriously, did the Android SDK team at Google entered Bugzillas at all? It sounds like you never did for JDT. That's certainly not how Eclipse (and to some extend Open Source) works. You can't complain and celebrate a switch without letting developers/committers know about your issues. Alex, seriously, did the Android SDK team at Google entered Bugzillas at all?

It sounds like you never did for JDT. That’s certainly not how Eclipse (and to some extend Open Source) works. You can’t complain and celebrate a switch without letting developers/committers know about your issues.

]]>