Such an interesting showcase of history.
RCT was a masterpiece written in Assembly from hand. Looking at code from OpenRCT2 you can really see the thought behind it.
Now ISO Coaster really is a badly slipped together adaptation. A lot of details don’t make sense, graphics often look weird and performance is terrible - all while using tons of compute resources.
Nothing to do with politics and everything to do with crappy AI slop.
There was some list somewhere of some of those reports and it was painful to look at
Visited for the first time and it said I already visited 800+ times with a 99.5% accurancy - not very promising.
From the code this also looks like very simple client-side fingerprinting + IP information?
We’ve just deployed a fix to the core matching logic that should significantly improve accuracy and reduce false positives. Feel free to retry at https://deviceprint.io
and share your results!
Exactly my thoughts. The whole time scrolling I thought „and now a full example? Ah no, another block of extreme details I dont need“.
If it’s so easy and great - just show me what it looks like
With all this talk about the README, has no one even tried including the js file and USING the framework before commenting?
I should have it up on a CDN, that’s true. How best to include it in one of the JS CDNs? That way people can literally just include it, or click on a jsfiddle link and play around with examples.
I thought the “overview” section was supposed to cover progressively all the main use cases of how to use the framework. So you would get the idea and try it yourself.
> With all this talk about the README, has no one even tried including the js file and USING the framework before commenting?
To be frank, no. That is too much to ask.
The overview, as explained in another comment, fails to be convincing. And you're asking people to spend time and code something up when it isn't even clear if your framework has any real and convincing advantages.
It is you who should create that first working example, which someone can then tinker with and modify.
const app = new Elysia() .patch('/user/:id', (request) => { return handleUserRequest(request); })
or some other custom logic, does it automatically need to fall back to full parsing?