Yea, should have been V-00000000-0000-0000-0000-000000000008
instead
Yea, should have been V-00000000-0000-0000-0000-000000000008
instead
Hmm, well the first round(s) are doable for beginners. If you want to get into programming, these kinda games are a good way to start, since you’re getting visual feedback of what your bot is actually doing.
And you can participate in loads of languages, so you can pick anything that you’re somewhat familiar with.
However, once you’re getting into higher rounds, ranks, and leagues, you’ll be playing against other peoples’ bots. So obviously if you have 0 experience it’ll be way harder to beat people with loads of experience, that understand which algorithms are suitable etc.
But I’d say go ahead and try it out. Its free. Maybe it turns out to be too difficult, maybe you’ll manage.
If “build the server and client in the same language” is a hard requirement, I believe your only choice is JavaScript…
You can probably also use Java. And I’ve used dotnet / c# for it. You can build the server in ASP-core, and a desktop client in Avalonia, or a website in Blazor
It would be easy for Google to remove the guardrails from WebAssembly in some sort of public testing version of Chromium
Google is not the authority on WASM, W3C is. Google diverging from the standards and removing any guardrails would result in “This page only works in Chrome” kinda bullshit we’ve seen before
It’s not a big red flag, but it indicates that the product is not fully open source. You can get the full community edition from Github, but for the Self-hosted Enterprise version you have to contact sales.
So all the Enterprise features are most likely closed source, and when you buy/license it, you’ll just get the compiled version. And since their Cloud hosting model has a “Per 1,000 sessions/mo” model, their Enterprise self hosted model might have that as well. So it’ll have some kinda DRM/License managing, and maybe a “call home” to check your license or usage every once in a while
base63? I’d guess you’d mean base64?
Anyways, doesn’t that fuck with performance?
I’m using this in production: RT.Comb - That still generates GUIDs, but generates them sequential over time. Gives you both the benefits of sequential ids, and also the benefits of sequential keys. I haven’t had any issues or collisions with that