I'm curious why you want to target 2.1 specifically? A lot of drivers these days don't go below 3.x
And just changing the shader to #version 330 often isn't enough, that's why we need to see your setup code either way.
Preferably a minimally reproducible example project that we can build and test to be able to tell you exactly what's wrong with your code.
You don't say what your target OpenGL (or GLSL) version is, and we need to see your setup code as well. Typically gl_MultiTexCoord and ftransform isn't used since ancient times.
Lorne is a dick, and Al is too smart for him. Playing by SNL's rules and dealing with their own writers would not end well.
you might need a time machine for that
I think if Rust people want C and C++ devs to switch over, there needs to be a lot more documentation that's easy to follow on how exactly to do that. For example with Swift there's an amazing tutorial called Swift for C++ Practitioners that step-by-step goes over all the equivalent functionality and how to translate existing concepts over from one language to the other. I think Swift at least has the edge there with familiarity because the syntax physically looks closer to C-like languages, so when that's not the case, even more hand-holding is going to be necessary IMO.
biggest IF of the century
you'll still get filtered by those mods on other instances and the amount of visibility your comment has will go down. lemmy has already gotten fragmentation problems like this for similar reasons IMO
Yes, they actually CAN know those things.
Please work on your Japanese.
I would use Ada or Spark in a heartbeat if there was an easy-to-use, mature cross-platform GUI library for it.
Not everyone wants to live in the terminal. I would argue most people don't.