Forwarded from Вопреки всему | Итиль Тёмная
ТАСС
Вице-президент Ирана Мансури подтвердил гибель президента Раиси при крушении вертолета
Ребят, кто призывали смерть на президента раиси, магия не понимает сарказма, называйте Россию правильно
😁40🤡16💩6🥴1
Папищеки, предлагаю новый интерактив: вы присылаете мне свои нюдсы , а я на них смотрю .
❤🔥17🤡10😁2💩2🥴2🔥1🤮1
#prog #rust #article
Unwind considered harmful?
Нико аргументированно показывает, почему имеет смысл если не полностью убрать раскрутку стека, то как минимум радикально снизить её использование.
Unwind considered harmful?
Нико аргументированно показывает, почему имеет смысл если не полностью убрать раскрутку стека, то как минимум радикально снизить её использование.
👍3
Forwarded from Generative Anton (Anton Repushko)
Волшебная история про то, как в 90ые годы в Германии все сообщения Air Traffic Control передавались через headless Emacs, а роутер сообщений был написан на Emacs-Lisp.
In Germany, a Herr Doktor is always right (they have forgiven Moses by now for not having space on the stone tablets, but it really is the 11th Commandment). This one worked at Symbolics before so knew one programming language: Lisp. He wanted to code the message router in Lisp because of the “complex” (meh) requirements, but there was no Lisp (or no Lisp in budget) for HP/UX so he was stuck. I told him about Emacs, gave him my tape with the ports, and maybe that was a mistake 😉
A week later - I helped out finishing the 4GL UI in the meantime and completed the messaging protocol - he called me in, quite happy. He showed me the code - page after page of Emacs Lisp, with exactly zero comments “because Lisp is self-documenting”. I got scared, it was an air traffic control system after all, but I was no Herr Doktor so I whipped up the DCE native code for Emacs, made a hack to have it start headless in message router server mode, and we got messages to flow. I did a code hand-over, and drove back home a couple of days later. The “self-documenting” code, as far as I know, landed in production so at least for a while, all ATC message routing in Germany was done through Emacs.
In Germany, a Herr Doktor is always right (they have forgiven Moses by now for not having space on the stone tablets, but it really is the 11th Commandment). This one worked at Symbolics before so knew one programming language: Lisp. He wanted to code the message router in Lisp because of the “complex” (meh) requirements, but there was no Lisp (or no Lisp in budget) for HP/UX so he was stuck. I told him about Emacs, gave him my tape with the ports, and maybe that was a mistake 😉
A week later - I helped out finishing the 4GL UI in the meantime and completed the messaging protocol - he called me in, quite happy. He showed me the code - page after page of Emacs Lisp, with exactly zero comments “because Lisp is self-documenting”. I got scared, it was an air traffic control system after all, but I was no Herr Doktor so I whipped up the DCE native code for Emacs, made a hack to have it start headless in message router server mode, and we got messages to flow. I did a code hand-over, and drove back home a couple of days later. The “self-documenting” code, as far as I know, landed in production so at least for a while, all ATC message routing in Germany was done through Emacs.
🔥13😱4😁2🤔2