Jump to content
  • Advertisement


  • Content Count

  • Joined

  • Last visited

Community Reputation

121 Neutral

About sankrant

  • Rank
  1. I might rather wait for Rust. I don't have guts to bet on Go. Actually I don't have guts for automatic garbage collection. I will wait for Rust. Till then there's nothing wrong with C++. It just takes time, Much like haskell.
  2. It's like chicken-egg situation. Start using go for non trivial parts. But as you move ahead, you will find that some things are close to impossible You drop to C, and end up using C++.
  3. Totally agree. The day there is a real alternative, I will jump ship, but there is not today, and I don't think there is any will to bring up an alternative. People are just fine using C++, if they use it. The fact is, there is no real alternative, and nothing will come up as mid level language, if not counting rust or D, which are far from mature.
  4. I urge the moderator to close this thread and give the conclusive post if possible. I have got the answer, I will use C# for games, but C++ will remain strong in the Engine and Backend development, for long time in the future. That's clear.
  5. Yeah, OK.... For some reason you think that, C# is the future mega tech. But why C#? Why not lisp? Or haskell. They have the same possibility of displacing C++. Why only C#? Why not Clojure? Or Obj C? Why only C#? Whats so special about C#. Game scripting can be done in Lua too. And engine development has no real alternative other than C/C++. There will be no alternative for a long time. That's clear.
  6. Can you enumerate the game languages of the past please? Assembler? Assembly was left by the Game Devs because we changed the way, the game's were developed. We introduced the concept of game engines to write games. C took the crown. C? We started using C++ because C++ emmerged as a superset, and we could use any C library from C++. C++ : Here the codebase increased to massive momentum. It was adopted as the industry standard for game engines. Fringe languages : Pascal? Well pascal was more productive than C and as fast. Compare it to C#. Basic? Compare it to python. Never intended for game dev. C++ will always (for a very very long time) remain the industry standard for writing game engines. (C++ is much much more stronger in case of the AAA game engines) Practically speaking, C++ is here to stay for enourmously long time, and majorly used, perticularly in the case of development of game engines, if not any other areas. Note : By game engine I mean renderer, physics, script and sound infrastructure which does the heavy lifting. I love C# when writing the actual game (not engine). Don't bother about creating game engines. Create good games with C#. Enjoy.
  7. '' As the hardware gets more powerfull... We will not require fine grained control. Down with C++! '' As the hardware gets more powerfull *OUR Needs will GROW*, and everything now which is called graphically intensive will be called crappy.... '' There will be a time when C++ geeks will be no more. '' Believe me, Earth will be destroyed some day. That's a universal fact. C++ will only die, when we start creating gamse withought a game engine. And microsoft (C++), apple (obj-C) will make sure, that there is a supply of young C/C++ programmers, who will than take charge of the game engines in the future. That's 30 years minimum. C++ is changing all the time, it will get more functional. As platforms like Google Glasses come into play, C++ compilers will be the first to get hands on. Libraries like openGL/DirectX are writern in C/C++. Do you know why? Because most languages have a C API. What about C#? If you use C#, you get locked in to the CLR. Suppose, hypothetically I write my Engine in low-level C#. My team wants to use LUA for scripting. They cannot. This will always be like that till John Carmack is alive. 50 years more maybe? Till there are console games, till we create game engines to program a game C++ will remain the Industry standard, for game engines only. Create games with C#. Use an existing game engine if you somehow hate C++.
  8. sadly I don't think it'll go that way. C++ is a very closed relative of C, the 2 can mix in the same codebase and the boundaries between the 2 become quite blurred. C++ allowed C "engine" developers to slowly get use to it without throwing away what they had and was working.. they could experiment with a little of C++ flavor here and there without compromising the structure and without feeling unsafe about it,because they knew they could just switch back to C if and when cornered. The problem with C# is that you can't "inline" C code into it. The boundary between the "native" side and the "managed" side is VERY defined.. devs from one side can't "play" moving stuff here or there.. everything is much more "frozen"... plus you have the marshaling cost to consider every time you want to move something around. To make C# (or any other language) a viable option to replace C/C++ in the game engine realm you need to create a compiler that can seamlessly include .c, .cpp or .cs files IN THE SAME PROJECT. I have more hopes for a C++ evolving into something more C#-ish (add modules and optional GC and you're there) than the entire world to adopt C# for everything. [/quote] C++ getting more C#-ish, is IMHO far from being a reality. Adding optional GC, will make it more like Rust Programming Language. C++ is now stealing ideas from functional programming languages. The world requires and always will require, one and only one mega multi-paradgrim language. I don't see C++ going away anytime soon, from the realm of game engines, and C++ going away is unimaginable in case of AAA game engines. I say, don't bother much. Make beautiful games with C#.
  9. Nobody will bother to make 'a C++ out of C#'. C# is primarily meant for the enterprise, and will be developed in that capacity. C++ is meant for creating underlying high performance infrastructure and low level code. It will be developed in that capacity. So for the future, I will be choosing C++ to make the heavy lifting infrastructure/base of my software (game engine), and C# or my favurate language to make the real part (the game). As an indie, you might be loving to code in C# (as I do), but indie developers do not create game engines for that matter!! (be happy)
  10. Game Engine in C#? Humans are greedy creatures. Every inch of performance counts, and technically C++ will always outperform C#. Its one time investment! System programming != Low level programming. The day someone writes a C++ compiler, as optimised as the present ones, 'in C#'; that day I will say 'welcome new C++'. Why would anyone want to create unmanaged C#? It will give the world another C++. Believe me, we won't switch from C++ in case of Game Engines any time soon. Focus on creating games and use C# if you like. PS : One day, the earth will end, and we will live on mars. But we will still remain human beings.
  11. C++ isn't going anywhere till we use/create game engines. Do you want to know, why we switched from assembly? Productivity was only one of the reasons. The main reason was, that we changed the way we changed the way we created games. We introduced the concept of *game engines*. We started using C/C++, and we are going to use it for game engines until we see a radical change in the way we create games (maybe games withought game engines). Till then live happy. (very very long time). Looking at a larger picture, only a *systems programming languages* like Rust or D can replace C++, if ever. Till then (what? Eternity?) use C++ to write game engines, and use C# or your favurate language to write a cool game. I am doing that, and I do not/will not regret it
  12. I agree to this point, but it's highly unlikely. Also, it will give you another C++, which is not required. C# is looked upon as an enterprise solution by the majority. No Chance. The ring has only one master, and that's C++. If the ring gets to C#, it will lead to the rise of *yet another dark lord* Let C++ and C# remain the best tools in their own domain. (game-engine and game respectively) Edit : Creating Game Engines require low level programming, thus C++ is the haven and heaven there.
  13. And unity's been proving that pretty well. [/quote] Yeah, That's how it is done. And I don't see this changing any time soon... The game engines will have to get more fine tuned (thus C++), and the game itself will need to get better productively engineered (thus C# or more productive things). People will use the right tool for the job, and will have fun. PS: Game Engine != Game. Both are engineered differently and require different kind of skills. (C++ and C# respectively in this case)
  14. Game engines are not created everyday. This is a long time investment, and thus requires really good fine tuning. C++ isn't going anywhere from this niche. Creating a Game is a different matter, and C# can be efficiently used in that domain...
  15. What? Maybe for you this is the case, but others have quite happily created their engine either mixing C++ in their code or created purely in some other language WITHOUT issues. [/quote] Other than C++? I like Haskell. Working on mastering it
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!