best java decompiler

hermione that's not an answer. i think this person knows how to use google. he/she is here to get professional advice.

as far as decompiler's are concerned jad is considered very good:L

http://www.kpdus.com/jad.html

but it seems like the obfuscators are ahead of the decompilers. anyone have a better suggestion?

regards

fred_garvina at 2007-7-16 0:51:45 >

> hermione that's not an answer. i think this person

> knows how to use google. he/she is here to get

> professional advice.

> ...

Since when does a (professional) programmer need a decompiler?

Without some more detail, I think it is justified to point the OP to a search engine.

prometheuzza at 2007-7-16 0:51:45 >

> - Where can I find A decompiler? (google link

> justified)

Because nobody would think to google the name of the

given choices to download them. Nope. Never happen.

> - Is it unprofessional to use a decompiler? (let me

> guess, pros don't use a debugger either, right?)

You don't understand the difference? Hint: if somebody wants to

let you see what they're doing, they won' t make you decompile. They'll

just give you the source. Then you get comments and reasonable

variable names and ... If I were to pull a number out of a hat, I'd

say that 95% of decompiler use is for IP theft.

es5f2000a at 2007-7-16 0:51:45 >

> > hermione that's not an answer. i think this person

> > knows how to use google. he/she is here to get

> > professional advice.

> > ...

>

> Since when does a (professional) programmer need a

> decompiler?

When one finds out that the last developer who quit in a rage was delivering the builds from his machine and not all of the source code made it into source control.

jschella at 2007-7-16 0:51:45 >

> > When one finds out that the last developer who quit

> > in a rage was delivering the builds from his machine

> > and not all of the source code made it into source

> > control.

>

> I never said a developer will never be in need of a

> decompiler. That's why I said after the one sentence

> you quoted: "Without some more detail, I think it

> is justified to point the OP to a search engine."

I was just providing an example of one that happened to me.

Another example was in a particular situation where there were two software teams in different regional areas. One was where all the bosses were (they got to call the shots.) The second one was rather certain that they had found a bug in the code of the first. The first's reaction to that possibility was that it most assuredly wasn't a bug. The first also rejected the possibility that the second would need the source code for any reason either. Decompling demonstrated that yes the first's code did have a bug in it.

jschella at 2007-7-16 0:51:45 >

> > I never said a developer will never be in need of a

> > decompiler. That's why I said after the one sentence

> > you quoted: "Without some more detail, I think it

> > is justified to point the OP to a search engine."

>

> I was just providing an example of one that happened

> to me.

I believe this would have happened to most of us. Fortunately for me, the application only had 10 odd classes.

aniseeda at 2007-7-16 0:51:45 >

> > > I never said a developer will never be in need of

> a

> > > decompiler. That's why I said after the one

> sentence

> > > you quoted: "Without some more detail, I think

> it

> > > is justified to point the OP to a search

> engine."

> >

> > I was just providing an example of one that

> happened

> > to me.

>

> I believe this would have happened to most of us.

> Fortunately for me, the application only had 10 odd

> classes.

And that's why any project that's worth anything has a source control system in place...

Bad enough to loose a day's (or a few days') work in a harddisk crash, worse to loose manmonths worth due to something like that (or worse, your network being vandalised as happened to a company I worked for once, we had to revert to a 1 month old backup tape, all later tapes had failed).

jwentinga at 2007-7-16 0:51:45 >

> >

> > When one finds out that the last developer who quit

> > in a rage was delivering the builds from his

> machine

> > and not all of the source code made it into source

> > control.

>

> If that happens you count your losses and rebuild the

> **** he built before he left while sueing his *** off

> for damages.

You could only do that if the developer deleted code from the repository deliberately. In this case is was just a matter of lax process control. And the only option the company could have would be to attempt to get the original developer to recreated it via contract work (and which was one solution that was proposed.)

jschella at 2007-7-20 18:23:17 >

> So it's OK for you to read and comment but not for

> anybody else?

Are you just looking for a fight or what? Nobody said anything of the sort. You're overreacting and there's quite a bit of irony in your telling me to ignore what people post and then getting upset of what I post.

kablaira at 2007-7-20 18:23:17 >