/tech/ - Technology★

It's mostly large tech companies developing vulkan that are hiring for that specifically. Nvidia, amd, intel etc.

>>969483 (OP)

>months

Come on. At least you're not AMD, how does AMD make it through the morning without suicide?

Also imagine how MacOS developers feel after building OpenGL programs, only to see that Apple in their infinite wisdom have shoahed OpenGL in favor of their own 'Metal'. inb4 the fags deserved it

Vulkan won't be a big thing for 5-10 years. Up until then, layers above games like engines and drivers will be handling the gradual migration transparently and game programmers won't be dealing with it directly. It takes time to move tech, we finalized IPv6 in the '90s fir example.

>learning new technology is bad because legacy software exists

You did good if your goal was to write your own engines for your own games, OP.

You whiffed if your goal was to get a job.

Learn OpenGL and leave Vulkan on your resume. Once in, be "the Vulkan guy".

tfw it's the 90s

>spend months learning OpenGL and DirectX

>all jobs using Glide

Wow, I might as well just kill myself now.

>>969485

>Come on. At least you're not AMD, how does AMD make it through the morning without suicide?

By looking at their stock price and the new Intel CVEs.

OpenGL and DirectX 11 takes like half the work of DX12 and 1/3 of Vulkan

so its going to stay around for a while

SLOC wise OpenGL wins by having all in extensions and you just using what you need

Vulkan is similar but has tons of setup low level code thats great for optimizing but if you need to ship in 3 months you will mostly ignore

>969483

>spent months learning API

>everyone else uses different API

You should have learned how tech works instead of memorizing function names.

>>969507

Turns out vulkan is a lot more different than just function names.

Most computers and gaming rigs still werk so there's no real world use yet. Vulkan is unneeded developer preview at this point.

You can work on emulators, I guess.

>>969508

you're right. gamenigger tech is idiosyncratic cancer

>be me

>read a billion specs before no problem, even implemented jpeg from the spec without reading a single other word on the subject

>read opengl spec for a week

>still cannot figure out how to draw a pixel to the screen, end up drawing 2d lines specified by floating point values instead

>back to linux framebuffer API again until i can give another shit (lacks vsync which is the only reason i wanted to render through opengl in the first place. will probably just add vsync to the vesafb driver and never touch opengl again)

<inb4 hurr durr just read someone's tutorial online where they spend 100 lines setting up a context with cargo cult copy/paste code

<inb4 hurrr durrr GLUT

no fuck off, i actually want to understand the system i program in, unlike gaymers who will just blindly copy a bunch of API calls without having the slightest clue about what the API actually does

also the opengl spec was filled with redundant adjectives and phrases to make it sound like they are sophisticated, i've never seen a worse case of this until i read opengl. like i remember sentences where they would casually mention some concept they just made up on the spot as part of the description of some function.

>>969483 (OP)

Fire off an email to Khronos, they should know who has openings available.

>>969485

>Come on. At least you're not AMD, how does AMD make it

through the morning without suicide?

Probably by looking at the one year candlestick chart for $AMD.