I haven't watched all of his videos, but of the ones I have it's so frustrating to watch him spend 45min+ faffing around with something that's explained clearly in the README, all the while cursing other developers for being idiots.
This is why I said to use a preprocessor macro. You get both because you can build the non prefix - backwards compatibility and with prefix versions. No problem for people who want to use it without prefix and people who want to use it build it with a prefix (or get a prebuilt with a prefix).
Yeah. Seems like a no brainer. I personally like rl_ as the prefix, but anything would do as long as you had the preprocessor trick to keep/remove them
Yeah na, your using C, you need to psuedo namespace, especially with such common names, if you don't like it either don't use C or push for namespaces in C.
Yeah, or even ray_ would be ok. Current library function names clashes when I need to use windows.h or anything which uses same functiom names and I need to use weird hacks. Since its C it would be nice to have the prefix. Its a nice way of making your lib work with others.
Why are you using windows.h? It's cross-platform library with a very low dependency count on its own. You write for one platform and it compiles on all. Including OS dependencies sounds like a problem you are making for yourself.
That is a very weird reasoning. raylib isnt the main thing I want to use in my project but part of it. I need windows.h for other functions which are not related to raylib at all.
Not everyone needs or uses raylib the same way or just to just make games.
What's wrong? You don't like it when one of your libraries defines Rectangle? Surely you were only ever using raylib as an educational tool to teach young people the basics of computer programming, and so RLRectangle or any such abbreviation would just be confusing and needless noise. Surely that's what folks are using raylib for.
Raylib definitely compromises on speed, but not compromising on speed would completely change the API, and it wouldn't look pretty (plus would hurt its exotic platform support). Its just not doing speed compromises like RPGmaker/,Game maker makes which can't run at decent frame rates at 480p in basic pixel art games. The performance compromise on desktop is like the difference between running at 500 fps vs 5000 fps with proper modern GPU driven rendering.
I remember i once tried raylib, wanted to ask something on their discord, met with very hostile responses and since then never looked back, rolling my own 3d engine
AnonymZ_@reddit
Tsoding better be speedrunning this new version in a random ass language
solve-for-x@reddit
While not reading the documentation and therefore taking 3 times as long to get anything done as he should.
tav_stuff@reddit
This is what real engineers do
solve-for-x@reddit
I haven't watched all of his videos, but of the ones I have it's so frustrating to watch him spend 45min+ faffing around with something that's explained clearly in the README, all the while cursing other developers for being idiots.
tav_stuff@reddit
It should have been made more clear then
Lucas_F_A@reddit
I recently learned there's bindings in Lean4
FancierHat@reddit
So your math proof is valid and runs doom?
dopaminefeed04@reddit
lol that's the real benchmark right there. if it runs doom it's legit
Edit: nvm figured it out
Maybe-monad@reddit
It can't be valid if it doesn't run Doom
sumwheresumtime@reddit
what does that even mean?
StarInABottle@reddit
Didn't he just do it in Standard ML? Even wrote a binding generator.
VictoryMotel@reddit
This guy chose the worst name in history, rivaled only by bevy and slint.
RaccoonElaborate@reddit
Programmers hella need to be banned from naming things, even their own projects.
larsga@reddit
Slartibartfast is very happy to hear you say that.
Frolo_NA@reddit
squeak smalltalk :pray:
frakkintoaster@reddit
Came here to find a tsoding comment, was not disappointed
arekxv@reddit
Still no prefixed functions?
LessonStudio@reddit
No, the function names are so clean. Don't dirty them this way.
arekxv@reddit
It is possible to have both at the same time and switch a version with a preprocessor directive for people who need it, that is not a problem.
aalmkainzi@reddit
Maybe the lib author doesn't want to break backwards compatibility.
Going from function name to macro could break things like
dlsym(h, "DrawRectangle")arekxv@reddit
This is why I said to use a preprocessor macro. You get both because you can build the non prefix - backwards compatibility and with prefix versions. No problem for people who want to use it without prefix and people who want to use it build it with a prefix (or get a prebuilt with a prefix).
Everyone gets happy that way. :)
aalmkainzi@reddit
Oh so you're saying there should be a build flag that prefixes the entire APIs? I dont know if that's a good idea.
That would mean you dont immediately know what symbols
libraylib.acontains, could be prefixed, could be not.shaving_grapes@reddit
Yeah. Seems like a no brainer. I personally like
rl_as the prefix, but anything would do as long as you had the preprocessor trick to keep/remove themdopaminefeed04@reddit
yeah rl_ is clean. the option would be nice
bonch@reddit
Those "clean" names conflict with existing functions.
Plazmatic@reddit
Yeah na, your using C, you need to psuedo namespace, especially with such common names, if you don't like it either don't use C or push for namespaces in C.
Devatator_@reddit
Like raylib_InitWindow instead of InitWindow?
arekxv@reddit
Yeah, or even ray_ would be ok. Current library function names clashes when I need to use windows.h or anything which uses same functiom names and I need to use weird hacks. Since its C it would be nice to have the prefix. Its a nice way of making your lib work with others.
halkun@reddit
Why are you using windows.h? It's cross-platform library with a very low dependency count on its own. You write for one platform and it compiles on all. Including OS dependencies sounds like a problem you are making for yourself.
arekxv@reddit
That is a very weird reasoning. raylib isnt the main thing I want to use in my project but part of it. I need windows.h for other functions which are not related to raylib at all.
Not everyone needs or uses raylib the same way or just to just make games.
nachohk@reddit
What's wrong? You don't like it when one of your libraries defines
Rectangle? Surely you were only ever using raylib as an educational tool to teach young people the basics of computer programming, and soRLRectangleor any such abbreviation would just be confusing and needless noise. Surely that's what folks are using raylib for.sumwheresumtime@reddit
raylib needs to be compiled with c compilers as well. if it was c++, then obvious thing would be to use namespace or something similr.
LessonStudio@reddit
I've been moving most of my code to rust for all platforms.
Raylib is cruelly holding me back.
It isn't only the cleanest C library I've ever seen, but the cleanest for pretty much any language, C++, rust, even python.
I love the author's suggestion that the cheatsheet is enough. The ultimate in self documenting code.
Plazmatic@reddit
Raylib definitely compromises on speed, but not compromising on speed would completely change the API, and it wouldn't look pretty (plus would hurt its exotic platform support). Its just not doing speed compromises like RPGmaker/,Game maker makes which can't run at decent frame rates at 480p in basic pixel art games. The performance compromise on desktop is like the difference between running at 500 fps vs 5000 fps with proper modern GPU driven rendering.
ezekelol@reddit
This whole thread confuses the shit out of me
afl_ext@reddit
I remember i once tried raylib, wanted to ask something on their discord, met with very hostile responses and since then never looked back, rolling my own 3d engine