oivey

8 ms·

61.
by oivey 1y ago
It’s not a non-sequitur. The thesis behind the push for in person paper is predicated on the idea that it makes it prohibitively difficult to steal an election. That’s demonstrably untrue based on current and historical examples. As another
62.
by oivey 1y ago
I don’t really understand the blind trust in paper in person ballots. Historically and currently, elections are stolen all the time whether paper or not. Off the top of my head some recent ones: election irregularities in Venezuela and the
63.
by oivey 1y ago
If it’s just a signature or stamp, won’t the 7 year old ask why those can’t be faked or forged?
64.
by oivey 1y ago
Ahh yes, if only the commit message was better. That would have stopped the xz attack.
65.
by oivey 1y ago
Even with frame generation it is incredibly obvious. The latency for sure is a downside, but 100 FPS vs 240 FPS is extremely evident to the human visual system.
66.
by oivey 1y ago
So I guess there is no need to change any of the hardware, then? I think it might be more complicated than waving your hands around linear algebra.
67.
by oivey 1y ago
Famously, this fact is also why no one drives recklessly and no one has lost any limbs with power tools.
68.
by oivey 1y ago
Oof. This feature request has nothing to do with lazy imports. It’s also solved far more cleanly with inline script metadata.
69.
by oivey 1y ago
Because it’s nice to reuse code. It’s virtually never the case that a function being compatible with too many types is an issue. The issue is sometimes that it isn’t clear what types will be compatible with a function, and people make mista
70.
by oivey 1y ago
> That's your problem right there. Why are random callers sending whatever different input types to that function? Because it’s nice to reuse code. I’m not sure why anyone would think this is a design issue, especially in a language
71.
by oivey 1y ago
I feel pretty similarly on this. Python’s bolted on type system is very poor at encoding safe invariants common in the language. It’s a straight jacketed, Java-style OOP type system that’s a poor fit for many common Python patterns. I would
72.
by oivey 1y ago
I took a closer look at some of that and it’s pretty cool. Definitely neat to have some good higher level abstractions than the old C-style CUDA syntax that Numba was built on.
73.
by oivey 1y ago
Slight correction: CUDA Python JIT has existed for a very long time. Warp is a late comer.
74.
by oivey 1y ago
It can be hard enough to fix things when some surprise happens. Unwinding complicated “future proof” things on top of that is even worse. The simpler something is, the less you hopefully have to throw away when you inevitably have to.
75.
by oivey 1y ago
He seems to have mistaken his personal opinions on which languages and language features are good for some objective truth. Ironically, that’s part of why we can’t have nice things. People who aren’t open to other viewpoints and refuse to c
76.
by oivey 1y ago
Sure but neither is Mojo.
77.
by oivey 1y ago
Where did you read this?
78.
by oivey 1y ago
That seems like a wildly questionable conclusion to draw. 60 years prior to that act, there was a huge influx of immigrants who would have been considered non-white at the time: Italians, the Irish, Germans, Eastern Europeans, etc. To the p
79.
by oivey 1y ago
It’s a pretty standard run down of CUDA. Nothing to do with ML other than using relu in an example and mentioning torch.
80.
by oivey 1y ago
2 miles is an awfully long way, and 36% of Americans are even further away. That’s 4 miles round trip. Presumably many of those charging stations aren’t that big and disallow you leaving your car overnight. The rest of the numbers are simil
81.
by oivey 1y ago
The courts interpret the law, so in fact he does have to convince them that his interpretation is true.
82.
by oivey 1y ago
That sort of directory-based splitting almost never works in my experience. The code between those directories is almost always tightly coupled. Splitting arbitrarily like this gives the illusion of a non-tightly coupled code base with all
83.
by oivey 1y ago
Yeah. My experience is that the teams managing shared repos tend to shift responsibility for integrating their changes onto their users. They then also more often make breaking changes because they’re insulated from the costs of those chang
84.
by oivey 1y ago
It’s difficult to trace through the repo, but it looks like the compression ratios are computed by seeing how many pixel diffs were able to dropped. That’s interesting, but the more interesting comparison would be to the average byte size o
85.
by oivey 1y ago
That doesn’t address the issue at all. The issue is that discarding small changes in any color space is fundamentally lossy, so the algorithm isn’t lossless.
86.
by oivey 1y ago
So, has any of that slowed down J.K. Rowling? These sorts of boycotts seem to be more of an attempt at controlling something in an uncontrollable situation rather than an actually effective means of change. “Voting with your wallet” is almo
87.
by oivey 1y ago
That quote does not say anything about citizens inflicting pain on others. That’s such a strange way to read it. It’s saying to vote shitty leaders out. I’m not sure what you think any other possible alternative there could be.
88.
by oivey 1y ago
I mean, why not just write Rust at that point? Required static typing is fundamentally at odds with the design intent of the language.
89.
by oivey 1y ago
At least in Japan, they all work from your phone already.
90.
by oivey 1y ago
Suppose you write a program that computes the sum of two input numbers. Suppose the two inputs are 1 and “a”. If it returns “1a” or 12 or whatever, the program is incorrect. Its correctness does not hinge on type safety. A untyped program c

More ›