About the goal of this engine

[code_glitch]

Relfos: On the XKCD picture its as I said before, not the people creating the universal 15th standard whoa re at fault. Its those involved the previous 14 standards who refuse to accept the new standard for whatever reason.

Also, you mention a very small market - this is far from what everyone is seeing. There is an increasing demand for better engines to power web games, mobile games, desktop games and console games. And the indie scene is booming in all those markets. The demand is increasing - not the other way around. You also mention unity - this is, if I'm not mistaken, one of the target the PGDCE has in its cross-hairs. We can't have everyones engines rival it. So we'll make one that does things it cannot. The "move to unity/ue/engine_name_here" is great. But what if you want to write it in pascal? Its not like you *can't* its just inconvenient with current solutions (in the sense that there are better alternatives if you are okay to forego using pascal for some other language).

Not only that, but the PGDCE is being designed in a highly modular nature. Why? Because there's more to code than just games. Game engines, are in my experience, a fantastic starting point if you're developing a new UI to fly an aircraft where you want to display things with not just guages, but better 3D UIs. Thats one instance I have actually tested out anyways. That article is great - and it does support your stance on this. BUT - here we have many developpers with different everything. The engine we're making is not some creation of some isolated programmer built around one use case. Its quite the opposite in fact. Put it this way: I read that article and decide to make a game with an already existing engine/system. Whats my best choice? Why the PGDCE. We're making that engine that everyone can develop games with - no matter the genre/type/platform. Its 'not just another engine'.

Edit: Also relfos, might I point out that the PGDCE is (as it says on the tin) made by a community. It has people around the engine who are working together. That right there is something to not forget - there's a community around it and its ambitions. If it was not necessary, there would be no PGDCE as a result and as a result no PGDCE to argue about . The fact the PGDCE exists and we are having this debate is proof that it is in fact something people would like to see/need.

[Relfos]

Also, you mention a very small market - this is far from what everyone is seeing. There is an increasing demand for better engines to power web games, mobile games, desktop games and console games. And the indie scene is booming in all those markets.

You did not read my answer properly.
I think I already said this, but for those that still don't understand, I am a professional in the game industry, with years of experience making engines in various languages. This pascal engine I've done is just one of my side projects, as is the Minimon game.
I know perfectly the state of the industry, I have a huge number of contacts inside the indie game developers scene, I'm not limited just to the "pascal scene", actually I'm not really that active inside of it.
Please read my message, of course the indie scene is huge now. However 99% of people are using Unity, and for a good reason.
Traditional engines are obsolete now, except if you are talking AAA engines for big console games.

Not only that, but the PGDCE is being designed in a highly modular nature. Why? Because there's more to code than just games. Game engines, are in my experience, a fantastic starting point if you're developing a new UI to fly an aircraft where you want to display things with not just guages, but better 3D UIs. Thats one instance I have actually tested out anyways. That article is great - and it does support your stance on this. BUT - here we have many developpers with different everything. The engine we're making is not some creation of some isolated programmer built around one use case. Its quite the opposite in fact. Put it this way: I read that article and decide to make a game with an already existing engine/system. Whats my best choice? Why the PGDCE. We're making that engine that everyone can develop games with - no matter the genre/type/platform. Its 'not just another engine'.

Again I see unbased assumptions about quality of existing engines. My engine is not made for a specific game genre, or even specific for games, for example right now I've been developing a 3D modelling application with it for mobile phones, something very different from a game. I'm pretty sure all kind of stuff could be done with my engine without need to change anything at all in the engine core.

Edit: Also relfos, might I point out that the PGDCE is (as it says on the tin) made by a community. It has people around the engine who are working together. That right there is something to not forget - there's a community around it and its ambitions. If it was not necessary, there would be no PGDCE as a result and as a result no PGDCE to argue about . The fact the PGDCE exists and we are having this debate is proof that it is in fact something people would like to see/need.

This is what I don't understand, so you people really insist in being part of the original authors of a project?
Because you can turn any open source project into a community, it does not matter that it was started by one guy or ten...
If people were working in improving Castle or TERRA they would still be working *together*.

It seems that the focus here is that people really want to have a project made especially by the people from the PGD community?
If yes, just state it, and I would understand and stop being so negative about it.
Because right now I only see this as it as separation of talent, instead of joining forces as people seem to want, we will have 3 or 4 teams implementing the same stuff separately in different engines.