I'm pretty confident that option A is not correct. Web3.js may change often, but that doesn't mean Truffle-Contract is a must for every developer. I'll steer clear of that one and focus on the key differences between the two.
Option B sounds like the best approach to me. Truffle-Contract can simplify working with Web3.js, especially since Web3.js is still in beta. I'll highlight how Truffle-Contract's promise-based transactions can be more convenient.
Hmm, I think option C is the correct answer here. Truffle-Contract and Web3.js are quite different - one is a framework and the other is a library. I'll focus on explaining that distinction in my response.
I'm not too familiar with the differences between Truffle-Contract and Web3.js, so I'll need to review the key features of each before deciding how to approach this question.
Dahlia
2 months agoCammy
2 months agoAlison
3 months agoKindra
3 months agoJesus
3 months agoRaylene
3 months agoLoren
3 months agoNichelle
4 months agoWinfred
4 months agoTawanna
4 months agoMelissia
4 months agoAntione
4 months agoChristiane
4 months agoHyman
5 months agoGoldie
5 months agoReita
5 months agoTasia
5 months agoHoward
6 months agoPaul
6 months agoKasandra
6 months agoJanine
6 months agoCatalina
1 month agoKanisha
1 month agoMoon
1 month agoMy
2 months agoChi
2 months ago