OvermindDL1

> Following up on my question in Slack - are we going for null interfaces or do we promote the use of Optional? Optional's *do* have overhead in benchmarks on...

> /me holds up the Scala flag 🎏 Hehe, I too am a proponent of Scala, however, much to my dismay, Scala's stdlib is *HUGE* in comparison, and Kotlin has,...

For note, doesn't `Optional` incur a runtime speed overhead that `null` (and consequently Kotlin's `?`) does not have? If Kotlin is ever expected to be merged in then having the...

Even ignoring it though, `Optional` does still have a runtime overhead that null does not have.

I personally really like Scala, it does its typing system Right, but it is not really 'first-class' in that it is not native on anything yet, has to be separate....

Null is more efficient and ties with Kotlin's safety better, efficiency is good in an engine core, so that would be my vote.

What I've done in a past engine is have 65536^3 number of chunks (via a short, each chunk holding 65536^3 blocks, though each renderable chunk is much smaller, it started...

Same as all the above as well, even `--classic` doesn't help. I can manually assigned an AppArmor profile but that's supposed to be done by snap based on information given...

@icefoxen Eh not really, take most games, they just want the delta without the position. Should they pay the calculation cost every time? (I'd probably honestly say yes but I...

Even the delta on click, take an FPS, it wants the location to 'finish' moving before applying the click (shot) itself. But yeah, devil's advocate, I'm for including the calculated...