Hey Dustin! Great introduction to raylib! Thank you very much for taking the time and the effort! :D Just working in raylib 1.7 right now with lots of improvements and additions... but keeping it simple! :)
This kind of reminds me of Blitz Basic, Monkey-X, and Cerburus-X. The above three programming languages were designed for making games super super easy to make and it was what I started with. I am glad to see this. I will be checking Raylib out! I like these kinds of toolsets. It has been what I have made some of my first games with.
I’m getting the impression that Raylib is “easy”, for people who alreary have 10+ years of C experience, compared to trying to code a game directly interfacing with OS-specific low-level stuff, and not for anyone else, because C is hard, and there seems to be no debug tools.
11 minutes of telling us how easy it is. But not a word on debugging, you know that thing that takes up 75% of a programmers time. I had to explore that by myself, all I had was your ad nauseum assurance that it would be 'easy', because everything to do with raylib coding is easy. I introduced the simplest of errors in the example code, then pressed F6 in the Notepad++ IDE that comes with raylib. The console gave about 30 lines of report about what it had successfully done e.g. "[VAO ID 3] Default buffers VAO initialized successfully (quads) ", none of these reports were of interest or importance in light of there being an error in the code. There was not a word from the console about the compile time error. The only sign that there was something wrong was the program didn't execute. This is a gaping flaw in this setup pack and vid. No one can get far with C without error reports. Until someone finds a way to get compile time error reports from it, the raylib starter pack \ intro vid is incomplete\broken.
I agree with you, by easy I mean in terms of the C programming language, I didn't explain that very well though. I should've stated that it was simple compared to other libraries like sdl2 or sfml.
Hey Dustin! Great introduction to raylib! Thank you very much for taking the time and the effort! :D Just working in raylib 1.7 right now with lots of improvements and additions... but keeping it simple! :)
This kind of reminds me of Blitz Basic, Monkey-X, and Cerburus-X. The above three programming languages were designed for making games super super easy to make and it was what I started with. I am glad to see this. I will be checking Raylib out! I like these kinds of toolsets. It has been what I have made some of my first games with.
Yeah definitely! I really like how the library is designed
Where is your game github link?
Thank you very much for this video. You explained Raylib very well.
Thank you so much, this is awesome !
Know any shader wizardry? If so would love a video on it
Yeah I am quite experienced with shaders, ill do some experiments and ill see what I can do :)
Alot of people say you shouldn't treat C like C++. So is this a C or C++.
/
It has compatibility for both
Do you have a github link for that code?
I’m getting the impression that Raylib is “easy”, for people who alreary have 10+ years of C experience, compared to trying to code a game directly interfacing with OS-specific low-level stuff, and not for anyone else, because C is hard, and there seems to be no debug tools.
11 minutes of telling us how easy it is. But not a word on debugging, you know that thing that takes up 75% of a programmers time. I had to explore that by myself, all I had was your ad nauseum assurance that it would be 'easy', because everything to do with raylib coding is easy.
I introduced the simplest of errors in the example code, then pressed F6 in the Notepad++ IDE that comes with raylib. The console gave about 30 lines of report about what it had successfully done e.g. "[VAO ID 3] Default buffers VAO initialized successfully (quads) ", none of these reports were of interest or importance in light of there being an error in the code. There was not a word from the console about the compile time error.
The only sign that there was something wrong was the program didn't execute.
This is a gaping flaw in this setup pack and vid. No one can get far with C without error reports. Until someone finds a way to get compile time error reports from it, the raylib starter pack \ intro vid is incomplete\broken.
I agree with you, by easy I mean in terms of the C programming language, I didn't explain that very well though. I should've stated that it was simple compared to other libraries like sdl2 or sfml.