tag:blogger.com,1999:blog-5522230262649447143.post6289869954432655469..comments2024-03-01T00:22:39.982-08:00Comments on stuff: Highlights that impressed me from the video on the Go languageVishnu S Iyengarhttp://www.blogger.com/profile/06935516811962030409noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-5522230262649447143.post-39090774739261657832009-11-14T04:54:26.861-08:002009-11-14T04:54:26.861-08:00@Vamsi good question. I've been trying to hunt...@Vamsi good question. I've been trying to hunt for the information too and I haven't found anything yet. Looks like a deeper search is in order :)Vishnu S Iyengarhttps://www.blogger.com/profile/06935516811962030409noreply@blogger.comtag:blogger.com,1999:blog-5522230262649447143.post-38963474621149400442009-11-14T04:49:12.043-08:002009-11-14T04:49:12.043-08:00oops scratch that. They do have locking. I guess i...oops scratch that. They do have locking. I guess it's just usually unnecessary. Given large enough data structures though, I suppose it will be necessary to fallback to it.Vishnu S Iyengarhttps://www.blogger.com/profile/06935516811962030409noreply@blogger.comtag:blogger.com,1999:blog-5522230262649447143.post-35457654003840347752009-11-14T04:45:35.508-08:002009-11-14T04:45:35.508-08:00@vikram : haha I agree the name go lends itself to...@vikram : haha I agree the name go lends itself to some pretty cheesy names around this. The async execution model is nice here especially because they don't require people to fiddle around with crap like shared state and locks. The channels make it really elegant :)Vishnu S Iyengarhttps://www.blogger.com/profile/06935516811962030409noreply@blogger.comtag:blogger.com,1999:blog-5522230262649447143.post-47747516678767842362009-11-13T09:48:18.013-08:002009-11-13T09:48:18.013-08:00I am a big fan of co-routines and Async execution ...I am a big fan of co-routines and Async execution - So Go gets good points in my book for that (I love how F# brings async execution to .NET)- But goroutines sounds very cheesy :)Anonymoushttps://www.blogger.com/profile/15599894556739103705noreply@blogger.comtag:blogger.com,1999:blog-5522230262649447143.post-74761414467170987852009-11-13T06:21:11.043-08:002009-11-13T06:21:11.043-08:00Nice article! I was in need of a programmer's ...Nice article! I was in need of a programmer's perspective of the language. This gives good incentive to start exploring this, as you've said.<br /><br />And I guess the really innovative thing is the Go keyword, from which this gets its name I suppose.<br /><br />I am more interested in the dynamic nature of the compiler. "Run time reflection". I wonder if it has something to do with a dynamically expanding memory stack which the compiler uses? and wow at portability.<br />The golang faq doesn't mention anything about how the data reflection is achieved on a compiled language :p<br /><br />Though it mentions about using segmented stack memory for the goroutines to do their job. Interesting, it should prevent any memory bleeds (If at all) after its stable.<br /><br />And thanks for the articleUnknownhttps://www.blogger.com/profile/08111477594264425343noreply@blogger.com