Ericson2314
> But I know Malis well enough to trust his work without looking into it
> If I didn't know Malis, I would make the same assumption, because who has the time to look into all of these projects? Because I know Malis, I didn't bother to look at it; I just trusted him
First and third paragraphs are highly redundant (surrounding ideas are the same too).
It's not nice to read something that appears like the author never read it.
There is no business here that can afford any capital outlay, this is a bunch of mom-and-pop shops that rent stable slots (I think) and own medallions. No capital outlay -- nothing can really change.
The city could also spend money on the stables. And NYC NYS have spent money propping up stupid small businesses unable to take care of themselves before. But I do not endorse that outcome at all.
I suspect though that mandating better conditions would have the same effect --- the horse tourism business probably stops penciling out if they have to make the required changes. And given that, TWU would fight it just as hard --- a de jure or de facto ban has the same effect as far as they are concerned.
This is also an L for the TWU, and I suspect there will be more of those to come in the following months.
("ex normal" doesn't clearly mean "evil"/"sinful", and Latin already had it as "big".)
Who knows what they were thinking before, but this all sounds very good.
We've just locked out a large part of modernity because the shitty American auto industry is in swing states and also gender.
Same could be said about the slow rollout of Waymo.
Lots of America is just very anti technological change, and this means any technology no matter how "magical" hits a wall.
I saw a post that said roughly "I thought computing was doomed to be 'Linux, Python, and HTTP' for the rest of my life. Now we're free". That's it. Let it sink in. We're free. We can make the computer do whatever we want.
Cast off the yokes back-compat and history
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