You forgot to preface that whole thing with "It is my opinion that..." FTFY.
On Tue Nov 04 2014 at 1:26:42 PM Steven Stamps <[email protected]> wrote: > This is yet another example of the true cost of building on top of a > proprietary product. > a) you are at the mercy of the owner's priorities, agenda and (sometimes > poor) judgement > b) you are frequently placed on a "slippery slope" that forces you to buy > into the commercial product if you want to get "real" work done > c) a strong open source ecosystem never materializes around the tool, > even if there is a "community edition", because the open source developers > know they will be marginalized > > Daniele's point is technically correct. There are many other ways to work > around this problem, but that is missing the entire point of an IDE. It is > supposed to make things fast/efficient/frictionless/natural for the > programmer. IDEs are supposed to enable and sustain high programmer > velocity during many longs days of coding. > > As an example, SQLite is an important architectural component of many > Android apps. Examining the database contents frequently during > development is an important debugging and validation actiity. Human eyes > during initial development are always needed to validate even the best > test-first frameworks. It is a one-step frictionless effort in Eclipse, > using a free plug-in, which is completely reliable and a pleasure to use. > > BTW, I have been using AS on a fairly large/complex project for about 4 > months. I migrated the project from Eclipse to AS when Google made it > clear that they were not going to continue their commitment to the Eclipse > platform. Although I am a loyal Google/Android soldier, I can tell you > that: > - AS is less stable than Eclipse, at least for my large project/app > - debugging is not nearly as robust or reliable as Eclipse > - developing/debugging with an actual piece of hardware (beats the pants > off of any emulator) is 10x better in Eclipse > - there are dozens of UX/GUI characteristics that were elegantly designed > and implemented in Eclipse (to create/facilitate the actual writing of Java > code), that are either missing or just downright destructive to programmer > flow and productivity in AS > > On the flip side, it is obvious that Google is putting in way more effort > into the Android-specific features of AS than they ever did with Eclipse. > It just turned out (thus far) to be a giant step backward for those of us > who actually write a lot of Java code and/or build complex > profession/expert tablet applications. > > I'll reserve final judgement on AS until it is formally released as a > product. I know they still have a VERY long way to go. > > Unfortunately, the IntelliJ/proprietary problem will never go away. :( > > Best... > > > > > On Friday, January 24, 2014 6:49:17 PM UTC-6, Adam Brown wrote: >> >> I saw that back in October of last year InteliJ added Android >> SQLite support to their Database Support plugin: >> http://blog.jetbrains.com/idea/2013/10/intellij-idea-13- >> eap-and-android-sqlite-database/ >> >> But that doesn't appear to be present in Android Studio (*as of 0.4.3*). >> >> I was wondering if there were plans for integrating this? It would be >> fantastically useful to have 1 click access inside the Android tab in AS to >> visually inspect your applications Databases. >> > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
