Hacker News new | comments | ask | show | jobs | submit login

Until I see this as an official Android SDK language, or presented at Google IO as such, I will ignore it.

The Android team has been very clear where they stand.

and this: We are building a Flutter plugin for Atom. Today, it can syntax highlight, code complete, refactor, launch apps, create new apps from a template, show type hierarchies, jump to definition, and more.

Why not Android Studio ? this release announcement is weird. it seems to be as much political as technical.

I think they are trying to be more friendly to non-android developers , and you may noticed this is platform for both iOS and Android . If it were for only android they you were right, but as it stated they targeting iOS too, then we can deduce they are trying to be more like React or Cordova(if I spell correctly).

p.s. It seems that is their approach , does not mean I agree with that.I would prefer android studio support. Then they can advertise android developer can produce iOS version of their app in android studio too.But clearly they want be more like react.

Intellij Idea and Webstorm already supports Dart as language. I am guessing they wanted something lightweight initially. Since Flutter is in pre-alpha state, support for Android studio may come later.

lightweight except Atom struggles on my mbpr 2013 while I use intellij (pycharm) just fine (2 windows/projects at once even)...

I did not mean speed, definitely Java beats JS in speed.

And yet Atom starts instantly on my rMBP 2014 while PHPStorm takes a minute or so?

honestly, my atom must have something wrong as it hangs like I'm working on a 386 with 1MB ram on startup, open file (I will let you imagine what happens if I open the occasional unfortunate file with long lines)..., and I'm not even taking in account the feature mismatch. I come from vim so I can appreciate a text editor, it's not I'm an IDE lover or anything...

How many features from PHPStorm does Atom cover?

Atom is a good choice to get started on editor integration because it's easier to develop for using a language that can compile to JavaScript. But the underlying technology (Dart analysis server) works with multiple editors and IDE's.

Yeah another caution of mine. I would very much not like my projects to be a causality in an internal political war at Google. Who knows what might happen down the line...

I get the feeling that Android Studio is a ship on the seas of Google with a helmsman of sorts but with a flotilla of smaller boats around that vie for attention.

The new features they introduce look interesting-ish but there are big problems, and I suspect that bundling Flutter into Android Studio, whilst a good headline, would not be high in the list of priorities.

For example, the C++ NDK is still not properly supported in Android Studio, despite the message that Eclipse is being deprecated at the end of next month. I have ran into numerous issues with it which has meant I have to currently abandon hope of porting this C++ library across to it.

Issues I have ran into:

a. I can either run the emulator with resume support and no GPU acceleration so that it is dog-slow to use, or have GPU acceleration and the very slow startup of the emulator.

b. On my Mac, it will randomly not install or find the device with adb (oddly intermittent!).

c. The emulator does not support WiFi, meaning monitoring apps that rely on wireless and multicast and the wireless interface being there are impossible to debug (the app makes checks for the wireless interface being available and uses its address to join an interface lower in C++ land). What's the point of the emulator, I hear you ask?

d. You have to jump through Gradle hoops to stop the ndk-build system generating its own build script and to get it to respect your existing Android.mk and Application.mk files. Getting it to build static libs involves bulding shared libs and then adding another build command to include that static lib into your dummy shared lib. Static libs that you build in a build process will not be automatically copied to the APK library - only shared ones will.

e. My application is having problems with OpenGL textures early on but breakpoints for NDK C++ apps will NOT be hit until 10 seconds after program startup...... this is really rubbish; I can't stress how unfathomably lame this is.

f. Android Device Monitor (DDMS) does not support networking monitoring for Intel images (https://code.google.com/p/android/issues/detail?id=25997) so you can either have a fast Intel emulator with no network monitoring support, or you can use the dog-slow ARM software emulator with network monitoring support, with the caveats that the wireless interface you depend on will be missing from the emulator, and that your breakpoints during program setup will not be hit etc. etc. etc.

g. Android Studio randomly stops accepting keyboard input. Random background crashes happen (but the IDE does not disappear).

I cannot see Flutter being high on the priority list here.

I use C++ for portable code between Windows Phone and Android. Slowly thinking about jumping into a JVM/CLR friendlier language though, without JNI/NDK headaches.

Currently my mobile development is just an hobby.

Based on my experience, the issues related on the NDK issue tracker, the mailing list, IDE support, Google IO talks and the state of the still experimental and incomplete Gradle support, it feels as if the Android team was dragged into supporting anything else other than Java.

At least you manage to hit the breakpoints, on my cases the IP just flies by the address never stopping.

Compared to the tooling experience on Windows Phone or the few cases I used iOS at work, one feels as if they only do NDK development on as needed basis, but actually it would be better if the NDK never existed in first place.

If I was on the NDK team I would feel ashamed that Microsoft and NVidia are able to provide a better developer experience than the platform owners.

Yes this is precisely how I feel. I have spent days trying to get a decent development platform (can't remember how I got breakpoints to hit, I think after upgrading to 1.4 things stopped working) so I have completely given up. I can really see why development is typically iOS first and then Android second.

And I say this having written Android applications in Java (no problems there really) and now getting my feet wet in iOS with Swift/ObjC.

I agree with you about the NDK being a thing they never wanted to support. You can see this in the documentation where they state that applications should be written in Java for Android, first and foremost. But given that the underlying libraries can be compiled under Windows, OSX, iOS etc it makes sense to have a C++ system for Android too. It's a pity that it's such a complete mess, and is at best a complete joke.

I really am giving up on it.

> The Android team has been very clear where they stand.

Just for reference and general understanding, can you link something on this point? Thanks.

Yes, that is what I meant.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact