https://www.opennet.ru/opennews/art.shtml?num=62725

"Пользователям KDE рекомендовано попробовать перейти на использование сеанса на базе протокола Wayland, так как разработчики KDE практически прекратили тестирование сеанса на базе X11"

Ну все, лед тронулся, через пару лет про X можно будет просто забыть, эффект будет лавинообразный.

https://www.opennet.ru/opennews/art.shtml?num=62727

Драма продолжает набирать обороты.

Закончил читать шедевральный #rant https://izzys.casa/2024/11/on-safe-cxx/

Rant про состояние сообщества С++, rant огромный, читал я его, с перерывами, несколько дней. Если соберетесь - запаситесь попкорном, оно того стоит. Видно, что у человека просто бомбит от происходящего.

"In reality, this post isn’t really about Gaby Dos Reis, Herb Sutter, and the creator of C++, Bjarne Stroustrup. I lied. It’s about toxic masculinity (oh hey there’s that word) in language design. Remember when I mentioned the weird schoolyard insults and constant bizarre emasculation of Rust and its users? Good"

"This post isn’t about feminism in language design"

"For those of you not in the know, a llamafile is basically for turning an LLM’s weights into an executable. Which is where this post is actually going because surprise shithead, I lied again about this post’s topic. Ok, you’re probably wondering at this point “What the fuck does AI have to do with C++, let alone memory safety in C++” (that or you’re probably along for the ride at this stage and are just rolling with it), and it’s sadly more related than you might realize"

"This article wasn’t ever really about C++ the language. It was about C++ the community, because that’s what C++ really is. Bjarne is too caught up in his own bullshit to see it, same as Herb and Gaby, and as long as this is the situation we’re in, C++ will never be “safe” as a community. You could have the perfect language, but if no one uses it, because there’s no community, what do you have?"

"C++ is not in a unique situation. Far from it. This story has been told before. Leadership refusing to let the next epoch come around, destroying themselves and the world in the process. Leaving the rest of us to pick up the pieces, convincing some of us to take on a mandate to repeat this cycle, to make sure the world stays out of the hands of those would change it, while others shirk this mandate and take upon themselves a different path. Discouraging jolly cooperation, as long as we think we only have these two options before us"

ну я

#llvmweekly

ВНЕЗАПНО послать всех нахуй не вышло, и был принят исходный proposal - https://github.com/llvm/llvm-project/pull/127006/commits/d5492cfe0a52512b981a452dea2a373d640e1416

https://www.phoronix.com/news/Torvalds-Override-On-Rust-Code

Миша с похорогикса пишет, что Линус таки собирается вмержить патчи с биндингами в Rust:

"Today he's out with another mailing list post where he notes that Linus Torvalds mentioned in private he would override maintainer vetoes on Rust code within the kernel"

В целом, это правильно, а иначе эксперимент просто пришлось бы завершить.

Чо началось то

From: "H. Peter Anvin" <hpa@zytor.com>
. . .
Once again, let me emphasize that I do *not* suggest that the kernel code should use STL, RTTI, virtual functions, closures, or C++ exceptions. However, there are a *lot* of things that we do with really ugly macro code and GNU C extensions today that would be much cleaner – and safer – to implement as templates. I know ... I wrote a lot of it :)

One particular thing that we could do with C++ would be to enforce user pointer safety.

https://lore.kernel.org/rust-for-linux/326CC09B-8565-4443-ACC5-045092260677@zytor.com/

https://www.tgoop.com/itpgchannel/2189 - я как-то писал, что С++ для ядра гораздо более разумный выбор, чем Rust, но, к сожалению, для Линуса это значило бы потерять лицо.

r/ #aww
Состояние после очередного рабочего дня