Hubert P

Before:  After:   (so pretty consistently lower)

After removing the dependency: 

By resolving here we mean that a correct edition is found in the FS, which is unavoidable. But it's not that which is causing the slowdown. The biggest penalty is...

The default log level is warning, I think. So we should reduce the log level of that particular message to trace or debug.

@jdunkerley let me know if I should spend time trying to figure out which node is causing this. It happened on the Enso 201 project.

[Warnings_3.zip](https://github.com/enso-org/enso/files/11788915/Warnings_3.zip) Happens when showing full screen visualization for: 

Slightly related to https://github.com/enso-org/enso/issues/6553

We export the type `Function` and all members of the module (including `identity`) but not the module itself: https://github.com/enso-org/enso/blob/c7692152144aa96b048138a0e91bd11793fdd05b/distribution/lib/Standard/Base/0.0.0-dev/src/Main.enso#L70 If we did export the module that would lead to ambiguity...

@jdunkerley can this be solved on the libs side or preferably on the IDE?

> Isn't there some other, more modern library that would work with _JavaBeans_ dependency? Looks like [YamlBeans](https://github.com/EsotericSoftware/yamlbeans) is the only alternative.