Choosing a library to work with WebGL
One morning, as I ran past the glorious lesson , I thought, “This is cool, but all the same, there’s not enough.” If you need to write a lot of code quickly and easily, then we need, without a doubt, for this library. But how can we choose it, if everyone who knows how to start a repository on a githaba has washed his bicycle? And about this for you, my friend, I will write a post today suddenly.
I, like many other users of WebGL technology, began my acquaintance with it from a single library, which I read about somewhere or heard from someone, and now I am hammering all the nails with the same hammer. However, if I was just starting to get acquainted with WebGL today, then everything could have been different. The fact is that last year one kind person spent 6 months writing a series of simplest examples of working with WebGL using all the libraries that I could reach - which gives you a unique opportunity to compare the APIs of different libraries before starting in-depth study of one of them:
This table presents four simple examples of working with procedural geometry as part of the APIs of the respective libraries, and overhead, which your website or application will have to pay for using them. In addition, the author performed the same examples using library primitives, where it was possible:
')
Of course, procedural geometry is not all that you need in your work, but from this series of examples you can also learn the general principles of working with this or that API, and create your own informed opinion before you start doing anything.
Update 9 / III : I thought I would continue to work on the article, but I will not check out the reaction . Learn to chew before swallowing, dear readers.
I, like many other users of WebGL technology, began my acquaintance with it from a single library, which I read about somewhere or heard from someone, and now I am hammering all the nails with the same hammer. However, if I was just starting to get acquainted with WebGL today, then everything could have been different. The fact is that last year one kind person spent 6 months writing a series of simplest examples of working with WebGL using all the libraries that I could reach - which gives you a unique opportunity to compare the APIs of different libraries before starting in-depth study of one of them:
| Library | Version | The size |  |  |  |  |
|---|---|---|---|---|---|---|
| Naked webgl | 1.0 | 0 | Tyts | Tyts | Tyts | Tyts |
| Naked webgl | 2.0 | 0 | Tyts | Tyts | Tyts | Tyts |
| Webgl helper | - | 15KB | Tyts | Tyts | Tyts | Tyts |
| TWGL.js | v0.0.20 | 19KB | Tyts | Tyts | Tyts | Tyts |
| glCubic.js | v0.01 | 22KB | Tyts | Tyts | Tyts | Tyts |
| webgl-utils.js | - | 50KB | Tyts | Tyts | Tyts | Tyts |
| stackgl | v1.4.0 | 67KB | Tyts | Tyts | Tyts | Tyts |
| lightgl.js | - | 72KB | Tyts | Tyts | Tyts | Tyts |
| GLOW.js | r1.1 | 77KB | Tyts | Tyts | Tyts | Tyts |
| TDL | v0.0.8 | 91KB | Tyts | Tyts | Tyts | Tyts |
| GLBoost | - | 132KB | Tyts | Tyts | Tyts | Tyts |
| Philogl | v1.4.3 | 136KB | Tyts | Tyts | Tyts | Tyts |
| Webglu | - | 178KB | Tyts | Tyts | Tyts | - |
| xeoEngine | v0.1.0 | 224KB | Tyts | Tyts | Tyts | Tyts |
| Scenejs | v4.2.1 | 242KB | Tyts | Tyts | Tyts | Tyts |
| CubicVR.js | v0.2.1 | 347KB | Tyts | Tyts | Tyts | Tyts |
| three.js | r71 | 419KB | Tyts | Tyts | Tyts | Tyts |
| SpiderGL | v0.2.0 | 498KB | Tyts | Tyts | Tyts | Tyts |
| Babylon.js | v2.1 | 814KB | Tyts | Tyts | Tyts | Tyts |
This table presents four simple examples of working with procedural geometry as part of the APIs of the respective libraries, and overhead, which your website or application will have to pay for using them. In addition, the author performed the same examples using library primitives, where it was possible:
')
| Library | Version | The size | | | | |
|---|---|---|---|---|---|---|
| lightgl.js | - | 72KB | Tyts | Tyts | Tyts | Tyts |
| Processing.js | 1.4.13 | 223KB | Tyts | Tyts | Tyts | Tyts |
| p5.js | v0.4.13 | 236KB | Tyts | Tyts | Tyts | Tyts |
| three.js | r71 | 419KB | Tyts | Tyts | Tyts | Tyts |
| Babylon.js | v2.1 | 814KB | Tyts | Tyts | Tyts | Tyts |
| AwayJS | v0.4.31 | 1,008KB | Tyts | Tyts | Tyts | Tyts |
Of course, procedural geometry is not all that you need in your work, but from this series of examples you can also learn the general principles of working with this or that API, and create your own informed opinion before you start doing anything.
Update 9 / III : I thought I would continue to work on the article, but I will not check out the reaction . Learn to chew before swallowing, dear readers.
Source: https://habr.com/ru/post/278731/
All Articles