Ну и срань
Хабр в плюсе, Яндекс в плюсе, а вот читатели получают здоровенный неотключаемый баннер к каждому сниппету кода, который ещё и требует логина в аккаунт Яндекса и (по отзывам) работает крайне паршиво.
Если используете uBlock, то в комментариях подсказали фильтр для того, чтобы убрать:
Хабр в плюсе, Яндекс в плюсе, а вот читатели получают здоровенный неотключаемый баннер к каждому сниппету кода, который ещё и требует логина в аккаунт Яндекса и (по отзывам) работает крайне паршиво.
Если используете uBlock, то в комментариях подсказали фильтр для того, чтобы убрать:
habr.com##.code-explainer
Хабр
Теперь Хабр может объяснить, что это за код
TL; DR Мы встроили SourceCraft во все кодовые сниппеты в публикациях на Хабре. Он объяснит, что делает код. Как это работает, кому нужно и как использовать — читайте ниже. Хабр — площадка для...
😭14👍1👎1😁1💩1🤡1
Forwarded from Kedr to Earth | Земля, я Кедр (✅ Yuri Ammosov)
РИА Новости накануне зимней сессии предупреждает: ДУМАТЬ ВРЕДНО !
https://ria.ru/20251209/vrach-2060710660.html
Длительная умственная нагрузка может привести к развитию гипертонии, аритмии и ишемии сердца.
Как пояснил врач, когнитивное переутомление - это не просто усталость мозга, оно отражается на вегетативной регуляции сердца. Так, уже после нескольких часов напряженной умственной деятельности учащается пульс, повышается давление, растет уровень кортизола.
После четырех-пяти часов сложной умственной работы меняется обмен в префронтальной коре и повышается уровень глутамата - медиатора, связанного с утомлением и стрессом.
Врач порекомендовал ограничивать интенсивную интеллектуальную работу тремя- четырьмя часами в день, а также делать паузы каждые 60–90 минут.
https://ria.ru/20251209/vrach-2060710660.html
РИА Новости
Врач рассказал об опасности длительной умственной нагрузки
Длительная умственная нагрузка может привести к развитию гипертонии, аритмии и ишемии сердца, рассказал РИА Новости главный кардиолог кардиологического центра... РИА Новости, 09.12.2025
💯5🤩4🥴3
shitposting 3.0 [+ dragons]
Photo
That is awesome.
Does everyone know the story of Lot?
Angels come to check out the town because omni-present God wants a report and can't get it by simply being everywhere at once. So the town goes to rape the angels and Lot offers his two daughters to the rape gang instead.
The gang refuses, so Lot goes to his future sons-in-law and tries to get them out of town with his daughters (after offering them up to a rape gang... seriously). The sons-in-law don't go.
The angels tell Lot and his wife and two daughters to leave and don't look back. Lot gets a pass for being the one good guy in town... (in spite of offering his daughters to a rape gang... seriously)
After they head out of town, Lot, who has received a pass for offering his daughters to a rape gang, notices that his wife is incinerated into a pillar of salt on the spot for the great sin of LOOKING BACK.
(too bad she didn't commit a minor sin like offering her own kids to a rape gang instead, then she'd be alive)
After Lot and his daughters get to the caves, his daughters are sad that their husbands to be aren't around to impregnate them, providing the only possible value to women (having children). So the daughters get their father rip roaring drunk, and even though he's super old, Lot has sex with both his daughters and impregnates both of them.
Note that the ONE PERSON IN THE STORY who didn't do something abominable... Lot's wife... is the one who was crisped to a pillar of salt.
What a great guy... that Lot... and his great daughters...
Source
👍4🥴3😁1🙏1🤷1
#prog #article
Afternoon project: JPEG DCT text lossifizer
Чел сделал штуку (веб-приложение), которая применяет к тексту процесс, аналогичный сжатию с потерями в JPEG: разбирает текст как семпл на частоты, огрубляет их и собирает обратно.
Пара моментов:
В JPEG квантизация в основном огрубляет (и отбрасывает) высокие частоты. В случае же с текстом это приводило к слишком большой деградации, поэтому программа сначала отбрасывает низкие частоты.
Первоначальная реализация использовала ASCII-коды напрямую, но комментатор предложил другую кодировку, в которой символы со схожим написанием/звучанием имели близкие коды, и это положительно сказалось на читаемости сжатого текста даже с весьма большим огрублением.
Afternoon project: JPEG DCT text lossifizer
Чел сделал штуку (веб-приложение), которая применяет к тексту процесс, аналогичный сжатию с потерями в JPEG: разбирает текст как семпл на частоты, огрубляет их и собирает обратно.
Пара моментов:
В JPEG квантизация в основном огрубляет (и отбрасывает) высокие частоты. В случае же с текстом это приводило к слишком большой деградации, поэтому программа сначала отбрасывает низкие частоты.
Первоначальная реализация использовала ASCII-коды напрямую, но комментатор предложил другую кодировку, в которой символы со схожим написанием/звучанием имели близкие коды, и это положительно сказалось на читаемости сжатого текста даже с весьма большим огрублением.
🤯9❤4
Forwarded from AlexTCH
Dear colleagues,
At AWS re:Invent 2025 in Las Vegas, we announced the AWS Nitro Isolation Engine [1, 2, 3], a formally verified enhancement to the AWS Nitro System that enforces isolation between virtual machines hosted on AWS's new Graviton5-based EC2 instances.
Nitro Isolation Engine represents a significant deployment of mechanized proof in production infrastructure, and we therefore wanted to bring this to the attention of the formal methods and programming languages communities. This work builds directly on decades of advances in interactive theorem proving, program verification, and programming languages theory, alongside landmark projects—such as, seL4 [4], CertiKOS [5], SeKVM [6], and many others—that were inspirations for this work.
What is Nitro Isolation Engine?
Nitro Isolation Engine is a small, trusted computing base written in Rust that sits beneath the AWS Nitro Hypervisor, providing a security isolation boundary between the hypervisor and guest virtual machines, and between co-tenanted guest virtual machines. The Nitro Isolation Engine controls the critical hardware features required for isolating customer workloads, primarily control of Stage Two translation tables.
The verification effort
Nitro Isolation Engine was designed with verification in mind from the first line of code. Nitro Isolation Engine is subject to AWS’s existing rigorous engineering practices, including the deployment of property-based-testing and lightweight formal methods, for example the Kani bounded model checker for Rust [7].
Building atop this foundation, we have specified and verified the correctness of Nitro Isolation Engine in Isabelle/HOL [8]. Our model and proofs consist of around 260,000 lines of machine-checked models and proofs. Specifically, we have proved:
Functional correctness: Nitro Isolation Engine behaves as specified for all operations: virtual machine creation, memory mapping, instruction and data abort handling, and so on. As corollaries of our total verification style, we have also proven memory-safety, termination, and absence of runtime errors, providing our modelling assumptions are accurate.
Confidentiality: We prove a noninterference-style property demonstrating the confidentiality of guest virtual machine states, formalized as indistinguishability preservation up-to permitted flows of declassified information out of a guest.
Integrity: The integrity of guest virtual machine state is formalized as a safety property, showing that the private state of one virtual machine is unaffected by operations modifying another distinct virtual machine.
In addition, we have applied Iris [9] and Verus [10] to prove the correctness of the Nitro Isolation Engine’s concurrency primitives, including ticket locks, mutexes, and rendezvous barriers.
For functional verification, we defined μRust, a restricted subset of Rust expressive enough to write Nitro Isolation Engine but amenable to formal reasoning and embedded its semantics into Isabelle/HOL. Specifications are written in separation logic, and proofs proceed via weakest precondition calculus with custom automation. We have made our verification infrastructure open source as the AutoCorrode library [11] for Isabelle/HOL, which may be of independent interest.
Regards,
Automated Reasoning Group, AWS
[1]: https://www.aboutamazon.com/news/aws/aws-graviton-5-cpu-amazon-ec2
[2] : https://www.youtube.com/watch?v=3Gt-30Fm38U https://www.youtube.com/watch?v=3Gt-30Fm38U
[3]: https://www.youtube.com/watch?v=b0P55gHhG4g
[4]: https://sel4.systems/
[5]: https://flint.cs.yale.edu/certikos/
[6]: https://www.usenix.org/conference/usenixsecurity21/presentation/li-shih-wei
[7]: https://github.com/model-checking/kani
[8]: https://isabelle.in.tum.de/
[9]: https://iris-project.org/
[10]: https://github.com/verus-lang/verus
[11]: https://github.com/awslabs/AutoCorrode
At AWS re:Invent 2025 in Las Vegas, we announced the AWS Nitro Isolation Engine [1, 2, 3], a formally verified enhancement to the AWS Nitro System that enforces isolation between virtual machines hosted on AWS's new Graviton5-based EC2 instances.
Nitro Isolation Engine represents a significant deployment of mechanized proof in production infrastructure, and we therefore wanted to bring this to the attention of the formal methods and programming languages communities. This work builds directly on decades of advances in interactive theorem proving, program verification, and programming languages theory, alongside landmark projects—such as, seL4 [4], CertiKOS [5], SeKVM [6], and many others—that were inspirations for this work.
What is Nitro Isolation Engine?
Nitro Isolation Engine is a small, trusted computing base written in Rust that sits beneath the AWS Nitro Hypervisor, providing a security isolation boundary between the hypervisor and guest virtual machines, and between co-tenanted guest virtual machines. The Nitro Isolation Engine controls the critical hardware features required for isolating customer workloads, primarily control of Stage Two translation tables.
The verification effort
Nitro Isolation Engine was designed with verification in mind from the first line of code. Nitro Isolation Engine is subject to AWS’s existing rigorous engineering practices, including the deployment of property-based-testing and lightweight formal methods, for example the Kani bounded model checker for Rust [7].
Building atop this foundation, we have specified and verified the correctness of Nitro Isolation Engine in Isabelle/HOL [8]. Our model and proofs consist of around 260,000 lines of machine-checked models and proofs. Specifically, we have proved:
Functional correctness: Nitro Isolation Engine behaves as specified for all operations: virtual machine creation, memory mapping, instruction and data abort handling, and so on. As corollaries of our total verification style, we have also proven memory-safety, termination, and absence of runtime errors, providing our modelling assumptions are accurate.
Confidentiality: We prove a noninterference-style property demonstrating the confidentiality of guest virtual machine states, formalized as indistinguishability preservation up-to permitted flows of declassified information out of a guest.
Integrity: The integrity of guest virtual machine state is formalized as a safety property, showing that the private state of one virtual machine is unaffected by operations modifying another distinct virtual machine.
In addition, we have applied Iris [9] and Verus [10] to prove the correctness of the Nitro Isolation Engine’s concurrency primitives, including ticket locks, mutexes, and rendezvous barriers.
For functional verification, we defined μRust, a restricted subset of Rust expressive enough to write Nitro Isolation Engine but amenable to formal reasoning and embedded its semantics into Isabelle/HOL. Specifications are written in separation logic, and proofs proceed via weakest precondition calculus with custom automation. We have made our verification infrastructure open source as the AutoCorrode library [11] for Isabelle/HOL, which may be of independent interest.
Regards,
Automated Reasoning Group, AWS
[1]: https://www.aboutamazon.com/news/aws/aws-graviton-5-cpu-amazon-ec2
[2] : https://www.youtube.com/watch?v=3Gt-30Fm38U https://www.youtube.com/watch?v=3Gt-30Fm38U
[3]: https://www.youtube.com/watch?v=b0P55gHhG4g
[4]: https://sel4.systems/
[5]: https://flint.cs.yale.edu/certikos/
[6]: https://www.usenix.org/conference/usenixsecurity21/presentation/li-shih-wei
[7]: https://github.com/model-checking/kani
[8]: https://isabelle.in.tum.de/
[9]: https://iris-project.org/
[10]: https://github.com/verus-lang/verus
[11]: https://github.com/awslabs/AutoCorrode
Aboutamazon
AWS introduces Graviton5—the company’s most powerful and efficient CPU
Fifth generation chip provides the best price performance for a broad range of workloads in Amazon EC2.
🫡3🔥1🤔1🎉1🌚1