Rust wgpu now has a
-
Rust wgpu now has a .agents/skills, a .claude/skills, an AGENTS.md, and a CLAUDE.md.
Increasingly wondering if my goal of living in a way that I never benefit from the actions of generative AI users and generative AI users never benefit from the actions of me is going to inherently mean never using hardware-accelerated video on a computer again.
The scale of work you bring attention to is at once enlightening and soul-crushing
#I-still-hope-to-help-do-it-someday -
@MaddieM4 @mcc @amarioguy our usual take on the role of idealism is that we need to know what our ideal world is, so that we can evaluate each step by whether it takes us closer or further
without that, activists go in circles and each new group has to dismantle the previous group's work
@MaddieM4 @mcc @amarioguy that's very much the spirit in which we're offering our thoughts, we're not trying to say don't use RISC-V. we have a RISC-V machine ourselves that we intend to use to test our compiler when we get to that stage of things.
-
@eniko redox is currently capable of handling one channel of mono sound output and i think no support for sound input whatsoever
@mcc yeah. I'm uh, aiming for CPU framebuffer rendering, for exactly those reasons
I mean. The affine textured low res low poly PS1 aesthetic is in right now? At least that's what I tell myself
-
@lispi314 I don't think they're discussing this. This is I believe a very big problem but not my concern at the current time because (1) you need a programming language; that's not optional (1.5) i no longer acknowledge the existence of C (2) there are already at least four Rust backends and at least two frontends (3) i am much more confident i can create an independent Rust implementation than I am confident that I can do literally *any* of the projects described in the thread above.
-
@amarioguy @mcc @MaddieM4 and yeah if we had our way we'd remove like at least 80% of the functionality modern ISAs have, as security hazards. we realize we're prone to the nostalgia bias here, of course, but CPUs are an unremovable part of attack surface for any computer and we don't think we're being unreasonable in wanting to have even the slightest confidence in their safety
@ireneista @amarioguy @mcc @MaddieM4 DECSYSTEM-10 ISA with hypervisor facilities added and the floating-point facilities removed and offloaded to the GPU/vector math processor
-
This thread is probably meandering and maybe solipsistic. My point is this: My weird background means I can look at this staircase full of missing stairs, identify one step, and go, "I can fix that". But I don't know if there's enough of me to fix multiple steps. I haven't decided what to do from here. Pick a step and fix it anyway? Pick a "fun" project, like the GPU [which face it, even if I finished it chances are not high more than 3 people would ever use it]? Give up and learn electric bass?
@mcc Meanwhile I feel silly for trying to remain fairly high up in the stack. I look at the missing steps and can only think about how not terribly helpful I would be right now trying to like… help with a kernel. Hell I took my eyes off of audio for a while because “the world needs more music theory!”
-
@mcc Meanwhile I feel silly for trying to remain fairly high up in the stack. I look at the missing steps and can only think about how not terribly helpful I would be right now trying to like… help with a kernel. Hell I took my eyes off of audio for a while because “the world needs more music theory!”
@griotspeak Thinking only in a utilitarian way and not contemplating concepts such as joy:
If you're helpful high in the stack, but don't think you'd be helpful low in the stack, wouldn't it make more sense to stay high in the stack, where you're useful?
-
@ireneista @amarioguy @mcc @MaddieM4 DECSYSTEM-10 ISA with hypervisor facilities added and the floating-point facilities removed and offloaded to the GPU/vector math processor
@decay @ireneista @amarioguy @MaddieM4 i don't want to write for the DEC PDP series anymore, I've written enough C
-
@eniko redox is currently capable of handling one channel of mono sound output and i think no support for sound input whatsoever
-
@MaddieM4 @mcc @amarioguy that's very much the spirit in which we're offering our thoughts, we're not trying to say don't use RISC-V. we have a RISC-V machine ourselves that we intend to use to test our compiler when we get to that stage of things.
@ireneista @mcc @amarioguy That is also true. Navigation is complex. Without a north star it's impossible.
-
@mcc yeah. I'm uh, aiming for CPU framebuffer rendering, for exactly those reasons
I mean. The affine textured low res low poly PS1 aesthetic is in right now? At least that's what I tell myself
@mcc anyway yeah you're right we do need a kernel. Something that goes "here's file system, video, sound, and input" and then from there things get a lot more manageable. At least for games
-
@decay @ireneista @amarioguy @MaddieM4 i don't want to write for the DEC PDP series anymore, I've written enough C
@mcc @ireneista @amarioguy @MaddieM4 an extremely fair point
-
@griotspeak Thinking only in a utilitarian way and not contemplating concepts such as joy:
If you're helpful high in the stack, but don't think you'd be helpful low in the stack, wouldn't it make more sense to stay high in the stack, where you're useful?
@mcc It would but I am genuinely not sure how possible that is when so many foundational pieces are being compromised
-
@decay @ireneista @amarioguy @MaddieM4 i don't want to write for the DEC PDP series anymore, I've written enough C
@mcc @decay @ireneista @MaddieM4 part of me does sorta wish that rust wasn't so dependent and reliant on cargo and such...
-
@decay @ireneista @amarioguy @MaddieM4 i don't want to write for the DEC PDP series anymore, I've written enough C
@mcc @decay @amarioguy @MaddieM4 we're not suggesting eliminating the MMU, just, like, refactoring a bit so it isn't so many abstraction layers that subvert each other
-
@mcc @decay @amarioguy @MaddieM4 we're not suggesting eliminating the MMU, just, like, refactoring a bit so it isn't so many abstraction layers that subvert each other
@mcc @decay @amarioguy @MaddieM4 we'd keep hyperthreading, too
we just don't think management engines have any place heh
-
@mcc It would but I am genuinely not sure how possible that is when so many foundational pieces are being compromised
@griotspeak the thing about a high level is *by definition* you can transplant it onto a different low level, once that problem is solved
-
@eniko redox is currently capable of handling one channel of mono sound output and i think no support for sound input whatsoever
-
@mcc @decay @amarioguy @MaddieM4 we'd keep hyperthreading, too
we just don't think management engines have any place heh
@mcc @decay @amarioguy @MaddieM4 vector units are one of those "sigh .... yes" things, as well. frustrating complexity, but important, and at least it's self-contained.
-
@amarioguy @mcc I mean I feel about modern GPUs and their intentionally prohibitive feature span the way I do about web standards: "that's a nice miracle you destroyed the ecosystem with. Undoing the damage is probably a multi-decade job and none of the normal folk will understand why feature reductions are needed. Won't stop me from patiently pushing in the right direction, though."
@MaddieM4 @amarioguy @mcc i would also consider that this is exactly how things start. a lot of open source pillars started as someone's cool project
