Conversation

The Reverse Engineering community has spoken. will be ported to in the next months. I would love to have it working properly by the end of the year, but I cannot be sure. So, no ETA for now.

2
4
1
@joxean Do you plan to develop using a public repository? I'd love to contribute this (except Q4 is happening :P)
1
0
0

@buherator Yes but no. I mean, not for the initial version because I have to actually properly design it. But once I have it designed and the initial code working, I will ping you.

1
0
1

@joxean that’s an interesting distribution, do you think it reflects IDA vs Ghidra usage in general?

2
0
0

@joxean @buherator Any thoughts on Java vs. Kotlin vs. Python?

1
0
1

@Patricia @joxean I wish we had something akin to the Python Developers Survey...

0
0
0

@Patricia I don't think so, but I cannot be sure at all.

1
0
0
@joxean @tmr232 In this case this tool may be very useful for robust handling of Java types:

https://mypy-lang.org/
2
0
1

@buherator @joxean
And I should probably get https://github.com/VDOO-Connected-Trust/ghidra-pyi-generator up to date for the transition to Python3...
It's already planned, but I have no idea how much will need to change.

1
0
1

@buherator @tmr232 I'm 100% using mypy for the refactorization and port to Ghidra of Diaphora 4.0.

0
0
1

@nf3xn @buherator @tmr232

>why python and not a properly typed language

Because of compatibility issues between different reverse engineering tools. Python is the only thing that all RE tools use.

0
0
0

@joxean I have been expecting Ghidra to come to dominate because I would expect new hobbyists would start with it and later decide that IDA wasn’t necessary, or they were now accustomed to Ghidra. And I was thinking the pipeline for new folks would go from hobbyists to pros. But I did expect it to take significantly longer to get to almost 50%.

0
0
0