Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Go bug the game devs about it.
I took the time to dig through it... it was not worth the effort really.
OP obviously just crawled the web for "modern programmers practices" and some random buzzwords to try to make some sort of statement.
On this way he produced so many misconceptions such as languages and associated "good practices" having the upper hand in one department so they must have it in every department and so on and so forth. The thing that hurt me the most was literally the first paragraph saying stuff such as...
or
You don't need to be that much of a computer scientist in order to tell that OP did not educate himself properly and just picked up some random stuff probably on NewEgg and Reddit and tried to debunk the "stupidity" that the biggest companies are running on for decades now after years of further research and experimenting...
Quintessential of this wall of text is "C++ old, C++ bad".
Thats another misconception of his...
Since many Steam Games come with the "Common Redistributable" depot he assumes that Valve enforces Steam Games to be C++ based - at least partially
And that is his suggestion to be changed
The idea that you’re even saying visual c++ is 32 bit only, and that you think that somehow Vulcan a GRAPHICAL API replaces visual C++ is just so astoundingly bad I’d laugh if “gamers” didn’t actually believe this nonsense. It also glosses over the actual complexities in implementing things like DX12/Vulcan like you’re just pushing a button in Unity or something
It also ignores the complexities of game development like you could just throw in RUST into a project and then see in horror as all your 3rd party tools you need to integrate don’t support RUST.
What?
Basically nothing of what I skim read is based in this reality.
Fun Fact:
I started with Rust last week. Guess what I had to install. C++ Build Tools. :D
The 2015 and 2017 runtimes are no longer needed to be distributed; the 2019 runtimes cover those versions too based on Microsoft's updated runtime update policy.
I personally host the runtimes on my own website for a program I develop, regularly updating the installers to point to the latest version every time VS2019 has a feature update.
"Protected memory" is an OS feature, not a language one. You're perhaps thinking of "memory safety" which is a different concept.
C and C++ are still pretty much the fastest languages out there. Rust is competitive, but they're still trying to catch up to C and C++, not overtake.
Modern C++ is very featureful; e.g. it's getting first-class coroutines in C++20, which is neat.
No idea what this means. Out-of-order execution is something the CPU does internally, reordering instructions in a way that it thinks will make things faster. It's not something the compiler does!
I can't be bothered to go through the rest of the wall-o'-text line-by-line addressing the falsehoods, because it's full of them.
As mentioned above, runtimes like Vulkan will use C, likely with ASM modules in performance critical sections, as this has the lowest overhead. Driver packages will install any needed MSVC runtimes the driver DLLs depend on.
I wonder why people stopped doing that... almost as if they switched to something easier, I wonder what that was... ;)
You write a lot, but it really sounds mostly like mambo jumbo that has no ground or truth to it