[pgAdmin4] UI/data grid issues

I'm not sure images can be attached to the email, I'll try. In case if
doesn't work, you can see the image at: http://i.imgur.com/oPYHaAw.png

Please note, the first column on the picture is masked intentionally.

There are following issues depicted on the screenshot

1. Width of columns depends on column name as well as datatype
description, but not on data itself. This way, column "vyhra" is way
too wide, while column p_datum wraps contained values.
2. Width of columns is not adjustable. Despite column edge can be
"caught" by mouse and dragged, nothing changes after releasing mouse
button
3. This particular table contains way more columns - but there is no
vertical scroll or any other method I know to get to them
4. numeric datatype with unlimited numeric precision is shown as
numeric(65535, 65535). Similar thing regarding other datatypes like
integer, date, timestamp
5. To numbers, 'thousands' formatting is applied however formatting
rules (added comma before each 3 digits) doesn't match system
settings (spaces instead of comas). To be honest I don't like any
such formatting in data grids. But if any, it should be configurable
or at least should reflect system settings.
6. At the bottom of data grid we can see pagination buttons. Does it
mean that while getting 100 records, these will be split to smaller
parts and available page by page? Not sure if it's good idea. Beside
of this, switching between page 1 and 2 is very slow. Takes about 4
sek on my end (it's only 100 records, but lot of columns)
7. Whole GUI seems to be very slow. especially comparing to pgAdmin3. I
can see some animated transitions (would like to disable it, found
no option for that). But even scrolling is lagging. For example
while scrolling data grid up-down-up-down, the delay between mouse
cursor and grid movement is significant. Next major UI slow downs
are visible while expanding width of object tree or resizing
application window (especially from/to full screen).
8. auto-completion/intellisense is way too slow to be useful (and have
to be triggered manually afaik). Moreover it cannot resolve simple
scenarios like SELECT * FROM mytable WHERE .... showing all object
from database instead of objects of the table. I admin that it might
be valid in some cases but in most cases we need to see the table
columns, nothing more or less Maybe it should show most likely
useful hints first, then others? If you consider this feature to be
improved in near future, IMO SQL Assistant is a remarkable benchmark
for such features.

Hope it helps in some way

With regards