4 ms·
IMHO, it's not really a good language for mobile development. It is great for the task it was designed for; web services and infrastructure. I can't think of an
by wyager 13y ago
IMHO, it's not really a good language for mobile development. It is great for the task it was designed for; web services and infrastructure. I can't think of any other area I would choose to use Go.
- axaxs 13y agoI initially agreed, but realize it's just because go hasn't been widely used in GUI development. With a proper SDK, there's nothing wrong with it in this role that I can think of. In full disclosure, I've not done Android development out of my distaste for Java, so I'd welcome it.
- wyager 13y ago> but realize it's just because go hasn't been widely used in GUI development There are a lot more reasons than that. For one, Go has awful support for any kind of generic programming. The closest thing Go has to proper generic support is the interface{} type, which is awful. It's basically the same type safety as a 100% dynamically typed language (i.e. almost none), but with a much uglier syntax. A related issue is that Go isn't very extensible. For example, Go's iteration features only work on builtin types. You can't iterate over trees, graphs, sets, or any other non-builtin type. For me, the only good things that Go offers are decent threading primitives and good standard library support. Nothing else excels, and some things are downright bad.
- oscargrouch 13y agoDont know why just because of a negative critique, people have downvoted you.. so im doing justice and doing a upvote I might not agree with this comment, but at least his showing the reasons why he dont think Go is a good candidate for mobile development, and his opinion is technical backed I think this should be in some HN etiquette somewhere.. dont know why people are so sensitive when a comment is not to say something nice about something..
- pkulak 13y agoEvery language doesn't have something. A better response would have tied those ommisions into GUI development. A set in Go is a hash, queues are channels. You can range over both. I've never used custom tree iteration in Java to build an Android app and I've managed to do okay.
- RyanZAG 13y agoIt's an interesting phenomenon that occurs on HN. It's fairly easy to explain. Each HN user that sees this post has a chance to view and comment on the post depending on his interests. A Python developer would be likely to simply skip this post, while a Go developer would be highly likely to view this post as he has an interest in using his Go knowledge on more platforms. That means we have a highly skewed distribution of people upvoting and downvoting comments on any language specific article. For example, if there are 10 Go developers for every 100 Python developers viewing HN, in a thread such as this one, there may be 9 Go developers for every 5 Python developers. This means that a large percentage of viewers of any critical Go posts in a Go thread are Go developers. They will downvote that critical post almost regardless of content. This is not a knock on Go developers, merely standard tribalism. There is an identical effect in Haskell, Ruby, or even Perl discussions. There is probably no solution - if you value karma, I recommend not posting critical comments about a language in a post specific to that thread. You should rather save those comments for more general threads about programming theory, etc. If you don't care about karma (and you shouldn't), then please keep posting.
- rm445 13y agoJust because someone frames an opinion in technical terms doesn't make it relevant to the discussion. There's a mismatch in the levels of abstraction, claiming that a lack generic programming is Go's downfall for mobile application development. Some people clearly feel quite strongly that generics are a vital part of any language. But they don't really tie into the difficulties of mobile app programming, which are (i) resource contraints, much tighter and differently prioritised to desktop and server programs; and (ii) dealing with GUI libraries, which typically have massive numbers of functions, nests of callbacks, and are generally fiddly to program. Generics can be a help with various algorithms but it's far from clear that they help with mobile-specific issues. Your parent poster is the typical person who shouts about generics in every Go thread. Like the people who spit bile every time Stephen Wolfram is mentioned in any context, it gets pretty tiresome.
- mseepgood 13y agoWhat do generics or loop syntax sugar have to do with GUI development?
- wyager 13y ago>What do generics or loop syntax sugar have to do with GUI development? Nothing. Someone said something along the lines of "Go is only bad for mobile because it has bad GUI support." I disagreed. Mobile development is more than just GUI development. If the only thing I cared about when writing a mobile app was GUI support, I could write mobile apps in HyperCard.
- herokusaki 13y agoIs there a HyperCard clone for the mobile?
- melling 13y agoYou are simply offering an opinion with providing any supporting evidence. Where does Go fall short as a language for mobile? Why would it not work well? People use JavaScript to develop mobile apps, for example. The rapid compile times would be great for iterative development and the fast performance might even be better than Dalvik.
- skybrian 13y agoI'm not the original poster and I have no evidence to share, but I'll point out that Go executables are often quite large due to static linking. Client-side apps have to worry about code size.
- leaveyou 13y agoif I understood correctly, that problem is already being addressed in 1.3 and the size of the files will decrease with the work on the new compiler/linker.
- wyager 13y ago>Where does Go fall short as a language for mobile? Go falls short as a language for mobile in the same ways it falls short as a language for most things. It's simply not a very well-designed language. Let me give you a few examples: Terrible support for generic programming. Read almost any production go code and you see many instances of the interface{} type. This is basically equivalent to up-casting to Object in java, or passing things around as null* in C++. In many cases, that's the best you can do. All the type-safety of Python with five times the verbosity. Many features are built-in, non-extensible language directives. Take the `range` operator. `range` only supports built-in types like maps, slices, and chans. You want to range over a tree? Too bad. Want to range over a graph? Too bad. Want to range over a queue or a linked list? Hmm, well too bad, or maybe wrap the queue or LL with a chan, write a helper function, range over that, and watch your performance go to shit. Go was built with one purpose in mind; building web services. It's good at that. But really, the only things Go has going for it are decent threading primitives and a solid standard library. So the answer is this: Go is not a bad language, but it is certainly no better than existing languages for writing mobile applications. Go offers nothing that would make me, if I were a mobile app developer, want to switch from Java or Objective-C. In fact, it's missing a lot of things that I might consider important.