Galactic-State VS procedural-gl-js

I created my own “global state” management library: https://github.com/baron816/Galactic-State. It takes 30 seconds to learn, is very lightweight and ergonomic, and should solve performance issues with Context. Please check it out.

I'm working on a simple state library for React. It will 1) allow you to have a "global" state that doesn't require context [1], and 2) allow you let you set state imperatively [2].

The links below are the two separate parts that I want to combine together so that you can have that imperative state setting apply to all components depending on the generated hooks. That's the easy part.

`useStructure` allows you to have a class that your component uses for state (and be able to use any methods on that class). The hard part will be having async functions on those classes that update your state correctly. Not sure if it's even possible.

[1] https://github.com/baron816/Galactic-State

Nice writeup, I always like it when the shaders are highlighted like this. I got started in a similar way 7 years ago and have been making 3D terrains with THREE.js & WebGL since.

The real fun begins when you need to implement some sort of Level-of-Detail system and streaming in data to give the illusion of high detail everywhere without sacrificing performance.

Last year I released an open-source framework (https://github.com/felixpalmer/procedural-gl-js) for creating 3D terrains for web applications, you can see Uluru here: https://www.procedural.eu/map/?longitude=131.036&latitude=-2... (unfortunately the aerial imagery from our default provider isn't as high resolution as other places in Europe)

Great visualization and approach with compressing the tile data. Do you have a comparison of how much smaller the payload ends up being compared to simply sending PNG files?

I use PNGs to encode elevation data in my 3D mapping library (https://github.com/felixpalmer/procedural-gl-js/) and this does a pretty good job of compressing the data, for example in the ocean the PNG files are also very small as the image is mostly black. Different use case I now as your data is much more sparse, but I wonder how close the PNG compression would be compared to your approach.

Yeah, the React parts of this are very minimal. I'm not really sure what using it gets you, since it just manages a single div.

The _actual_ library that does all the work is here: https://github.com/felixpalmer/procedural-gl-js

- Tiny filesize means library is parsed fast. Package size is less than THREE.js thanks to code stripping

Check it out on Github: https://github.com/felixpalmer/procedural-gl-js/

The imagery comes from the Orthofoto dataset on https://www.basemap.at/ - the actual texturing is done by the Procedural GL JS library https://github.com/felixpalmer/procedural-gl-js