gonative is going away it's a system to connect gno and go code together, used for packages like fmt, but it has some problems and is not inspectable using static analysis
making tests run faster #3119 improves the state of GnoVM tests, by greatly improving their performance with some smart caching
gno will have to make floating points deterministic floating point arithmetic sometimes yields slightly different results on different hardware. this will be a problem we'll have to solve in gno.land to avoid chain forks.
why should you use an avl tree instead of a map? on the first day of gno development, you're taught "use avl trees, not maps". but how is a more complex implementation better than a native map type?