yes, i like it very much

you should be very careful messing with maps, you may not need maps

maps are not concurrent safe and iterate randomly

i built a key/value collection type, took me an afternoon, that does much of what a map does, but preserves field ordering

also, the reason why go's maps are so basic is because go doesn't force you to use any high level abstractions more complex than this map for your data types

if you need large tables, better to use a database like badger or leveldb

if you need proper ordering, you need to write code that unpacks the map into a slice before rendering it, or you can use a heap or other similar ordered complex data type, container/heap is where the priority queue heap implementation lives

main thing you are going to learn about go is that it's not easy to work with dynamic typed wire encodings like JSON this is why i've spent a lot of time on making sure my in-development relay codebase has some clean and precise implementations that work with Nostr's json types