In https://news.ycombinator.com/item?id=45831614 jack1243star pointed out the possibility that English might not be Kiki's first language and they perhaps even have used ChatGPT to make the comment sound more polite.
> I doubt Apple could demonstrably prove damages before the civil statute of limitations expires.
Statute of Limitations is about how long you have to file the case, by no means is it a deadline by which you must fully prove damages and have no opportunity to continue your case after it passes.
Apparently from a F@H blog post [1] they say it's still useful to know the dynamics of how it folded, in addition to the final folded shape. And that having ML-folded proteins is a rich target for simulation to validate and to understand how the protein works
With or without the advent LLMs, it's an uphill battle to build a moat around a small (but nice!) wrapper around the output of a command-line tool shipped with MacOS.
> what is the moat?
Increasingly, and sadly, it's online services with a monthly subscription and no data portability. Get users in with a generous free tier and pull up the drawbridge so they can't get out easily.
I appreciate you having a go and it does look very attractive. It's not a problem I have but $5 is a reasonable request for something that gets the info into an understandable format for somebody.
I do think that small, single-purpose apps are probably the easiest lunch to eat. Narrowly scoped greenfield projects are where the LLMs seem to excel right now so that game seems like a race to the bottom.
As far as the cloning goes: your only recourse is probably the DMCA angle for the exact duplicate text. It's a shame they're so lazy as to straight copy it, but I suspect the response (if any) will be them lightly laundering it through ChatGPT so it's no longer the same.
Good luck! And I hope you find more useful ideas people might pay for
If you select a chunk of text in the page and right click there should be a context-menu option to translate the text. It's a popup with a textarea and not in-situ, but it's the same local model as far as I can tell
> By contrast, ex situ methods involve the removal or displacement of materials, specimens, or processes for study, preservation, or modification in a controlled setting, often at the cost of contextual integrity.
Might as well use the correct words if you want to talk above people's heads.
First: No need to be rude, "in situ" is a very commonly used phrase among English speakers, as should be evident from the Wikipedia article [1] you yourself cited
Second: The normal Firefox translate feature replaces the text in the page with the translated text - retaining its styling, position, context w/ images, etc. The right click menu, does not. I described the right click menu as "not in situ" which is correct.
The WASM VM doesn't have any (direct) access to the DOM, so there's no code you can write in it that would affect the DOM.
There's a way to make JS functions callable by WASM, and that's how people build a bridge from WASM to the DOM, but it involves extra overhead versus some theoretical direct access.
That's like saying WASM doesn't have a direct way to allocate memory or print to the console. Of course it doesn't, it doesn't have access to anything, that's the whole point.
I think a good analogy would be between user-space and kernel-space code.
It's just weird that by this logic, JavaScript - the more high-level, less typesafe and less performant language - would be the kernel, while performance-optimized WASM code would be the userspace program.
Thanks for the clarification. So if I understand correctly - when using WASM you interface to web things through JS forcing the user to always need JS in the stack when e.g. they may want to just use Rust or Go. My first thought would be modules that are akin to a syscall interface to a DOM "device" exposed by the VM.
