Regarding the taxonomy of WEMI (work, expression, manifestation, and item), all of them are useful since we are talking about books at different levels. From "I have read Don Quixote", which is about the work (translations are the same), to "My Don Quixote has coffee stains", which is about the item.
The last time something similar happened (Google vs Oracle), the legal battles lasted more than a decade. It would be a very bold decision by ARM to commit to this strategy (implement "CUDA" and fight it out in courts).
That means Google got to use Java for a decade. A decade-long legal battle is great news for whoever seems to be in the wrong, as long as they can still afford lawyers. Remember, they don't claw back dividends or anything.
And while compatibility layers aren't illegal, they ordinarily have to be a cleanroom design. If AMD knew that the ZLUDA dev was decompiling CUDA drivers to reverse-engineer a translation layer, then legally they would be on very thin ice.
Correct, but the "if Amy works for Global Corp and has the authority to sign legal documents on their behalf" does a lot of work here.
At $WORK, a multi-billion company with tens of thousands of developers, we train people to never "click to accept", explaining it like "look, you wouldn't think of sitting down and signing a contract binding the whole MegaCorp; what make you think you can 'accept' something binding the company?"
I admit we're not always successful (people still rarely click), but at least we're trying.
> At $WORK, a multi-billion company with tens of thousands of developers, we train people to never "click to accept", explaining it like "look, you wouldn't think of sitting down and signing a contract binding the whole MegaCorp; what make you think you can 'accept' something binding the company?"
That sounds pretty heavy-handed to me. Their lawyers almost certainly advised the company to do that--and I might, too, if I worked for them. But whether it's actually necessary to keep the company out of trouble....well, I'm not so sure. For example, Bob the retail assistant at the local clothing store couldn't bind his employer to a new jeans supplier contract, even if he tried. This sounds like one of those things you keep in your back pocket and take it out as a defense if someone decides to litigate over it. "Look, Your Honor, we trained our employees not to do that!"
At least with a mechanical agent, you can program it not to be even capable of accepting agreements on the principal's behalf.
Another enthusiastic Zotero user here. Current library has 13,775 items and for a low yearly price one can have multi-device sync and support the project. I'm also syncing to a server I own, for complete data ownership (just in case).
My solution: auto-export to a folder then sync using your preferred method. Use the betterbibtex plugin to rename and move all necessary files. Fiddly to set up, but reliable once it's working.
This matches my experience completely: more than 40 years using vi and then vim, my fingers and my brain know to do.
I've tried to use VScode, especially since people said that it could emulate vi... it can't. Some of the basics are there, but then you forget you are in a different program, and use something that works in vim... and it fails. A couple of times with catastrophic results: I lost a file completely after typing a command.
I actually repeat the experiment every year or so, but I do not see much improvement.
Your documentation should definitely list the Unicode code points / glyphs covered, for people to get an idea which scripts are supported.
Also, the repository has a LICENSE file with the MIT license text, but the actual font file (.ttf) embeds the information that it's licensed under SIL Open Font License 1.1. One of these two pieces of information needs to be corrected.
yes, im gonna fix this... honestly i didnt realize anyone would be actually interested... i've gotten really great responses... thank you so much! companies have actually been reaching out to me! im really honored thank you!
From the abstract: NVIDIA's CUTLASS library provides a robust and expressive set of methods for describing and manipulating multi-dimensional tensor data on the GPU. These methods are conceptually grounded in the abstract notion of a CuTe layout and a rich algebra of such layouts, including operations such as composition, logical product, and logical division. In this paper, we present a categorical framework for understanding this layout algebra by focusing on a naturally occurring class of tractable layouts.
Regarding the taxonomy of WEMI (work, expression, manifestation, and item), all of them are useful since we are talking about books at different levels. From "I have read Don Quixote", which is about the work (translations are the same), to "My Don Quixote has coffee stains", which is about the item.
reply