"I wish there were more good role models of this behavior. Or maybe there are, and I’m too much of a grouchy complainer to see them. Who comes to mind for you?" Immediately thought of, and could not stop thinking of the…
Thanks for posting this view: I had read the "Land Value Tax"-side of the argument before (and somewhat agree with it), but I hadn't seen someone post good reasons _not_ to support LVT. I think your reply - and your…
I was hoping to find some sort of "how this feature will be exposed to users" section in the conclusion, but maybe that discussion is out of scope. Does this kind of feature then bubble up into CoreML as API calls and…
> However, the Hexagon DSPs are notoriously hard to program. I disagree the Hexagon is "hard" to program - the HVX intrinsics are fairly straightforward if you've used neon/avx/etc. The problem is that you don't get…
"I wish there were more good role models of this behavior. Or maybe there are, and I’m too much of a grouchy complainer to see them. Who comes to mind for you?" Immediately thought of, and could not stop thinking of the…
Thanks for posting this view: I had read the "Land Value Tax"-side of the argument before (and somewhat agree with it), but I hadn't seen someone post good reasons _not_ to support LVT. I think your reply - and your…
I was hoping to find some sort of "how this feature will be exposed to users" section in the conclusion, but maybe that discussion is out of scope. Does this kind of feature then bubble up into CoreML as API calls and…
> However, the Hexagon DSPs are notoriously hard to program. I disagree the Hexagon is "hard" to program - the HVX intrinsics are fairly straightforward if you've used neon/avx/etc. The problem is that you don't get…