react-in-out-textarea VS procedural-gl-js

Multiple projects right now:

- https://getworkrecognized.com — A platform to keep a work journal/brag document/work diary and create self-reviews or promotion writeups based on your notes // Currently trying to find motivation to make onboarding nicer incl. free trial instead of paid to get more users and initial feedback; I guess partly because of that tool i got promoted to senior level recently soo wohooo

- https://caseconverter.pro/app — A simple case converter on the web, guesses the type you want to convert into with a neural net (i know i could have used just statistical approaches lol) // Open sourced some components: https://github.com/igeligel/react-in-out-textarea and the text conversion soon™ - will launch on Product Hunt soon

- https://linkedium.com — A LinkedIn post scheduling app, planning to make it a bigger growth tool with insights on what kind of content performs well. Kind of like some analytics + social media scheduler for personal profiles but also company pages

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