БЛ @dereference_pointer_there
Showing posts older than #11025 · Back to latest
Forwarded from Neural Machine
Forwarded from Somewhere I Belong
Блог* #prog #rust #amazingopensource Typst is a new markup-based typesetting system that is designed to be as powerful as LaTeX while being much easier to learn and use. Typst has: * Built-in markup for the most common formatting tasks * Flexible functions…
“Should we convert our _ code to Rust?” is a question that comes up a lot. And a lot of the time the right answer is a pretty firm, “No.” So I thought it might be beneficial (and hopefully interesting) to walk through a case where the code involved was incredibly you-cannot-fuck-this-up business-critical and when we asked that question about it, we came back with a yes. Here’s what it was, how we got to that answer, and what we did about it.
The bottom line is that C++ has caused more than a few situations where we wanted to do something or add a feature and it’s just like… that’s a cool idea, but it’s just not worth the uphill battle against the language. And it was to the point where any change carries the risk of unforeseen consequences.
Dolboeb-driven Development https://www.youtube.com/watch?v=4XCkeN0XuqA
Since its launch in 2007, the Wii has seen several operating systems ported to it: Linux, NetBSD, and most-recently, Windows NT. Today, Mac OS X joins that list.
In this post, I’ll share how I ported the first version of Mac OS X, 10.0 Cheetah, to the Nintendo Wii. If you’re not an operating systems expert or low-level engineer, you’re in good company; this project was all about learning and navigating countless “unknown unknowns”. Join me as we explore the Wii’s hardware, bootloader development, kernel patching, and writing drivers - and give the PowerPC versions of Mac OS X a new life on the Nintendo Wii.
Блог* Ландук думает, что это эвфемизм, лол
шитпостинг. Чеклист приличного security researcher - есть аниме тян аватарка - возможно транс - онлифанс Не понимаю претензий к выбору компании
Forwarded from шитпостинг.
Forwarded from xecut_channel
GDB pretty printing w/ Python is really powerful, but also it's ridiculously high friction compared to Microsoft's .natvis.
Completely aside from any syntactic whatever, you can't (safely) load any ol' Python script in a project's repo, but you can safely load up associated .natvis files, which makes Microsoft's solution vastly superior for library users.
And there's really no reason that GDB and LLDB can't just implement .natvis support out of the box. (Yes, I know there are Python libraries that add a subset of .natvis support to GDB, but that doesn't solve the "out of the box" part at all.) Or hell, if they really hate Microsoft (who doesn't?) then implement their own declarative debug visualizer format.
(This post brought to you by me using Clang 22 for _Defer via mingw and now having to write *ing Python to make my pure C project comfortably debuggable.)
In April 2026, Canonical disclosed 44 CVEs in uutils, the Rust reimplementation of GNU coreutils that ships by default since 25.10. Most of them came out of an external audit commissioned ahead of the 26.04 LTS.
I read through the list and thought there’s a lot to learn from it.
What’s notable is that all of these bugs landed in a production Rust codebase, written by people who knew what they were doing, and none of them were caught by the borrow checker, clippy lints, or cargo audit.
<...>
If you write systems code in Rust, this is the most concentrated look at where Rust’s safety ends that you’ll likely find anywhere right now.
Блог* #prog #article Four Kinds of Optimisation (перевод) TL;DR: 1. Использование более хорошего алгоритма 2. Использование более хорошей структуры данных 3. Использование более низкоуровневой системы 4. Принятие менее точного решения Разумеется, по каждому…
A little while back I wrote about what I considered to be the four main kinds of optimisation:
<...>
However, none of this excuses the fact that I missed off a technique that, even when I wrote that post, I use frequently:
5. Use parallelisation.
Parallelism has long held promise but for a long time we couldn’t rely on hardware or programming languages when it came to parallel programming. I hope I’ve explained explain why I – and, I think, many other programmers – have consequently been afraid of exploiting parallelisation.
Nearly all those problems are now in the past and – finally! – we are starting to see somewhat widespread use of software that exploits the parallelisation potential of our hardware.
