Ray

> Commenting this line solved the issue for me, but I presume is there for a reason. There should probably be a comment there explaining that reason... I don't know...

@archewashi Thanks for the further investigation and provided details! It seems a platform-dependant issue, that's usually difficult to address...

@RobLoach Actually I think it makes sense for `IsWindowReady()` and `IsAudioDeviceReady()` (@RenzoRomeo) but I still have doubts if it should be reviewed for all the other data structures. In any...

@krisvers Sorry, no plans to add prefixes to raylib functions.

@krisvers Simbol collisions can already be avoided. I can consider slightly renaming some functions added 6 months ago but not the full library. If anyone really has that need can...

> many function names being the same as in other mainstream libraries like the winapi @krisvers This is not true. Afaik, only 2 function names could potentially collide and it...

Anyway, this is a pointless discussion, this is my final message on the topic. If you have some complaint, probably better direct them to Microsoft and Winapi than raylib.

@luis605 The functions mentioned in this issue were added on latest release, a few months ago and they don't seem to be key functions that many users could use. I...

> because the API naming lacks some clarity in my opinion. Please, could you ellaborate why `IsTextureReady()` is so confusing in comparison to `IsTextureValid()`? Because, sincerely, I don't see that...

@luis605 the logging mechanism has been there for many years, when a resource loading fails it is logged. > When you use "IsReady()" to check the status of an object,...