---
title: "Comment by Mark on \"Go vs Java in terms of memory efficiency. Beauty of go routines and their variable stack size limit.\" | Hashnode"
description: "Wasn't this already posted? It looks familiar. Interesting though!"
url: "https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594/comment/5c87716ec1bd71485918419f"
---

[Discussion](https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594)

Comment [Go vs Java in terms of memory efficiency. Beauty of go routines and their variable stack size limit.](https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594)

[Mark](https://hashnode.com/@mverleg)

[Mar 12, 2019](https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594/comment/5c87716ec1bd71485918419f)

Wasn't this already posted? It looks familiar.

Interesting though!

[j](https://hashnode.com/@chilimatic)

[Mar 12, 2019](https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594/comment/5c87716ec1bd71485918419f#reply-5c8779351d0e3dd05d9f216f)

[Mark](https://hashnode.com/@mverleg) it was node last time.

[PRASHANTH H N](https://hashnode.com/@prahashnode)

[Mar 12, 2019](https://hashnode.com/posts/go-vs-java-in-terms-of-memory-efficiency-beauty-of-go-routines-and-their-variable-stack-size-limit/5c87671166eb7a457cb5a594/comment/5c87716ec1bd71485918419f#reply-5c87797c1d0e3dd05d9f2172)

The previous post was between nodejs and go. I had wrong understanding of node. I though node will spwan a thread per client which is not right. But this post is between java and go. I am not conveying anything wrong here.