nice thanks for the info.... but harm has been done already: now the win7 = a little mess , ahwell the pc = to old so if 10 needs to be used as new windows it will need a brand new pc :D

mono is open source .net, basically. .net was a project by microsoft to replace the win32 API with something else, but also inject it as an STL into programming languages, which would then force anyone who only knows that programming language to be stuck on windows. I remember when C# became a thing, i was warning people about how it's an overall bad idea, since it would lock them to windows development (since C# is the STL), which is especially bad if they want to become console developers or do any kind of development that isn't for windows GUI interface. No one listened to me (and given how formal programming education works, most really just didn't have a choice), so i'm thankful for mono, since it branches them out a little bit. They still won't be doing arduino development or anything, but at least they have a little freedom. Most gamedevs don't even program anymore: why do so if the engine is provided for you. I can respect this, even if i don't agree with it. When i was thinking about making 2d games recently, i realized that it's really just a matter of physics, but basically all 2d game engines are like 90% similar, whether it be shmups, RPG, or whatever. After spitting out sounds, throwing graphics onto the screen, and getting user input, all you do is implement the basic physics or whatever and the rest like menus, the graphics themselves, gameplay, etc are not part of the engine. While i think it's bad to get yourself stuck to an engine like that (portability issues and maintainability issues in the long run), i do understand how it can save time, effort, and money in development. However, just like programmers rely on the compiler to optimize their algorithms (which doesn't happen), these people rely on the game engines to optimize their game, which doesn't happen.

It's because of things like this, that i believe the person who uses a program to avoid learning layer X so they can do layer Y, should learn layer X to appreciate and understand layer Y. So electricians should learn basic chemistry, assembly programmers should learn electronics, programmers should learn assembly, unity devs should learn programming, game players should learn either unity or programming, etc. Allows everyone to know what they can reasonably expect everyone's else stuff to do, not just so that their end product isn't a mess, but so they also treat their tool providers with respect when the tools don't meet the unreasonable expectations, and they also gain the benefit of knowing out to swim if their boat ends up with a hole in it and their life vest can't support their weight. If your CPU is running too hot to run at 100% most of the time, you need to underclock it. 6 seconds of overheating 19 times over isn't as bad as a straight 60 seconds of overheating, but damage is damage. I forget what the actual recommendations are, but i remember that I had a computer that would shut itself off at that temperature, and considered "49" to be "critical." You have to understand that your CPU will shoot up when you're not looking, so if you're worried about the longevity of your computer, you need to keep those values at safe levels at sustained "max CPU." Beware those blasted auto-overclocking CPUs like mine: "1.0ghz CPU, but it has turbo boost to clock itself at 1.3ghz." You need to be realistic: you aren't going to manage that CPU control at all times, and trying to avoid something that's eating too many cycles at that time because it makes your CPU hot is just going to turn into a nightmare. So you want to lock the clock at bios or something ('cause, trust me, if a programmer can find a way to change it, they will, so they can offload the cost of optimization onto you, since that's how programmers these days are taught), so that you don't have to worry about it. Remember, the only person who has the incentive to worry about your computer is YOU, as everyone else has EULA and disclaimers galore to protect them from blame, and hardware manufacturers themselves gain from you having to buy new hardware, since that's more business for them.

Where is that quote from? I think I heard it recently on one of GamersNexus' Q&A videos.

Who's GamersNexus, and why should I care?

As for where it's from, simple: open up the directories of any random game you have that's been made in the past 10 years. It's usually either full of unity files or gamemaker studio files. I'm sure someone out there is doing statistics, too, but i can't be bothered to actually look. It's the thing: if you want to gamedev, don't bother learning programming. I don't agree with that way of doing things, but it is the attitude and way things are done, today.

See, this is one of those dumb things about EXEs, they tend to inflexibly build against a specific build library instead of flexibly being compatible among several. Many old windows game will balk if you don't have VBRUN300, for example.

Thanks for the info.... its helpfull, i dont understand all of it but i have a better idea now how things work, thanks.

As for the longevity of the old dino pc: its a 2009 ( regarding its main hardware) only the GTX 750 ti 2gb ram is newer its also an older GPU but only in build date meaning the physical state in years is younger maybe 2 years now while the main parts are 7 or 8 years old ( physically) so in that sense it kinda survived too long already, normally brfotr Euro introduction the pc was repalced every 4-5 years .... but euro made everything more expensive and life is expensive because of the Euro.