Difference between revisions of "Why use Gideros?"
From GiderosMobile
| Line 19: | Line 19: | ||
===[[Lua_enhancements|Various Lua enhancements]]=== | ===[[Lua_enhancements|Various Lua enhancements]]=== | ||
For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code. | For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code. | ||
| + | ===Facebook Instant Games support=== | ||
===Unique async calls system=== | ===Unique async calls system=== | ||
Besides regular enterframe callbacks, we can write a program "sequentially", like we would have written for the Commodore 64 or DOS PC, ie assuming our program has complete control of the computer. | Besides regular enterframe callbacks, we can write a program "sequentially", like we would have written for the Commodore 64 or DOS PC, ie assuming our program has complete control of the computer. | ||
===Built-in Profiler=== | ===Built-in Profiler=== | ||
===Built-in Debugger=== | ===Built-in Debugger=== | ||
Revision as of 05:20, 11 January 2019
As of 2019, Gideros just out of the box has pretty much everything that can be needed for creating even top tier mobile games:
- GLSL Shaders
- Physics (LiquidFun)
- Meshes
- Particles
- Texturepacks
- Tilemaps
- Blend modes
- Stencil
- IAP/Ads
- JSON
- Skeletal animations (Spine/Dragonbones)
- Sockets & real-time multiplayer (PhotonCloud/Noobhub)
Besides that, few more advantages can be mentioned:
Instant on-device testing
True Multithreading
Various Lua enhancements
For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code.
Facebook Instant Games support
Unique async calls system
Besides regular enterframe callbacks, we can write a program "sequentially", like we would have written for the Commodore 64 or DOS PC, ie assuming our program has complete control of the computer.
