Notices by Sergey Bugaev (bugaevc@floss.social)

And now I hacked up Pango to:
1. finally do per-layout limits on the number of lines (instead of per-paragraph, which makes no sense),
2. do a better job ellipsizing the last line even when the line itself fits, but there are further lines that don't (due the the height limit or line number limit) — this still needs more polish, but it works somewhat,
3. and to finally have a proper way to disable wrapping, PANGO_WRAP_NONE (wanna guess how Gtk.Label.set_wrap (false) was working until now?)
#gtk

Oh my freaking god, Tuba on my branch… just works now? With no warnings or criticals, and no broken layout?

This is a port to Adw.WrapBox (kindly made by @GeopJr), with fixes to Adw.WrapBox and further reworking of Gtk.Box (and Gtk.Window).

#GTK

@janneke amazing!

@goku12 almost every time a news item about gccrs is posted, the comments on r/rust, HN, and even LWN and overwhelmingly negative.

"essentially apologize and explain themselves" refers to their recent guest blog post in the official Rust blog, where they rebuff common criticisms and try to convince you that they're not out to harm the Rust ecosystem https://blog.rust-lang.org/2024/11/07/gccrs-an-alternative-compiler-for-rust.html

@goku12 here's a comment on r/rust by one of the gccrs devs about how un-welcome that makes them feel https://www.reddit.com/r/rust/comments/12y85ww/comment/jhrqz72

It's beyond ridiculous that instead of receiving gratitude, cheers, encouragement, and support (both moral and financial), #GCC #Rust developers have to essentially apologize and explain themselves in order not be judged by the Rust community.

Imagine you come across a small but somewhat useful piece of software, written in C or C++, built using a typical buildsystem like Meson or straightforward Make. There aren't any unreasonable dependencies or version requirements either.

Think something like scdoc.

But, there's a Dockerfile in the repo (starting FROM an outdated ubuntu image, naturally), all the build instructions prominently recommend doing the build in Docker, ...

1/3

...and all the usage instructions just as prominently recommend using a pre-built Docker image provided by them.

Should you file a bug report, where all signs point to a rather obvious issue in their code, and happen to mention that you weren't in fact using Docker, but just built the software in the natural & straightforward way, the maintainers close the report, saying that non-Docker builds are unsupported, ...

2/3

since they don't have the capacity nor the desire to support the multitude of differing environments & distros.

Finally, upon startup, the software checks to see if it's running inside Docker, and prints a loud & annoying warning about an unsupported configuration otherwise.

3/3

@brooke rather, of gender source, which GPL defines as "preferred form of the work for making modifications" 😉

GNU #Mach on AArch64 now boots up and runs a simple userspace hello world on ✨ real hardware ✨ , booted from U-Boot! 🎉

Kudos to Manolo De Medici for testing & helping track down issues!

If you want to help with Mach / #Hurd on AArch64 and know anything about writing drivers and/or have an AArch64 board, please get in touch :)

Looks like the "break rust" easter egg that I added last year is being removed from GCC #Rust over being "bloat" and "insulting the GCC users"

Oh well

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629

@lanodan @brooke x64 must be the instruction set of Intel 364, 464, 564, and 646 processors, the latter two also known as Penti64 and Penti64 2 :D

@brooke whoever decided to refer to AArch64 as ARM64 is to blame

Is Linux secure?

Let me rephrase, is a huge pile of C code, running in privileged mode in a shared address space, highly concurrent, using its own homegrown memory model based on volatile instead of the one the language spec defines and the compilers implement, dealing with untrusted data, implementing many complex protocols, data formats, & functionality, managing a bunch of "objects" with complex ownership and lifetime semantics, embedding its own JIT — secure?

Clarification: I'm not advocating for alternative kernels (certainly not for Mach / Hurd, which are a lot more insecure — I would know 🙂)

I'm saying, Linux is here to stay for decades and centuries. Look at what corner we've painted ourselves into.

Note to self, to insert ^L aka form feed aka \f:

in Emacs, C-q C-l
in Nano, M-Shift-V ^L

(both of these are enabling raw/verbatim input mode and then entering Control-L)

@yosh it's only a fast Fourier transform if it comes from the Fourier region of France, otherwise it's just a sparkling fast change

I cannot overstate just how important the GCC Rust project is for, like, the future of computing, and everything.

And yet, under any post on LWN / HN / Reddit, 90% of discussion is people demanding justification for the project's existence. Because how *dare* they develop a compiler that someone doesn't see a use case for?!

git: 'git' is not a git command