Quote from: ndalliard on Today at 06:21:22 AM

Quote from: n0nce on August 31, 2021, 10:08:09 PM

Hey LN friends, I'm a c-lightning user for around half a year now, and I'm seriously debating about switching to lnd instead. What do you guys think is the cleaner solution? And what is the more commonly used implementation here?
I just hate hacked-together solutions and dirty code, since those are precursors of failed projects in 5-10 years time max.

welcome n0nce to the c-lightning users, i am one too. if you mean here in the forum i am not sure, we maybe could make a poll for that at one point, but in general lnd seems to be used a lot more and has also the bigger community it seems

Quote from: n0nce on August 31, 2021, 10:08:09 PM

I personally much prefer C over Go, and I hate Docker. Additionally, I noticed c-lightning was structured in a more minimalistic way for core functinality, with plugins for additional functionalities like HTTPS API etc., whereas in lnd it's all built-in - this to me at first sounds like bloat! Which I also hate! Cheesy

So I naturally went with c-lightning.

pretty much the reasons i also went with c-lightning

also especially because it seems that everyone is using lnd i went with c-lightning, cause i think it is important to have some diversity. i also see that on developer calls, that the 3 (or 4 if you count the rust implementation) implementations help each other to find bugs and be compliant with the rfcs. i just went with the minority (and not eclair cause that is written in java/scala which sounds bloat to me)

Quote from: n0nce on August 31, 2021, 10:08:09 PM

However, after a while of using the node and interacting with it, I noticed the plugin interface isn't as clean and bloat-free as I hoped: some plugins require me to install Node JS Roll Eyes

, they're all written in tons of different languages and often totally unmaintained for years.

because the community / number of developers around c-lightning is much smaller than for lnd, some plugins are rotting away, but i like the fact, that a developer is free to choose his prefered language to write a plugin and is not forced to use go for it. i agree with you, i try to avoid nodejs and i am even hesitant using python in some cases (that might be a little bit extreme on my part)

Quote from: n0nce on August 31, 2021, 10:08:09 PM

So now, I'm thinking to deploy a new node, running lnd and trying to install it without Docker, straight from source.
Interested to hear your opinions and experiences!

rath_ switched from lnd to c-lightning - i asked him the following:

Quote from: Rath_ on July 13, 2021, 06:55:23 AM

Quote from: ndalliard on July 13, 2021, 06:47:31 AM

@Rath: did you ever write in the forum about the topic lnd vs c-lightning and why you made the switch from one to the other? might be interesting for others (it was for me) - we need that lightning network subforum. can i do anything to make that happen?

We discussed it in this topic. Check out this post first and then take a look at the 39th page. As for the subforum, there is nothing we can do beside waiting and talking about Lightning as usual.

i am happy with c-lightning atm and don't feel like switching

i stumbled the other day about this github issue for lnd. it seems that lnd doesn't run on 32 bit systems, after the size of the database gets bigger than 1 gb. and the last commenter there mentions that raspbian (used on raspberrypies) is a 32 bit system) - something to keep in mind if you run lightning on a raspberry pi