<hr/>**评论：**<br/><br/>jasharpe: <pre><p>Details?</p></pre>hoffentlich: <pre><p>Do tell first.</p></pre>mikebcity: <pre><p>Wow my inbox just exploded...I'm currently on vacation I will be back by Monday.</p>
<p>But the short of it is, I've written an API using a very antiquated language and I wanted it rewritten in GO simply because GO just rocks and I'm just not there yet.</p>
<p>The person who will do this conversion will basically convert this service over to GO. In addition, they will have ongoing work. Payment will be made via PayPal. If your communication skills and your attention to detail is excellent then their will be plenty of work to "GO ON" (little pun :)</p>
<p>That's it looking forward.</p>
<p>Mike</p></pre>danredux: <pre><p>I did this exact job for Google.</p>
<p>If the API is wide but shallow, like a REST API, I recommend not using Go. Other languages are more suited to doing basic request-database-response type work.</p>
<p>If the API is thin but deep, like an adserver or other computational service, I do highly recommend Go.</p></pre>commentzorro: <pre><p>What makes Go less suitable and why? Why would language [X] be more suitable?</p></pre>
