S
Size: a a a
2020 May 03
S
Отвратительно
Да
У
А если маленьких девочек
SQL
m
@iampiupiu do u wish u had a real vagina?
PP
@iampiupiu do u wish u had a real vagina?
ofc no
xui better
xui better
К
Но это не язык программирования
m
ofc no
xui better
xui better
so u prefer being a trap?
m
очен маладец ебанны
NV
Сначала надо выучить Си/Плюсы, несколько лет на них покодить, понять, какая это боль, перейти на Раст и уже в сравнении наслаждаться его удобством и возможностями как маной небесной
а потом делать доклады что плюсы лучше
У
Но это не язык программирования
Ну pl/sql, pl/pgsql ещё сверху
G
посчитал короче
G
генерируется примерно в 15 раз больше чем я пишу кода
G
по проекту в среднем
2020 May 04
EZ
Кек, никогда такого не было и вот опять
EZ
Re: Making Rust as Fast as Go
Hey all, as some keen-eyed commenters have pointed out, it looks like the rust program is not actually equivalent to the go program. The go program parses the string once, while the rust program parses it repeatedly inside every loop. It's quite late in Sydney as I write this so I'm not up for a fix right now, but this post is probably Fake News. The perf gains from jemalloc are real, but it's probably not the allocators fault. I've updated the post with this message as well.
The one-two combo of 1) better performance on linux & 2) jemalloc seeming to fix the issue lured me into believing that the allocator was to blame. I’m not sure what the lesson here is – perhaps more proof of Cunningham’s law? https://en.wikipedia.org/wiki/Ward_Cunningham#Cunningham's_Law [https://en.wikipedia.org/wiki/Ward_Cunningham#Cunningham's_Law]
chrfrasco, 8 hours ago
Hey all, as some keen-eyed commenters have pointed out, it looks like the rust program is not actually equivalent to the go program. The go program parses the string once, while the rust program parses it repeatedly inside every loop. It's quite late in Sydney as I write this so I'm not up for a fix right now, but this post is probably Fake News. The perf gains from jemalloc are real, but it's probably not the allocators fault. I've updated the post with this message as well.
The one-two combo of 1) better performance on linux & 2) jemalloc seeming to fix the issue lured me into believing that the allocator was to blame. I’m not sure what the lesson here is – perhaps more proof of Cunningham’s law? https://en.wikipedia.org/wiki/Ward_Cunningham#Cunningham's_Law [https://en.wikipedia.org/wiki/Ward_Cunningham#Cunningham's_Law]
chrfrasco, 8 hours ago
