Topic: What don't you like in cryptocurrency libraries or think is lacking from them? (Read 191 times)
March 12, 2019, 11:47:03 PM
You misunderstood my question, I am not asking about disadvantages of using these libraries. I am asking the developers what are the things that you might have noticed are missing from such libraries. Since I am currently developing one I would like to address some of these missing features as best as I can. I have some ideas myself which I shared here and am looking for more.
March 12, 2019, 09:27:29 AM
I think the reason is that such questions are often asked by first-year students at universities and there are enough answers you get from the Google search, the same points you mentioned in this topic ----> DISADVANTAGES OF THIRD PARTY LIBRARIES
About myself I see that the problem is how to teach or cross-reference or public:
-Always the answer to the problem is to download the entire library. for example, I have X problem so the solution is to download A library, For Y problem download B library but the real solution would be to build a small private library.
About myself I see that the problem is how to teach or cross-reference or public:
-Always the answer to the problem is to download the entire library. for example, I have X problem so the solution is to download A library, For Y problem download B library but the real solution would be to build a small private library.
March 11, 2019, 11:43:45 PM
Quote
Bump!
Does lack of reply mean lack of interest in what I started here or does it show there no longer is any developers on bitcointalk?! 
February 27, 2019, 03:13:44 AM
For the (nearly) past year I have been working on a library from scratch mostly to educate myself about cryptocurrencies and cryptography and at the same time increase my coding skills. I chose this kind of project because I saw some gaps in the existing libraries that I wanted to solve to best of my abilities. At this point I would like to brainstorm and know about things that other developers think are missing from existing libraries or things that you don't like about them.
Here are some examples that I have noticed:
1. Lack of independence
Many of the libraries are basically wrappers around other libraries which means you have to download multiple other projects sometimes in different languages. This sometimes introduces flaws such as the case with that Javascript malicious code injection through one of dependencies in one of the libraries.
2. Lack of documentation
This is probably the most annoying because sometimes it is hard to figure out what some functions do or how to use them.
3. Lack of originality
I will probably open up a separate topic soon about this in Development & Technical Discussion board discussing this topic in depth. For now lets just say there is a lot of code copying going on. This one has introduced bugs such as the case with BIP39/32 with those python and javascript libraries that were copying flaws over to their own code.
4. Scalability
For example if you want to create a multi-coin wallet you will have to download multiple libraries and depend on all of them each for a different coin while this can easily be done through one singular code designed in a way to work with all of them! That would eliminate new releases for both the library and the wallet. Adding a new coin would require injecting a new settings file (like an xml) to the already released wallet built on top of that library.
Here are some examples that I have noticed:
1. Lack of independence
Many of the libraries are basically wrappers around other libraries which means you have to download multiple other projects sometimes in different languages. This sometimes introduces flaws such as the case with that Javascript malicious code injection through one of dependencies in one of the libraries.
2. Lack of documentation
This is probably the most annoying because sometimes it is hard to figure out what some functions do or how to use them.
3. Lack of originality
I will probably open up a separate topic soon about this in Development & Technical Discussion board discussing this topic in depth. For now lets just say there is a lot of code copying going on. This one has introduced bugs such as the case with BIP39/32 with those python and javascript libraries that were copying flaws over to their own code.
4. Scalability
For example if you want to create a multi-coin wallet you will have to download multiple libraries and depend on all of them each for a different coin while this can easily be done through one singular code designed in a way to work with all of them! That would eliminate new releases for both the library and the wallet. Adding a new coin would require injecting a new settings file (like an xml) to the already released wallet built on top of that library.
Jump to: