Sebastian Cohnen

For reference https://github.com/capistrano/capistrano/issues/895

I'd too rather prefer to have duplicate output. No output on errors is a big problem IMO.

Works fine with 4.0.3 (`YAML::VERSION`) on Ruby 3.1.2): ``` "0x_bae".to_yaml => "--- '0x_bae'\n" ```

That commit was the fix for https://github.com/ruby/psych/issues/443. Can you show, what the result of `#attributes` is that get's `#to_yaml` called on? I'm assuming something like this (which is the correct...

I can't read the original suggestion (was edited). I think it is not too bad to use `Kernel.warn` with a proper category set. This can be managed by the [warning](https://github.com/jeremyevans/ruby-warning)...

Okay if people without any experience "just" use it (meaning just installing whatever version of `rubyzip` is latest), then I do see your point. 🤔 What about printing the warning...

@tamasf97 out of curiosity, which v8 go binding package did you use? It's quite hard to find bindings that are not outdated/abandoned…

That's too bad :( Efficient scripting support for a "static" language like Go is really nice and useful. Although I'm quite new to the ecosystem, my observation is quite similar...

@svyatov did you found a workaround, or did you just downgrade?

Forgot to mention: local lucene enables geographical searches