> We are completely overwhelmed, of course.

[hipsterelectron@circumstances.run]

@daemonspudguy @zzt @lykso @c0dec0dec0de yes but not in the L4 style. a "monolithic" kernel actively abdicates security boundaries or protocols of any sort and is impossible to optimize to application-specific access patterns. ring 0 is for memory allocations and not for hardware. explicit message buffering (unlike seL4) enables strong guarantees around data persistence and data copies can be used to safely transfer across security contexts as well as memory hierarchy regimes. the bullshit linux does to pass around pages to avoid copies is incredibly archaic and it's very cache-unfriendly

[hipsterelectron@circumstances.run]

@daemonspudguy @zzt @lykso @c0dec0dec0de most of POSIX can be supported but not fucking pthreads. the entire concept of a mutex is completely broken and that's why deadlocks are even allowed to happen. haven't figured all that out yet but i think any constructs built on top of c11 atomics need to have clear semantics for progress. the ring buffer i've built supports stuff like "block until N bytes are available to write" and it makes parallelism so much easier when data structures provide guarantees around data flow rather than control flow

[hipsterelectron@circumstances.run]

@daemonspudguy @zzt @lykso @c0dec0dec0de alexia massalin did the absolute coolest fucking shit ever with only an atomic compare-and-swap instruction in her synthesis kernel https://pages.cs.wisc.edu/~bart/736/papers/synthesis.pdf i'm doing a lot more with filesystem i/o and scheduler control because the scheduler is a security boundary and no process should have a global view of all files

[lykso@tiny.tilde.website]

@hipsterelectron That sounds fantastic, TBH. Really looking forward to seeing what you end up writing!
@daemonspudguy @zzt @c0dec0dec0de

[hsza@social.tudbut.de]

@zzt “we are drowning in slop, the solution is obviously more slop”

[hsza@social.tudbut.de]

@zzt it will be vindicating seeing linux go on that list

[hsza@social.tudbut.de]

@daemonspudguy @c0dec0dec0de @zzt it is the right-wing nutjob framing of “ethical project”

[grahamperrin@mastodon.bsd.cafe]

@raster I can not read the conversation here, thanks to @zzt for the block /s

I see that he enjoys the phrase "fucking slop", so you can point him and his fucking awful.systems to the open (non-blocked) anti-AI discussion linked below.

Alternatively, with less profanity:

― sloppy human systems.

https://www.reddit.com/r/freebsd/comments/1vtgx7t/antiai_open_source_has_an_enemy_in_common_but/

#AI #openness

[haihappen@social.anoxinon.de]

@zzt i am wondering if any of the benchmarks is "generate compiler for arbitrary language and architecture" with a testset that is just arbitrary code to compile amd execute (which is not oart of the context).
I guess not, that could lead to embaressment and admitting they set a trillion dollars aflame for spicy autocomplete

[glitterbean@wehavecookies.social]

@zzt what?

[paul@notnull.space]

@zzt "some hallucinations"

[ozzelot@mstdn.social]

@zzt
They embraced, they extended, now comes the extinguishing (even if some of them believe it's extension)

[ozzelot@mstdn.social]

@hsza
"The only thing that can stop a bad guy with a slop extruder is a good guy with a slop extruder"
@zzt

[mawhrin@circumstances.run]

@grahamperrin take the block like a real poster and don't whine about it. (calling reddit “open” is a beautiful joke.)

[grahamperrin@mastodon.bsd.cafe]

@mawhrin try commenting like a real reader and don't misunderstand what's written.

I described a single discussion, not Reddit, as "open (non-blocked) anti-AI".

Would you like to know why?

Cc @raster

[mawhrin@circumstances.run]

@grahamperrin please do not re-insert into the conversation people i deliberately removed in order to remove clutter in their threads, thanks.

i had a look at your timeline and now i do understand why people might not want to communicate with you; i just joined their number.

please do not reply, thanks in advance.

[grahamperrin@mastodon.bsd.cafe]

@mawhrin don't take an interest without properly knowing the facts and then feign disinterest.

[grahamperrin@mastodon.bsd.cafe]

@raster here's the less open public discussion, with greater engagement:

FreeBSD, AI, and LLMs

https://www.reddit.com/r/freebsd/comments/1vthk9s/freebsd_ai_and_llms/

― including a comment from a member of the FreeBSD Core Team.

[ryencode@mstdn.ca]

@ozzelot @hsza @zzt

I miss the days when this used to mean having a poorly configured and setup 3D printer.

[foolishowl@social.coop]

@bstacey @zzt That's kind of the root of the problem: Linux has been dependent on corporate development for a long time.