Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Studio 3.2

android-developers.googleblog.com

Post reply on HN
Print view View original

41–50 of 84 posts

Re: Android Studio 3.2

#41

Post by cobookman »

taeric wrote: post #22
waivek wrote: post #18

Earlier quoted context omitted.

Do you use a web app or a native app for YouTube?

I switched to firefox on my android for both Facebook and Twitter. So far, I've had very little downside to this.

+1 dropped facebook native app for their web version. Never looked back.

I think the answer is some apps are better on web, others on native.

Videos / Music / Games / Email / Messaging are better native. For actual reading of content (HN / Reddit / Twitter / Facebook ...etc) I find better on the web.

Re: Android Studio 3.2

#42

Post by dirtylowprofile »

I have been using AS since the first beta came out and every release it is just getting worst and slow on 16GB RAM.

While Xcode on the other hand 3-4 years ago it was liked developed by interns. But Xcode 9-10 has been very fast and less buggy on my 16GB.

Developing for Android is not fun anymore for me. It is getting bloated.

Re: Android Studio 3.2

#43

Post by [deleted] »

copperx wrote: post #35
lgleason wrote: post #23

Earlier quoted context omitted.

16GB is the bare minimum, but with some thrashing. 32 to really be usable, especially when running emulators.

Why has this been downvoted? I like Android studio but you do need to have at least 32GB of RAM for it to feel snappy. 16GB gives you a very usable, but sometimes laggy experience.

[deleted]

Re: Android Studio 3.2

#44

Post by kllrnohj »

foobaw wrote: post #5

Do the emulator and compiler still require SSDs and 16GB+ RAM to be usable? I love Android Studio but it used to always feel very heavy-weight.

My AS + Emulator running together is sitting at 3GB RAM. Definitely doesn't need 16GB+

Re: Android Studio 3.2

#45

Post by Scarbutt »

maxsilver wrote: post #40
TekMol wrote: post #6

I try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.

> I have to say it's such a giant bloated thing that it really does not make me want to write native code. Why? You can write (and compile, and test) native code without ever touching Android Studio. I would think any like/hate of IntelliJ (Android Studio) should have no bearing on whether you choose to write native Android code or not. It would be like saying, "CLion is such a giant bloated thing that I never want t…

If you are into masochism, sure, use Java without an IDE ;)

Re: Android Studio 3.2

#46

Post by sdinsn »

TekMol wrote: post #6

I try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.

> Developing for the browser is so much leaner

HAHAHAHAHAHA

Web apps are the most bloated thing I can imagine. Don't know what you are talking about

Re: Android Studio 3.2

#47

Post by wstrange »

TekMol wrote: post #6

I try Android Studio for a bit every now and then. I have to say it's such a giant bloated thing that it really does not make me want to write native code. Fortunately, there is a lot of great stuff going on with Progressive Web Apps now. I hope that they will be the future. Developing for the browser is so much leaner.

Have you considered Flutter?

Supported by VSCode and IntelliJ community edition. Hot reload is the cat's PJs.

Re: Android Studio 3.2

#48

Post by lokedhs »

I have used IntelliJ IDEA since the early 2000's and used it for Android development since Android first came out.

It used to be an amazing experience, and when the news came out that Google was going to switch to IDEA for their official tools instead of going with that Eclipse I was thrilled. Finally everybody was going to able to know just how fast and efficient Android development can be.

How wrong I was. When Android Studio came out, it was incredible slow. Even today, after years of improvement to the developer experience it still isn't as efficient as plain IDEA was before Google created Android Studio.

I actually lay most of the blame on Gradle, which became mandatory around the same time. I never thought that someone would create a buid tool I dislike more than Maven, but it seems they succeeded.

Re: Android Studio 3.2

#49

Post by p1necone »

specializeded wrote: post #29
watty wrote: post #8

Earlier quoted context omitted.

Developing for the browser is leaner but it's the opposite for end-users. I hope PWAs are the future as well but native is still king for the time being.

As a hypothetical user who doesn’t post on niche tech forums, I totally prefer a native app over a web app It’s pretty It’s fast It’s not stuttery-stoppy I can swipe back and forth between pages without waiting 4 seconds for everything to display, and then inevitably move around right before I fucking tap It’s on the app store I can use it instantly. I can remove it instantly. I don’t know what sandboxing is I don’t…

I prefer native apps over web apps, but for most things I vastly prefer a website to both of those. I shouldn't have to install an app for every single thing I want to use, especially if I only use the thing once a week or so.

Re: Android Studio 3.2

#50

Post by russellbeattie »

lokedhs wrote: post #48

I have used IntelliJ IDEA since the early 2000's and used it for Android development since Android first came out. It used to be an amazing experience, and when the news came out that Google was going to switch to IDEA for their official tools instead of going with that Eclipse I was thrilled. Finally everybody was going to able to know just how fast and efficient Android development can be. How wrong I was. When And…

Gradle is pure insanity. Take a JVM-based scripting language that no one uses, and base an entire build-tool around it - complete with a custom DSL - that is so slow it needs to be run in the background as a service to be even somewhat performant, and make sure that each new version somehow breaks older build scripts so that you're constantly being prompted to update, and then being prompted to fix whatever the update broke... It's honestly just pure, unadulterated, crap.
Post reply on HN