If you just want to make a game, use a game engine like Unity, Godot or Unreal.

If you want to do graphics, like making engines, simulations, renderers then you should learn a low-level language and a graphics API. For the language I recommend C++, you can also use C or Rust but C might be a bit too difficult and you don't want to fight the language since graphics APIs are already hard. Rust might also be a good choice but I personally find the compile times very slow and the syntax to be ugly.

As for the API, go with OpenGL, it's cross-platform, old (which is good and bad at the same time) and is the easiest of them all.

learnopengl.com is by far the best tutorial on opengl, so I suggest following that.

After using opengl for a while you can branch out and use something like Vulkan or a graphics library that implements all of them, or even keep using opengl if its fine for you.

It's definetly not easy but it's one of the most fascinating parts of CS imo

The compiler pipeline goes: lexer - parser - semantic analyzer - LLVM IR - native binary.

I also wrote a standard library in C that Techlang functions can bind to using an extern keyword.

Next up is a GPU compute companion language that can call into Techlang code natively since both target LLVM IR. Haven't seen anyone else do this.

Blog post about how I built it: https://gummyniki.github.io/portfolio/blog/posts/compiler.ht...

Comments URL: https://news.ycombinator.com/item?id=48687692

Points: 1

# Comments: 1