10 Small flaws noticed by new Geo Nodes

Working with color, hue, contrast, separation by hue, light temperature, ....

Input fields for addition, multiplication, logical or, and are analogs of the union operation. They can and should have 1 socket, like a geometry or instance join.

Structures. 3 float fields - maximum structure. And if shaders are not that important, then mesh generation programs are a pain.

Filling with volume points.

The ability to divide the geometry by islands, for example, as a set of instances. *The ability to work individually with all instances as geometry, making them just a mesh array.

Make the input of data about the view mode (like editing-object mode, render or preview) and the ability to see different results in different windows.

Make custom subgroups in the node creation menu. In a couple of days I have created more of them than I can see on the screen. This was rare in shaders.

Make it possible to create objects of extraneous types, such as cameras or light. This is only necessary so that you do not create them manually on other layers every time.

Associative arrays. Any container, the context of which could be passed, first enter data there by 1 key, and then receive it. It's not just the index that matters. Yes, using indexes and multidimensional grids you can do this now, but memory ...

Checking the input type, which can be a null pointer, that it is. For example a texture, or an object. Yes, you can check the number of vertices in the geometry, but .. .