Earlier quoted context omitted.
Ever since i picked up a Nokia N800 back in the day, my go to setup has been a featurephone with bluetooth and a "smart device". Thus if i need a net connection right damn now, i can pair the smart device with the featurephone and get online.
Can you elaborate on how you do this? I wasn't aware that you could use a feature phone over bluetooth as a wifi hotspot. Are you doing something different?
It’s Been Real, Android: Why I’m Retiring from Android
241–250 of 342 posts
Re: It’s Been Real, Android: Why I’m Retiring from Android
#242I found that as I get older, and still try to learn different languages and platforms, that I have to try and work on my research skills as much as my coding skills. As the OP pointed out - straddling several languages means that syntax and keywords are not always readily apparent when you sit down to code, but knowing where to look for them and refresh your memory quickly becomes an activity all on its own. This fro…
I always thought those language/framework/library cheat sheets were for newbies only, but I'm beginning to see that's not entirely the case.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#243Earlier quoted context omitted.
Other than the slightly different standard libraries, what else is different? Android Java is effectively the same as java 7, and any difference is solely attributed to library/SDK/api.
They don't support all the language features, specially the ones that make use of the new bytecodes. This will only get worse when Java 9, specially Java 10 gets released.
Android supports 100% of Java 7, and with a new compiler ("Jack") it supports most of Java 8. For an average Java developer, it is absolutely a completely vanilla Java experience, and Android developers can pull in virtually any mainstream Java project or code with ease.
The root claim is utter nonsense. This whole submission is just garbage -- a developer who is terrible at Android "retires" from it. The world doesn't care.
(yes this post will be dead, courtesy of the utter decline of HN)
Re: It’s Been Real, Android: Why I’m Retiring from Android
#244Earlier quoted context omitted.
> It's just a mess. I'd expect a relatively painless experience: install dev tools, start a new project, build and go! But no, it's jumping through hoops, requires understanding a myriad of different SDK/platform versions and a constant churn in keeping your apps up to date with new versions while trying not to break backwards compatibility. > And a big part of this mess comes from the fact that device manufacturers…
C# is as easy to get started with as I've seen for any language. I don't see the comparison?
ASP.NET used to be difficult to configure and deploy (just some things like basic defaults being pretty bad for real apps), but even then I'd say the alternatives at the time (EJB, Spring, etc.) were significantly worse. For all other uses, I've had zero tooling problems. Oh sure, there were times I painted myself into a corner with regards to my app design, but that will happen in any language. I've never found any platform as easy to get up and running as .NET.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#245Sorry for my ignorance, but wouldn't React Native help with these sort of problems?
React Native does not help with any sort of problems.
If you need to build an iOS and Android app and you don't need to really push the envelope on design then React Native is a godsend. It's not the right solution for everything but for that vast array of apps that are mostly just list/tableviews talking to a REST backend it's a massive timesaver.
I've been doing native iOS work for six years now and I'd still recommend RN over straight native for a lot of projects.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#246Earlier quoted context omitted.
C++ isn't a platform with a platform owner. Python's biggest strength that lead to its adoption was being a language with "Batteries Included".
I'm not sure about the meaningful distinction here. Programming on any platform will be greatly improved by using good (preferrably opensource) libraries. What difference does it make who made them and why? It's such a strange nitpick.
If you're using N separate libraries, that's N times the likelihood of breaking changes that force you to migrate at inconvenient times, and O(N^2) opportunities for bugs caused by incompatibilities.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#247Earlier quoted context omitted.
> Just like the web platform, Android is hugely improved when you leverage the community libraries and tools they provided. Which speaks a lot about the quality of work provided by the platform owner, when the community needs to step up.
No it doesn't it's the same on iOS. Apple didn't come up with dependency/package managers like Carthage or Cocoapods, the community did. There's just enormous amounts of OSS libraries provided by the community too, with ones like Alamofire smoothing out the rough edges of iOS's networking APIs.
What matters is the out of the box experience.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#248Earlier quoted context omitted.
Any Android Studio generated project will do. Dual core with 8 GB, 500 GB HD, perfectly fine for Eclipse, Visual Studio, MSBuild, Ant, Maven. No need for performance tricks like Gradle requires.
> 500 GB HD Do yourself a favor and get an SSD.
If you offer me a 500 GB SSD I will gladly take it.
Re: It’s Been Real, Android: Why I’m Retiring from Android
#249[deleted]
Re: It’s Been Real, Android: Why I’m Retiring from Android
#250Just like the web platform, Android is hugely improved when you leverage the community libraries and tools they provided. Gradle actually helps a lot with that, since its clear dependency management makes use of external libraries a breeze. If in 2016 you're still complaining about AsyncTasks and its management, you certanly have missed a lot of progress in the last few years. It's not unlike having people complain a…
Hey, what libraries for assisting with MVP/etc. patterns did you have in mind?
Incidentally, our Kotlin-based app actually has a completely custom one that an opinionated product guy wrote that works reasonably well, but it still needs a lot of work and probably to be fully extracted for an OSS release. We also have some Kotlin delegated properties and other magic for cutting down on lifecycle & state management boilerplate.