Vlyn

That's a ripped legging, it would be obvious if you didn't share an image for ants :)

I really don't see the issue there, you're only outputting highly specific data to a website, not dumping half the database.

Do you mean your typical CRUD structure? Like having a User object (AuthId, email, name, phone, ..), the user has a Location (Country, zip, street, house number, ..), possibly Roles or Permissions, related data and so on?

SQL handles those like a breeze and doesn't care at all about having to resolve the User object to half a dozen other tables (it's just a 1..1 relation, on 1..n, but with a foreign key on the user id it's all indexed anyway). You also don't just grab all this data, join it and throw it to the website (or rather the enduser API), you map the data to objects again (JSON in the end).

What does it matter there if you fetched the data from a NoSQL document or from a relational database?

The only thing SQL is not good at is if you have constantly changing fields. Then JSON in SQL or NoSQL makes more sense as you work with documents. For example if you offer the option to create user forms and save form entries. The rigid structure of SQL wouldn't work for a dynamic use-case like that.

I mean in my case it's for an international company where customers use this structure and the depth can basically be limitless. So trying to find the topmost parent of a child or getting all children and their children anywhere inside this structure becomes a performance bottleneck.

If you have a single level I really don't understand the problem. SQL joins aren't slow at all (as long as you don't do anything stupid, or you start joining a table with a billion entries with another table with a billion entries without filtering it down to a smaller data subset).

That's super easy to fake for a bot..

It's a ton more than mouse movement. Lots of browser fingerprinting for example and tracking.

If you only join on indexed columns and filter it down to a reasonable number of results it's easily fast enough.

For true hierarchical structures there's tricks. Like using an extra Path table, which consists of AncestorId, DescendentId and NumLevel.

If you have this structure:

A -> B -> C

Then you have:

A, A, 0

A, B, 1

A, C, 2

B, B, 0

B, C, 1

C, C, 0

That way you can easily find out all children below a node without any joins in simple queries.

You do realize we have an unlimited energy source burning down on us during the day? Energy isn't the issue here. We already overproduce during the day (though electric cars might take the load off of that in the near future).

Also you don't have to make the carbon go poof, you just have to capture it and store in in another form (that's not in the atmosphere). So yes, if you have a way to capture it and you use solar power (or any other renewable) you can reduce the carbon in the air.

Earth isn't a closed system.

For them money is just a highscore. They either win or lose, the actual amount doesn't matter at all.

The asshole could spend a thousand lifetimes just lying on the beach and sipping cocktails and he'd still be a billionaire.

My ISP doesn't support IPv6, now what?

It's really bullshit.

There's an easy mod to uncap fps, it works. There's a mod for ultra wide, it works.

It's not an engine limitation, you can already play like this with mods. But you can't play online because of changing the files..