Parse: How We Moved Our API from Ruby to Go and Saved Our Sanity
1–5 of 5 posts
Re: Parse: How We Moved Our API from Ruby to Go and Saved Our Sanity
#2[deleted]
Re: Parse: How We Moved Our API from Ruby to Go and Saved Our Sanity
#3Sounds like they would have ended up with C# if the CLR and Roslyn had been open sourced already.
Re: Parse: How We Moved Our API from Ruby to Go and Saved Our Sanity
#4Discussion from six days ago: https://news.ycombinator.com/item?id=9693743
Re: Parse: How We Moved Our API from Ruby to Go and Saved Our Sanity
#5This presumes you had sanity to save, which sounds really professional I guess. You wouldn't want to port a code base as a way to learn go and have fun that's not PC for some reason.
Edit: > Plus it seemed really fun. So, Go it was.
woot!