Earlier quoted context omitted.
Go gets compared to Rust because go was originally labeled a "systems" language. But the designers had a different older view of what "systems" meant than what is commonly used to day. People heard systems and thought they meant low level/operating system/embedded systems. That is not what Go is good for because it's garbage collected. They also planned to attract C++ programmers, but they've basically been attractin…
Yeah, additionally it would be unwise to use Go in embedded systems because it is so reliant on heap memory for dynamic allocation. In certain situations where things could fail if an operation takes too long - rocketry and robots - it would be difficult to tell how long something would take in Go with any degree of certainty because allocating and freeing memory on the heap is highly non-deterministic.
The State of Go
81–90 of 172 posts
Re: The State of Go
#82"Go 1.5 provides support for Android and experimental support for iOS." I thought this day would never come.
In fact, I really like using Go on iOS - the ease with which it can be done was astonishing!
Re: The State of Go
#83Earlier quoted context omitted.
I wonder how Go can be better than Swift for iOS development.
It may not always be better since you'll likely never be able to call from Go into Cocoa libs, but if you can write a shared library and use it on the server, iOS and Android, then it's a big win. Linking a Swift app against the shared Go library and calling directly from Swift into Go sounds pretty great to me.
It can be done, thus:
#cgo LDFLAGS: -Wl,-U,_iosmain,-U,_PopUpDialogBox
Any developer who wants to do this needs only to create these #cgo statements for whatever Cocoa API they want to use, and they become available from the Go context ..Re: The State of Go
#84Re: The State of Go
#85Nice little change in syntax. m := map[Point]string{ Point{29.935523, 52.891566}: "Persepolis", Point{-25.352594, 131.034361}: "Uluru", Point{37.422455, -122.084306}: "Googleplex", } may now be written as: m := map[Point]string{ {29.935523, 52.891566}: "Persepolis", {-25.352594, 131.034361}: "Uluru", {37.422455, -122.084306}: "Googleplex", }
I'm puzzled about the asymmetry of the syntax. What's the reason behind map[Point]string as opposed to something more symmetrical?
Now I wish I had 1 million dollars and a better brain to work full time on a proper language that would fix go's issues. What a missed opportunity to create something everybody would be comfortable with. It could have been the biggest language of the next 20 years in webdev, CSP is a great concurrency model. At least it will inspire some people in the future I hope. Rust is cool but doesn't have CSP builtin.
Re: The State of Go
#86Earlier quoted context omitted.
I wonder how Go can be better than Swift for iOS development.
It may not always be better since you'll likely never be able to call from Go into Cocoa libs, but if you can write a shared library and use it on the server, iOS and Android, then it's a big win. Linking a Swift app against the shared Go library and calling directly from Swift into Go sounds pretty great to me.
IIRC, Go can call any Objective-C code through cgo.
Re: The State of Go
#87Earlier quoted context omitted.
Go gets compared to Rust because go was originally labeled a "systems" language. But the designers had a different older view of what "systems" meant than what is commonly used to day. People heard systems and thought they meant low level/operating system/embedded systems. That is not what Go is good for because it's garbage collected. They also planned to attract C++ programmers, but they've basically been attractin…
Can you elaborate on the different meanings of 'systems programming'? I just thought it meant OS development.
Re: The State of Go
#88Earlier quoted context omitted.
You created a burn account just to complain about this? As you know, generics won't appear before 2.0, if ever. It's fine if that's a nonstarter for you. Perhaps you'll like Rust instead. It needs a big community too.
Why Rust? It doesn't really compete with Go anywhere. Haskell is a much stronger player in the space of high-level, garbage-collected languages. The only thing Rust and Haskell really have in common is not willfully ignoring the last 50 years of programming language design research.
Whenever Go is mentioned, Rust has to be mentioned somewhere in that same thread. And vice versa. It's practically law.
Perhaps a good indication that the debates tend to be more fashion-driven then about technical points (when the discussion is about new languages itself, that is of course reasonable though).
Re: The State of Go
#89Earlier quoted context omitted.
The same was true during the Microsoft Build event, the difference was that a lot of Microsoft employees registered a new (green) HN account. Not that I'm complaining but it looked more like a coordinated effort than Go language which has minimal PR from Google but is used by many devs around the world and is very big in Asia.
There are a lot of MS employees on HN normally, no need for green accounts. Also, where is Go popular in Asia? I haven't heard much about it in China (it isn't a resume point yet).
Re: The State of Go
#90Earlier quoted context omitted.
I seriously was wondering if Go would ever replace Java on Android because of legal troubles. I'm still wondering.
That will happen as soon as Android team decides to scrap all development of Android and rewrite it in Go.
I read in then news that iOS9 will use Swift in some internal apps/libraries too (major internal rewrites?).