21–30 of 45 posts
yet on real old hardware it would be 20x slower in real life. same as all native javascript junk - its fast, but non usuable on older hardware
Good thing I'm not running games on my 4gb Pentium 4 then.
I was wondering about the why of the headline, and this is a really interesting answer. Such a beautiful way to get around restrictions. I wonder how applicable it is to other projects.
Of course it beats a native interpreter. WASM overhead is about 20%, interpreter overhead is about 1000%. What's cool here is to have a GameBoy JIT runtime at all.
It's two jits in total.
https://github.com/StephenDev0/StikDebug
For an undergrad project, I suppose it's fine to conveniently forget about the existence of this solution for the sake of getting a good grade.
Earlier quoted context omitted.
[flagged]
Every company they apply to will be leveraging LLMs. Time to get over it. No need to be grumpy old man about such things. Every generation has faced such foes. The old always yields to the new. For the times they are a-changin'
Sure, companies are asking for LLM experience. But whether they know it or not they are also hiring someone who knows what they’re doing with the output.
Projects like this are still worth doing by hand. I’d dare say it’s even enjoyable.
The author's base assumption, and stated motivation for doing this project, is wrong. https://github.com/StephenDev0/StikDebug For an undergrad project, I suppose it's fine to conveniently forget about the existence of this solution for the sake of getting a good grade.
It’s right for ‘regular’ apps.
The author's base assumption, and stated motivation for doing this project, is wrong. https://github.com/StephenDev0/StikDebug For an undergrad project, I suppose it's fine to conveniently forget about the existence of this solution for the sake of getting a good grade.