# Considering Leaving Phaser Development

**URL:** <https://phaser.discourse.group/t/considering-leaving-phaser-development/5835>\
**Category:** Phaser 3\
**Created:** [April 8, 2020, 11:38pm UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835 "2020-04-08T23:38:35Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![BlunT76](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/blunt76/32/1454_2.png) [@BlunT76](https://phaser.discourse.group/u/BlunT76)\
**Post date:** [April 11, 2020, 9:14pm UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835/21 "2020-04-11T21:14:36Z")

</div>

You can’t compare google angular and phaser 3. I got difficulties with the doc too when started with phaser 3 one year ago, but once you know how to search and what to search it becomes more easier.  
I think Phaser is more like a lib than a framework.

---

<div class="post-metadata">

**Author:** ![rafael-lua](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/rafael-lua/32/2822_2.png) [@rafael-lua](https://phaser.discourse.group/u/rafael-lua)\
**Post date:** [April 12, 2020, 2:47pm UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835/22 "2020-04-12T14:47:44Z")

</div>

> but once you know how to search and what to search it

I agree, but the problem is to learn how to do it. I’m sure a lot of people have an easier time with the documation, even more if they are experienced programmers. But is very hard to understand how things flow and what I’m looking for in the documentation. For example: [Notes of Phaser 3](https://rexrainbow.github.io/phaser3-rex-notes/docs/site/) is MUCH more clean and helpful. It may be that I’m weak with Object Oriented logic, but it really feels that the documentation needs a basic guide for itself.

---

<div class="post-metadata">

**Author:** ![BlunT76](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/blunt76/32/1454_2.png) [@BlunT76](https://phaser.discourse.group/u/BlunT76)\
**Post date:** [April 12, 2020, 4:16pm UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835/23 "2020-04-12T16:16:25Z")

</div>

I agree, rexrainbow doc is very helpful.  
And yes, you need to knows the oop basics to master phaser 3.

---

<div class="post-metadata">

**Author:** ![snowbillr](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/snowbillr/32/332_2.png) [@snowbillr](https://phaser.discourse.group/u/snowbillr)\
**Post date:** [April 13, 2020, 2:59am UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835/24 "2020-04-13T02:59:25Z")

</div>

I always think back to this article when it comes to different types of documentation: [https://documentation.divio.com/](https://documentation.divio.com/)

Phaser has great official _reference_ docs, but lacks official _explanation_ docs. The rex docs fill that need very well.

---

<div class="post-metadata">

**Author:** ![snowbillr](https://yyz2.discourse-cdn.com/free1/user_avatar/phaser.discourse.group/snowbillr/32/332_2.png) [@snowbillr](https://phaser.discourse.group/u/snowbillr)\
**Post date:** [April 13, 2020, 12:51pm UTC](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835/25 "2020-04-13T12:51:32Z")

</div>

Actually it’s worth mentioning that the phaser examples are an exemplary piece of living documentation as well. They aren’t written explanations but they are clear and concise code examples that show how to perform a huge variety of tasks in phaser.

[https://labs.phaser.io](https://labs.phaser.io)

[Previous page](https://phaser.discourse.group/t/considering-leaving-phaser-development/5835.md?page=1)