SDL has extensions for things like network and is compatible with pretty much anything it could technically be possible to run it on.

simply invaluable. <3

hello

90% learning GLUT is cause of college

If you are fiddling with game programming, SFML and raylib just work. If you want to have the game on steam, pick SDL as valve supports it. If you used either SFML or raylib then SDL won't be as much of a chore to learn.

I still used glut, cause its easy and works. Idk why it shouldnt be used

e

Hello thank for sharing these video amd can you make update oft these video and explain a little bit detail

Thank you for your SDL information. Keep up the good work, your videos are easy to understand.

i wish i viewed this video earlier, really would've helped with decision paralysis :)

This video is complete bullshit. An absolute waste of time. It doesn't tell anything useful other than defining what complex and verbose means. What should someone who's just now getting into graphics programming learn? What if you want to make your own engine? These are the things people want to know when they click on a video like this.

Don't chose, learn both

too short..i want long version

does openGL and GLFW the same API?

Why are you starting your sentences with "So...." ? it's not 2017 Grandad

Where did your game engine video / links go?

Raylib is easy

college campuses: "I don't see no issue here"

0:05 x11 is mit licensed, not propiertary 🙃

Great, gonna learn vulkan now.

0:10 X

The downside of SFML is the idiotic division of headers and subsystems when compiling into separate libraries instead of one library and one header + toxic community even on Github.

OpenGL is shit and slow, I know lot of fanboys telling you that opengl is relevant in industry, but when you are a game dev and want make money forget it, nobody cares about linux gaming this assholes want everything for free, so go for DirectX and Vulcan.

opengl, directx, and vulkan are not apis. they are specs which is a big state machine. They are not an api.

There is a secret easiest option called raylib

I've been using SFML for a while. It's not so much that it's hard to troubleshoot, it's more like you have to develop your own tools for debugging WHILE troubleshooting. It saves you a massive amount of time in figuring out where your biggest problems are.

Saying that SFML is underrated it's an underrated statement on itself... SFML is the shoot!!💪🏼++

What's the diference?, I installed Glut because I didn't want learn WIN API, it's very hard.

Awesome video 😂

Do not learn either of these first. Learn OpenGL or DX11 first. These low level APIs remove a lot of abstractions that make it very hard for anyone new to graphics programming to accomplish much of anything.

Thank you

I really like the portability of SDL, if you look away for 10 seconds they might do a HolyC port for a random console from 2004

Awesome slander 😎!

Playing games using opengl I typically find issues to be rare, and vulkan games I try yo steer clear of due to it being a mess to run on any machine I've had. Trying to lear more about it consequently opengl is the entry point so it's good to know what kinds of differences there are.

Write more code, potentially more bugs, and much difficult.

vulkan is just more verbose? As a seasoned graphics programmer i could not disagree more. Incoherent caches, manual synchronization queue ownership, manual memory allocation, descriptor pool pool pools etc, etc... Vulkan is exponentially more complex and is so very much on purpose.

no

>winblows dropped

The nearly 1000 lines of code required to even get Vulkan to display something is enough to make most beginners not even attempt it. Whereas in OpenGL you could do the same in like a 10th the amount of code. That makes prototyping and iteration certainly leagues faster in OpenGL and makes it a lot less daunting. The setup is the most annoying part about working with Vulkan, it's tedious, boring, and not exciting even in the slightest. Altogether it just feels like a massive chore. After that though, it becomes a lot more intuitive and usable. It's really meant for you to build your own abstraction layer on top of it (DIY) whereas OpenGL already is its own abstraction layer. The only real benefit you get from using Vulkan is if you _actually_ know what you're doing with it. A beginner isn't likely to find all that lower-level access that Vulkan provides to be super helpful anyways, since they likely don't even understand what most of it does or the situations in which it can be applied. The biggest difference between the two, from a high-level conceptual point of view, is that OpenGL _assumes_ a lot of things for you, and Vulkan does not, it needs to be explicitly told everything. 99% of the time the default assumptions that OpenGL makes will be perfectly fine, and certainly for beginners. Vulkan really shines when you're trying to run high-performance 3D graphics on limited hardware (gaming consoles) where having that fine-grained low-level access to the hardware actually becomes super beneficial to the developers. It lets them squeeze out more detail and performance than they'd otherwise be able to get with OpenGL. Of course, Vulkan also provides support for all the newest graphical effects like raytracing, so if that's your goal, you'll want to learn Vulkan.

Well if there was an API as simple as SFML and capable of 3D, it would be priceless. SFML is very, VERY simple, well-sharpen for many platforms and the same code works properly on Windows and Linux (its latest stable version also has good backwards compatibility down to Windows XP, which I think is nice). You can use lots of other languages with SFML beside C++ (but that bindings are not official and some of them might be outdated). But it has one big con, it doesn't support 3D and never will and you should use low-level OpenGL calls to work with it. It's not very important for me cuz I don't use 3D, but if I want to try it, I should learn GLFW instead (because pure OpenGL is platform-specific). Maybe I could bind SFML and GLFW and use it both for 3D, but I dunno.

Man I wish more videos were as short and sweet as this

If you want to learn, I would recommend opengl. There are way more tutorials and as long as you know how to code its easier to follow. To be honest, you probably dont need the speed vulkan has if you are not working on a triple a game with a team. Opengl, while not easy, is more simple than vulkan but it will definitely be more than enough for any indie projects

You can say that C++ is better in your opinion, but objectively C is better.

Thank man

Really good video, good enough graphic and audio quality and straight to the point

I'm really new to C++ and this would be my first API I'll learn but don't know where to start

meanwhile in my College "let's learn Glut"

I think that SDL2 is the best. It has a built-in renderer, that can target OpenGL, Software rendering, Vulkan is worked on and it has sister libraries like SDL_image, SDL_net, ... It has great compatability, you can use emscripten to compile to wasm, and it has a well documented, feature-rich API. Overall, I recommend

True,i'm making a game engine with opengl

I'd say out of all the APIs, OpenGL (2.0+) is by far the least verbose, but a bit more complex than something like DirectX9. Vulkan though, as you said is more verbose than OpenGL, but is also a fair bit more complex. In OpenGL you just call a loader function and the entire API is ready to render, but in Vulkan and Direct3D APIs you need to create an instance and to a lot more set-up before being able to even clear the screen