3 ms·
wait until you try Android Studio...
by yiyayo110 1y ago
wait until you try Android Studio...
- andrekandre 1y agodo you mean to say it’s better or… worse??
- sunaookami 1y agoHuh, Android Studio is amazing because it's build by people who actually know how to make software (JetBrains) and it runs everywhere.
- pjmlp 1y agoProvided one has 32 GB, with 16 real cores and a 1TB SSD ultra-fast.
- sunaookami 1y agoThat's a pretty standard dev machine no?
- pjmlp 1y agoMaybe at Google, given how poorly Android Studio works otherwise.
- Jensson 1y agoThat was what I had at google 8 years ago, today its not expensive at all, any serious developer should have about that. If you develop on a weak laptop then that is on you / your company, should get a proper machine. Its good if tools are fast, but in general developers are expected to have fast machines so the tools are made with that in mind.
- pjmlp 1y agoSerious developer with US salary working at a FAANG, or SV money, you mean. As for being serious, most of the world being a developer is an office job like any other clerk, many companies have the same computers for everyone, regardless of what they do at their desk, assuming that they still get classical desktops instead of random brand laptops.
- bigfishrunning 1y agoIt really sucks that we, as software developers, are expected to spend a ton on a new machine every few years so that big companies can reap the benefits by shipping poorly written, slow tools. The development experience isn't any better or faster then it was 20 years ago, but it sure requires a faster computer.
- estimator7292 1y agoI run it on a Thinkpad T530 from 2013. It's maxed out with a 256GB SATA2 SSD, 16GB of memory and a 3rd gen 4c8t i5. Obviously the compiler and emulator (yes, emulator) are slow, but as an IDE it's perfectly functional.
- steve1977 1y agoWith everywhere, you mean everywhere in your RAM?
- flohofwoe 1y agoThe problems with Android Studio ist mostly caused by the underlying tech (mainly Gradle which is a massive pile of poop, and the general developer hostility of the Android SDK/NDK and related tooling), e.g. the JetBrains ancestry can be perfect but AS can still be bad (I don't share the Jetbrains enthusiasm though tbh, each time I tried any JetBrains IDE the UI was quite laggy, and the whole application takes forever to start). But yeah, if I have the choice between Xcode and Android Studio (and generally iOS vs Android development), Xcode+iOS easily wins, and that's not because Xcode is particularly great.