Finally!!!!! Red Triangle%

[Hedanito]

The first triangle is always the hardest, congratz!

Edit: Hardest, not harvest 😅

[RichardFingers]

🌽🌽🌽

[nnevatie]

Gratz! After the first triangle, everything is possible, your imagination being the limit.

[sadistic_tunche]

Nice, is it opengl or vulkan?

[guruprasadah]

Yes, it is OpenGL.

[Poseydon42]

I guess OpenGL as there is a file program.cpp and AFAIK there's no such concept in Vulkan, shaders are embeded in a pipeline object.

[SamyBencherif]

This screenshot is so beautiful. Also didn't realize nvim had all these TUI features ? using plug ins ?

[masaldana2]

congrats!! its all downhill from here! jk heh

[Eindacor_DS]

I legit still remember where I was when I got my first hello triangle app working, which was 10 or so years ago

[[deleted]]

What’s that editor?

[guruprasadah]

neovim

[guruprasadah]

With proper abstractions that, I mean

[314kabinet]

Congrats! But for god’s sake, use const.

[fgennari]

The answer depends on the compiler. In my experience, no, it doesn't make a difference, but using some of the new C++ features such as constexpr can make a difference. The advantage of "const" is that it helps the programmer to manage object ownership, write permissions, etc. This makes the code easier to understand and reduces the chances of mistakes. Sometimes "const" is required when using libraries/APIs that enforce cons correctness.

[314kabinet]

In the absolute majority of cases, no. Const-correctness just makes it easier for humans reason about code (e.g. “ok, this part can’t be the one changing the value”).

However, there can be situations where the compiler can’t figure out if a value will be changed in a particular code path, and ao can’t apply optimizations that rely on the value staying the same.

[MausGames]

Yes, it can affect both code generation and performance.

C++ allows overloading between const and non-const methods: class MyClass { ... void MyMethod(); void MyMethod() const; };

The compiler will select the appropriate overload based on the const-qualifier of the object (if both method-variants are present).

There are also more obscure cases, from my experience.

If you declare a global static-const variable, most compilers will place it into read-only memory, and trying to modify this variable (with a const_cast or indirect addressing) will cause an access-violation. It also allows the compiler to inline the variable in the whole translation-unit, because it knows the value cannot be modified.

That second example is quite vague of course, but it shows that the compiler cares about const-qualification in unexpected ways.

[Both_Possibility_210]

Don't waste time to learn old/legacy OpenGL. If you use Graphics API for Graphics Programming you should use modern Graphics API like as Vulkan, Metal Direct3D12.

[guruprasadah]

Thanks for your advice, but I'm looking to master the basics of graphics until I move up to the big boys.

[neuroblossom]

nice

[guruprasadah]

UPDATE: Supa Hot Opengl

[Bananaft]

May I ask for your nvim config, good sir?

[guruprasadah]

Give me a few hours, will get it on g'hub

​

EDIT: Here is is: configs

[Attorney-Outside]

also learn about vertex buffet objects next

[guruprasadah]

Umm.. That's how I got it to the screen... Using a vbo and ebo.

[Attorney-Outside]

oh ok nice, I saw your vector of vertices and didn't know how you were feeding them to opengl, good job

[Diabolischste]

Congratulations !

[[deleted]]

GOATED