asbru-cm VS mold

asbru-connection-manager - kind of like an mRemoteNG for linux. Probably only useful if you have a LOT of ssh connections to keep track of though.

You can try this: https://www.asbru-cm.net/

That said, https://github.com/asbru-cm/asbru-cm

https://www.asbru-cm.net/ I've been using that since it was known as PAC manager. Has always worked well for me. Multiple tabs, split horizontal and vertical, plus numerous other things.

https://github.com/asbru-cm/asbru-cm - if you have a lot of ssh connections, this is a nice tool to manage them in a gui. If you are familiar with the Winblows software mRemoteNG, this is somewhat of an analog to that.

I guess Remmina or Ásbrú Connection Manager is worth trying out. Ásbrú seems to be more a universal tool for all types of connections, while Remmina only focus on remote desktop. I've only used Remmina myself, and it does what it's supposed to (tested it with RDP, VNC and SPICE)

Have you guys tried Asbru? It is a fork of PAC, Perl Auto Connector, https://www.asbru-cm.net/

https://www.asbru-cm.net/ is my go-to ssh/sftp client these days.

Try asbru connection manager https://www.asbru-cm.net

I think this is unlikely to gain traction. I say that no to discourage you, just to explain.

- The community has an instinctive distrust of closed source or a compiler from an untrusted source. If you’re familiar with the Trusting Trust attack you’ll understand why.

- Dev tools in every language ecosystem are almost always free, unless they involve some kind of hosting. People aren’t used to opening their wallets. Look the experience of the guy who built the mold linker(https://github.com/rui314/mold). Far superior to the state of art, improves incremental compiles a lot, widely applicable across ecosystems (C, C++, Rust), CPU architectures and Operating Systems. You don’t even have to modify your compiler, just need to point to his linker. He’s even giving it away for free for personal use. But still, almost no one uses it. The inertia of the established options is really high.

- It’s not complex enough. Think about the complexity involved in the cranelift backend. No one can seriously recreate the efforts of bjorn3. If we could have, we would have. But the idea idea here can be recreated, especially by the experts who already built incremental compilation into rustc.

- But if your solution is truly complex, like the parallel frontend, the burden of maintaining a fork would be too high. You’d have to spend all your time rebasing.

Again I’m not trying to discourage you, just stating the difficulties of making a business in the dev tools space. You would be better off contributing this excellent work to the community and trying a different tack.

I initially thought this would be about the mold linker (https://github.com/rui314/mold)

I assume this submission is trying to highlight the specific message (2023-01-24) : https://github.com/rui314/mold/issues/190#issuecomment-14028...

Fyi... the author wrote a more expansive blog post about selling dev tools a few months later (2023-06-06) and there was a related HN thread about it: https://news.ycombinator.com/item?id=36225016

Loongson's LoongArch CPU has been supported. (03b1a1c)

I'm amazed at how quickly the author responds to requests: https://github.com/rui314/mold/issues/1057

From the report to the fix in less than two days.

I'm not sure how competitive it will be with lld, especially if we consider ThinLTO (which takes multiple minutes on 64-core machine) - it can make the advantages of mold insignificant.

What other solutions have you tried for the problem of slow linking? You haven't even said which linker and what flags you're using. I haven't actually tried it, but the author of gold has an even faster linker called mold: https://github.com/rui314/mold

> Mold did it first, though: https://github.com/rui314/mold

Before LLD?