• she/they/it 🏳️‍⚧️

∍⧽⧼∊ ΘΔ

grey ace, adhdtism


hobbyist game developer, professional procrastinator, and kink trash goblin


avatar by @theobii
Zorotek is @7x9000's
header by Gluepaw


second life's LSL desperately needs more data types - I shouldn't have to hamfist a boolean into an integer that takes up 4(!!) whole bytes, and bitfields actually take up more memory than you save by compacting them all down if you want the script to be even remotely maintainable. not to mention ints are still restricted to 32-bit, which poses problems for timers and such. they're already moving to 64-bit machines with the PBR update, so why not throw us a bone here

we really could use char, uint, int64, and uint64 data types, with an int alias for integers and str for strings. also 64-bit vectors and double precision floats, why not

on one hand, LSL scripts are exceedingly memory constrained (you get 64KiB to play with, maximum, per script) -- on the other, we really do need options. I only plan to use a single 64-bit integer anywhere, and I could save more than I use by simply changing two of my booleans-but-not-booleans to chars