Toot
Written by JF Bustarret on 2024-11-29 at 08:00
@ondrej Most benchmarks are partly/mostly useless, because they never run code as complex as a real world application.
The two most important properties are :
- CPU usage : the speed of both languages is similar BUT node.js uses a small worker pool to run CPU intensive code, and a few CPU intensive tasks might block the event loop, whereas Go can run thousands of goroutines simultaneously
- RAM usage : Go is usually more efficient, if you plan to use A LOT of RAM (GBs), it might be a better choice.
Unless your app is very CPU intensive or RAM intensive, I would say that the right choice is the language you know better.
=> More informations about this toot | View the thread | More toots from jfbus@piaille.fr
Mentions
=> View ondrej@social.synacek.org profile
Tags
Proxy Information
- Original URL
- gemini://mastogem.picasoft.net/toot/113565186614528197
- Status Code
- Success (20)
- Meta
text/gemini
- Capsule Response Time
- 226.052247 milliseconds
- Gemini-to-HTML Time
- 0.576352 milliseconds
This content has been proxied by September (ba2dc).