First thought I had this morning was that I started wondering if you could make "ChatGPT - The Board Game".

Each player would have 4x4 grid that would be educated during game, taking inspiration from mechanical matchbox tic-tac-toe player from 60s. And decision making would based on the conclusions of the AI and player.

Simplifying machine learning feedback ideas could foster some cool ideas for board games ;-)

Fresh ideas for remote attestation (vs Intel and AMD CA):

https://pom.ata.network/

#confidential #computing #machinehood

Tabs vs Spaces

I have good news!

The best available documentation on Rust-Linux still exists (when compared to anything else available, including Linux own documentation):

https://www.nccgroup.com/us/research-blog/rustproofing-linux-part-14-leaking-addresses/

I emailed to NCC Group and they've had just changed the URL. It is four part series, and the first part contains the URLs for rest of this series.

Documentation can be written from either "how"-angle or "why"-angle. For me the "how"-angle is irrelevant because I always read the source code from end to end :-) So I don't get whole a lot from existing kernel documentation.

#rust #linux #kernel

Why NPC's suck in games if the AI is great?

When Fallout 4 came out I stopped playing story oriented games because I started to feel like that I'm in a universe consisting of FSM's, which based on quiz trigger animation sequences ;-) No joke. Have not played story oriented games after 2015.

I guess you could improve a lot of taking some ideas of caching, tessellation algorithms and occlusion culling and apply them to AI. Like make "Quake solution" for AI. The best version would be used for the nearest entities, as it doesn't matter if the dudes far away are drunk/high ;-)

Second verse should be about unmuting the mic.

Everybody knows Phil Collins, i.e. the guy made gated reverb popular :-)

https://www.youtube.com/watch?v=m2siy25EWto

I have a company logo. It is "acid-ready" #inkscape

@glent Well, that's one way to look at it, I personally don't feel that way :-)

I'm working as a contractor through my own company so I guess I put that to my social media profiles instead of who I have a contract with :-) I pay my own salary for myself starting from October.

Right now I'm learning basics of #Inkscape because I don't have money to pay for a logo :-) It won't be great but it will be my own.

I'm using #IBM Plex font in this. I got the understanding that it is open source but have to check if the licensing terms allow to use it in a company logo.

Where the love for programming language, tool or technology begins, engineering ends ;-)

Engineering is art an of identifying things that suck, and finding ways to make them suck less.

#engineering #programming

I wish XCOM 3 will arrive some day. Every time I start playing Phoenix Point I get far but at some point I have too many stations and ships, get frustrated and give up.

Something in-between Phoenix Point and XCOM 2 in terms strategy/arcade factor would be nice.

BTW, speaking of games, why do NPC's suck so much if AI is so great? I cannot play story oriented games at all these days, not even the most visually pleasing like Cyberpunk, because despite all the nice graphics, I'm surrounded by FSMs. They just trigger stupid scripts causing pre-sequenced behavior. Why this is not fixed now that AI takes over everything? :-)

#commodore #amiga https://www.youtube.com/watch?v=AXCWYKSjHnI

Two years of being in the mainline is a short durationin kernel. Some feature patch sets take longer. For most part I'm wondering why people go crazy of not much happening on Rust side.

More patch sets like this are best possible effort for Rust enablement (and BTW, it is in C ;-) ):

https://lore.kernel.org/lkml/20240815173903.4172139-21-samitolvanen@google.com/

Once GCC-Rust catches up I'd expect more to happen as that will unlock for instance embedded toolchains and give at least theoretical chance to have something with Rust in a defconfig.

I'd contribute and/or wait another 3-5 years before making any fast conclusions. Linux is no worse in this than any other operating system, which decades of legacy to worry about. There is no unfortunately fast path here anywhere.

In addition to the NCC Groups awesome article series RTIC demonstrates how a low-level architecture can be documented without requiring enormous stretch in understanding all the nitty gritty details of Rust:

https://rtic.rs/2/book/en/

RTIC is a hard real-time OS framework. The documentation has exactly the domain information that helps to match the core concepts to the Rust artifacts and quickly also grasp those.

#rust #linux #kernel #rtic

I (accidentally) removed two symbols from a curl header that have been deprecated and without functionality for over 17 years.

Result: of course there is still code out there using those that now reports build failures...

Keeping absolute backwards compatibility is real work.

At the gates of hell - The Lake of Hell national park

i got so angry after reading this paper on LLMs and African American English that i literally had to stand up and go walk around the block to cool off https://www.nature.com/articles/s41586-024-07856-5 it's a very compelling paper, with a super clever methodology, and (i'm paraphrasing/extrapolating) shows that "alignment" strategies like RLHF only work to ensure that it never seems like a white person is saying something overtly racist, rather than addressing the actual prejudice baked into the model

From Jason Gunthorpe, maintainer of 5 Linux kernel subsystems:

IMHO the current situation of Rust does not look like success. It is basically unusable except for unmerged toy projects and it is still not obvious when that will change.

Today I learned that my Apple AGX GPU driver, which is the kernel side to the world's first and only OpenGL and Vulkan certified conformant driver for Apple Silicon GPUs, and also the FOSS community's first fully reverse engineered driver to achieve OpenGL 4.6 conformance, and which is used by thousands of Asahi Linux users in production, and that literally has never had an oops bug in production systems not caused by shared C code (unlike basically every other Linux GPU driver), is "an unmerged toy project".

(He works for Nvidia, I guarantee he's heard of it, considering we beat nouveau and NVK to GL 4.6 conformance.)

I guess this is what Linux kernel maintainers think of us Rust developers, that we only write "toy projects"...

Speaking of recent events at LKML concerning #Rust and #kernel, and also what I've said in some threads, the key element for reaching tolerance is #documentation.

This does not mean that bad behavior is acceptable but great documentation is best means to be preventive of such events ever occurring. Right now Rust kernel documentation almost does not exist.

What is an appropriate granularity for documentation? It is the level where an experienced kernel maintainer who has *never* used Rust can still understand your kernel patch.

That is the ideal. Obviously not always reached but underlines how bad state Rust documentation is ATM. I blame for most of this #Google and #Microsoft, not the developers. They are two private companies who spend vasta amounts of money for Rust kernel work. And they should know what I said already.