@ahmetb@karpathy As can't a different input value guarantee a different hash result, even though the output space is far smaller. I.e, while you're technically correct, having random.seed(n) and random.seed(-n) generate the same output sequence is bad taste IMO. Just include the sign somehow!
@levelsio@GotItFromEbay If you have the thermal paste that goes between the CPU and the cooler, this is really easy to fix. If going to the store anyway, might as well let /them/ do it.
@dhh AI may be great for "local solutions", but any large large code base is (currently) going to crumble under bugs, because the developer who used AI to write the code now can't find/fix them because *they don't actually know how the code works*.
@htmx_org React is suboptimal in the sense that it computes a virtual DOM every time, so e.g a spreadsheet is bound to be slow. This recalculation can be circumvented manually (this is how people optimize it), but why have this at all?
@snoyberg (I suspect all of these you know:) GADTs to avoid boolean blindness, laziness for tying knots, space as the operator to apply a function to an argument, rank-N types to restrict a value leaking at the type level, effects reflected at the type level
@VoxelPrismatic@htmx_org I'd still use websockets (when applicable!), it's not more complicated than polling, neither in code complexity nor in how it executes.
Never sure, whether @htmx_org tweets are serious, or just to stir the pot :p