MoonsideGames
/
encompass-cs-docs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

some more architecture quips

pull/1/head
Evan Hemsley 2019-05-21 18:23:06 -07:00
parent 5598180037
commit 7b9fd73940
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/why/architecture/mess.md
View File

@ -18,4 +18,6 @@ The key characteristic of this structure is that there almost doesn't seem to be
Shockingly, some game engines and frameworks not only fail to prevent this kind of architecture, they actually *encourage* it!
"But *I* know where everything is!" Tell that to yourself three months from now.
I don't need to say much more about this kind of architecture. It's obviously bad. Let's move on.

2
content/why/architecture/oop.md
View File

@ -4,7 +4,7 @@ date: 2019-05-21T15:54:18-07:00
weight: 20
---
*They call it OOP because it was a mistake. --Unknown*
##### *They call it OOP because it was a mistake. --Unknown*
You are probably very familiar with OOP, or object-oriented programming, as a game designer. It is the structural idea behind most games as they are written today, though this is slowly changing.