3 ms·
Some points in that page don't seem like valid criticism. Like, complaining that the compiler is not "zero dependency" on Linux, because it depends on glibc?
by yongjik 5y ago
Some points in that page don't seem like valid criticism. Like, complaining that the compiler is not "zero dependency" on Linux, because it depends on glibc?
Also, allocating a fixed 1000 byte region at the start of a program is not a "memory leak". In fact even glibc has tons of such "initial fixed cost" allocations - IIRC valgrind has built-in "suppression file" to ignore these allocations. (It would be a memory leak if the compiler allocated new 1000 byte chunks every time println is called, but the article doesn't demonstrate it so I guess I'll never know.)
- deleted 5y ago[deleted]
- the_duke 5y agoIIRC one of the original claims was to skip libc and do syscalls manually, like Go used to do on Linux. So listing it makes sense in that context.
- amedvednikov 5y agoNo, this was never claimed.
- GoblinSlayer 5y agoThat sounds more like a bugfix. Doing syscalls manually is a rather perverse exercise, which go thoroughly proved.