The ups and downs of porting 50k lines of C++ to Go (2015)

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by tsimionescu on Thursday March 14, 2019 @03:36AM (#19387179)

Go's big advantage over other memory managed languages is the very low overhead of its runtime - a hello world Go app is probably less than 5MB on disk with all dependencies, and takes up less than 5 MB of RAM. This is absolutely wonderful if you want an architecture of many independent containerized apps, especially with something like Kubernetes or Docker Swarm. Compared to that, the smallest Java container on the classic Docker repos is about 90MB in size and takes up a few tens of MB RAM.

Apparently there is a new Java project [1] floating around that is promising a way to use Java exactly in this use case, but I haven't played around with it.

[1]: https://quarkus.io/

[ Parent | on HN ]

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by apta on Thursday March 14, 2019 @10:25AM (#19389479)

http://august.nagro.us/small-java.html

You can run an empty Spring Boot service in 15MB of RAM or so.

[ Parent | on HN ]

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by pyrale on Thursday March 14, 2019 @02:43PM (#19392166)

How many mbs for a hello world in forth ?

[ Parent | on HN ]

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by tsimionescu on Thursday March 14, 2019 @07:26PM (#19394942)

Hey, I said 'over other memory managed languages'! I really wouldn't compare it to one of the tiniest languages this side of asm. I also think Forth would be a harder sell in a corporation than Go. Or C++. Or ASM, probably.

[ Parent | on HN ]