Open mre opened 4 years ago
Hey, thanks for linking here from HN ;) Just a small disclaimer: I work in the field, but this is my personal opinion and not necessarily that of my employer :) Though I'm probably biased.
IDA free
the "Binary code analysis tool." blurb is rather vague and if I didn't already know IDA, I'd need to check the website to figure out that it's something else.//edit: Ah, regarding this portion of your reply, "or wants to help build it": The part of my free time that's "allocatable to FOSS work" is currently locked to some other project(s) ^^"
Thanks for the input @archi.
special_offers
field, that could contain ["oss", "academia"]
. The question is if that information alone would be helpful. Most like people would want to know what exactly the offer is, which would require quite a bit more research and be harder to standardize.binary
section, which might be a good fit. It would greatly help us complete that section. The information right now is quite rudimentary. I suggest to add WCET to the description as it will show up in the Algolia search results for now. Once we find that more tools have that property in the description, we can go and formalize it as a field in the YAML.No worries if you don't personally find the time to contribute. Your input is quite valuable already. Maybe someone else will be inspired and come forward to add more suggestions or help with the implementation.
proprietary
, academia
(but this would ultimately be the same as proprietary: true
plus some special_offers
array/list of tags).commercial_support
tags, and define the possible tags somewhere? I think it's difficult avoiding to manually collect this from websites, or outright ask companies.sound
tag? Plus, generally, when a user clicks on a tag, not only list all tagged applications, but also an explanation of the tag.architectures
, and a per-architecture tag (riscv
, aarch64
, powerpc
,...). Though that's a deep rabbit hole (e.g. we differentiate between ppc architectures again).I was looking for a tool for unit test few days ago, and then I found this cool website, which compare between different library, maybe that will help?
That looks like a great product to me. We've heard from some people that they are interested in comparing two tools like that. It might be a lot of work, though. It's probably worth it in the long run.
A few users mentioned that we should focus on better support for comparing tools. This is new ground for us and we'd like to get some early feedback from the community to see what is really needed here. Some ideas we thought about so far:
Thoughts on the above? Anything else that comes to mind? We're thankful for any input.