279 karma · joined February 23, 2024
Disclaimer: I'm a zig fanboy and do all my hobby stuff in it
It's fine to develop "in the open" but this is a pitch for several million dollars, and handing that out without any credentials or track record is just not happening.
At least provide rough estimates for what is needed to get this done. What architecture? What training data? Where does the training happen? Who manages and administrates the cluster? Volunteers who try this the first time or paid experts? What solutions to failure recovery, to storage, to tracking and monitoring? Who has the last word on fundamental decisions? How will the legal component be handled? Do they already have a good law firm, how much would that cost? Will the first training be successful right away or how many iterations will be required? Can you even get access to the required GPUs at a reasonable price point? Train on older architecture? How much effort is required and planned to save cost by making training more efficient, ........
I also disagree that it's small but mighty, you popen curl that does the core task. I am not sure, but a bash script might come out even smaller (in particular if you compress it and make it self expanding)
He "ships" a website with a gmail address and nothing substantial. I could do the same, likely better, in 20 minutes. How could I even tell this from a scam, there is nothing of substance. And the great idea is just obvious and all the painful details to make it work are completely ignored
Apart from that, I agree with the other comments that the website looks unprofessional and llama is a bad name to use for this.
If I would want to give this a shot, I would first get engineers committed with a plan to start as soon as there's funding, set up a non-profit to handle the operation, and make sure that potential investors get the impression I knew what I was doing by providing a full plan and timeline, including addressing the legal challenges (among those, make it clear that the resulting model will be commercially usable and not sued to death. Are you planning on guaranteeing indemnification or do you want to release the model as-is? Etc)
Also interesting that "ultra lightweight" here means no error reporting, barely checking, hardcoding, and magic values. At least using tty color escape codes, but checking if the terminalm supports them probably would have added too much complexity......
Plus I meant for the manufacturer to "repair" it. Maybe tamperproof gets triggered if you accidentally drop the device in an unfortunate way
Now I am curious if I can find a terminal myself, if they are actually getting phased out it might not be too difficult to find a used one...
In this case, I do not care why he had changed his name, I read the beginning of the article and it did not explain why this is something that needs discussion, and stopped reading when it just stated his birth name.
The point I wanted to make is that using generator, in particular like here, is something that I consider ugly and difficult to maintain and it will probably have to be rewritten when trying to export to TorchScript. I really do not see how “just get a hang for it” can help me reevaluate my perspective
Edit: Maybe you were hung up on my “standardised” - I have to admit I do not know how thoroughly the PEP defines generators and if really all edge cases are defined without needing to check the python source code. From past experiences, my trust in python language standards is a bit shaky, as it had been difficult to reproduce the very exact behaviour using a different language, or python features - without requiring digging through the sources.