8,152 karma · joined April 1, 2013
x should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary. - R^nRS
Nothing is more important than good abstractions.
Haskell is practical; it pays my bills. (https://www.obsidian.systems/ is where I work.)
With this system, how do we specify whether dependencies are needed to be compiled for the CPU, GPU, or both?
----
Technically I don't know really care whether it's multiple files or one, I just want to make sure we are not reinventing a shittier version of CFG. What they are providing looks to me like:
1. explicitly annotate some things as `cfg(GPU)` or ungated (both)
2. unlabeled means annotated `cfg(not(GPU))` by definitely
Put this way, this has nothing to do with GPUs, and just has to do with creating some crate-local CFG shorthanded. Great! Let's do that first, get a solid foundation, and then come back to whatever is remaining for CUDA Rust.
This is especially good if one scopes out a family of ISAs that are ABI compatible such that one can compile down to a semi-pre-optimized portable IR, and just do the last bit per ISA.
Nixpkgs cross support for Windows has been in there a while. Native windows support for Nix is a bit less advertised because it is pre-release/pre-MVP-on-master, but see https://github.com/nix-windows/nix-windows-demo . And expect to hear more on this in the next few weeks :).
Right now, I put models in low thinking mode during my refactors and hate waiting. I would much rather have a faster model that that maybe was slightly stupider, and I would wait far less long between prompts where it needs my valuable input.
Models that are dumb, but humble and fast, can be fine.
This is the "dumber but honest person that works harder" phenomenon, vs "lazy genius".
It's for problems like these that I have been working at cross and native Windows support in the Nix ecosystem
Next up is demonstrating the AI is more productive with better programming languages.
Where is this meme coming from? IEEE floating point is deterministic
Yeah yeah, there are plenty of ways this could go wrong, but those pitfalls are not guaranteed, whereas the ways private sector journalism can go wrong have occurred in practice. So we might as well try it.
Sometimes bad designs stick around due to pure inertia
And I say that as one of the autodidacts.
> Nine coal power plants that were set for retirement last year have had their operating lives extended, including five in response to emergency orders from the Department of Energy.
Maybe the other 4 still stay open without the bullshit DoE order keeping the 5 open, but who knows.
Everything fundamental that makes good easier for humans to maintain also makes it easier for LLMs to maintain. Full stop.