RayDonnelly

vor 5 Jahrendiscuss

conda, although written in Python, is language (and somewhat OS) agnostic. We provide lots of C, C++, R and Rust packages as well as Python ones.

RayDonnelly

vor 7 Jahrendiscuss

Bazel is the bane of every software packager who needs to use it and who does not work for Google. GN (or whatever it's actually called) is a close second in terms of horridness and NIH-ness, then GYP (and depot_tools too, may as well chuck that in there). Guess which company foisted all this on us?

RayDonnelly

vor 7 Jahrendiscuss

And that is also awful in so many other ways.

RayDonnelly

vor 7 Jahrendiscuss

I disagree. tcl/tk is written in C and C can be compiled in very very badly indeed (from a security perspective).

RayDonnelly

vor 7 Jahrendiscuss

You can use `conda install rust_osx-64` on macOS and `conda install rust_linux-64` to use `cargo` with the Anaconda Distribution libraries and tools (including its compilers).

RayDonnelly

vor 7 Jahrendiscuss

.. because it's (relatively speaking) brand new?

RayDonnelly

vor 7 Jahrendiscuss

If you haven't seen it, also checkout Project LIEF. It is very good indeed. We use it for a lot of post-build binary verification in the conda ecosystem.

Windows, macOS and Linux are all supported.

https://lief.quarkslab.com/

RayDonnelly

vor 8 Jahrendiscuss

A lot of the credit for the Windows version should go to MSYS2. They provide all the libraries used here (including GTK).

RayDonnelly

vor 8 Jahrendiscuss

RStudio uses it.

RayDonnelly

vor 8 Jahrendiscuss

There's no such requirement at all, but it's a noble goal and one every package developer should strive for.

RayDonnelly

vor 8 Jahrendiscuss

Great I'll try it out, I always meant to but never got round to it. Does it work on macOS or Windows yet? What's the oldest Linux distro upon which it will run?

Not sure we constantly try to sell our Enterprise product. You could look at it less cynically as we sell an Enterprise product to allow us to provide the Anaconda Distribution for free.

RayDonnelly

vor 8 Jahrendiscuss

I agree that providing toolchains is very important.

The only non-system package manager that provides Python and its own toolchains - for Linux and macOS presently - which are used to compile every C, C++ and Fortran package, including Python itself is conda and the Anaconda Distribution.

Not doing this leads to static linking and that's inefficient and insecure.

Disclaimer: I work for Anaconda Inc.

RayDonnelly

vor 8 Jahrendiscuss

You are completely right. I apologize.

RayDonnelly

vor 8 Jahrendiscuss

ggreer: I have no grudge, hopefully ag will continue to be a success for its users but it'd be lovely if people could contribute to making it even more of a success. I believe there are some easy ways to achieve that (expanding the core team if you were ameanable or somewhere or shomehow ossasionally explaining why PRs are not getting looked at), and some not so easy ways (CI with good testsuites and benchmarks).

I apologise for my overly aggressive comments, I did not handle the fact I really hoped to help out on ag and got frustrated by the experience very well (at all).

Have a nice weekend.

RayDonnelly

vor 8 Jahrendiscuss

OK sure, but would you consider merging one PR that explains that people should not expect PRs to get reviewed? I'm happy to do the work if you'll review and merge it.

That way we can avoid unfortunate incidents such as this in future.

RayDonnelly

vor 8 Jahrendiscuss

In what way is updating README.md difficult? Please have as much respect for contributors and potential contributors as you seem to have for maintainers. They're all people after all and their free time is equally important.

RayDonnelly

vor 8 Jahrendiscuss

I respectfully disagree with you. I wasted perhap 10 hours of my life or more on this PR (pointlessly rebasing it a few times). 95 other PRs are outstanding. There are many ways to improve this situation. I pointed two of them out:

    1. Declare that you won't accept (or even review) them, preferably at the top of README.md *
    2. Give a second person merge status.

I have some empathy for the maintainer but I also have empathy for the prospective contributors who spent a chunk of their free time working on https://github.com/ggreer/the_silver_searcher/pulls

I've done my bit here to stop wasting people's time globally, I don't consider a maintainer's time more valuable than a contributor's time. That's elitest nonsense.

https://github.com/ggreer/the_silver_searcher/issues/1284

* The likely side-effect is a unblessed fork (or people not wasting their time, or if they do, well, they didn't read the README.md and cannot be too annoyed at anyone but themselves).

RayDonnelly

vor 8 Jahrendiscuss

You don't want to waste your own precious time but are more than happy for many other people to waste theirs?

Also you merged commits starting from 24 Dec 2011 and ending on 18th August. Presumably you saw value in those commits?

RayDonnelly

vor 8 Jahrendiscuss

You answered none of my explicit questions.

Hopefully a maintainer with a sense of community and responibility will fork the silver searcher.

RayDonnelly

vor 8 Jahrendiscuss

So it's not really an open source project in any meaningful way?

Do you consider it reasonable for people to waste their time making PRs and working trying to help you to improve the silver searcher?

Could you put something up describing this policy?

Could you recruit someone who's proven themselves to be maybe somewhere near as good as you to be a co-maintainer?

As I say I couldn't care less about my PR now since I've moved to rg, but this was an absolutely horrible experience.

Either embrace open source and do it right or please, do not bother releasing source code.