jay_gridbach

Thanks. I fixed it :-)

Thanks. Your advice is really helpful.

Thank you, I have just fixed it. This is so helpful, thank you from the bottom of my heart.

I respect you have learnt a lot of programming languages throughout of your career.

Thank yoy for trying! I am aware that it doesn't work correctly when opening the app in multiple tabs in same window.

I post this as a separate comment.

At this point, I am not capable with addressing the thing you pointed out - the way to block fake results in open network. From the very beginning, I don't want to make the system closed-network nor login required as I want people to join the calculation instantly. Technically, I think it is impossible to prevent reporting fake result as long as it is open network system - which means my design doesn't fit to seeking rigor.

If someone starts another project that handles calculations in better way, I would like to learn from it.

At this point, I am not capable with addressing the thing you pointed out. I didn't want to make the system closed-network nor login required. Technically, I think it is impossible to prevent reporting fake result as long as it is open network system - which means my design doesn't fit to seeking rigor.

I hope this comment answers to your question.

I will continue my project to seek meaningful purpose in some extent.

Thank you for sharing your experience. It's quite moving to know that someone in another country was going through the same thing I was. I implemented Goldbach in C++, C#, Java, and Go.

Thank you. I will do my best to make my project sustainable.

Hope everyone can enjoy the application.

Thank you. Just removed "to this day".

Exactly. At this point WASM was the best choice for me to run the calculation with uint64 as I wasn't sure how much BigInt in JavaScript is efficient.