Live data from Hacker News

Show HN: Java Bullshifier

takipi.github.io

1–10 of 84 posts

Re: Show HN: Java Bullshifier

#3
At first I thought this another one of the several Java shaming projects that have been posted in the past on HN (usually in regards to the ridiculous class names of some projects ... aka Spring).

But this project actually has some serious utility particularly for byte code manipulators are just alternative compilers like AspectJ. Particularly AspectJ as I have seen it fail on things that neither the Eclipse compiler (JDT) or Open JDK fail on.

Re: Show HN: Java Bullshifier

#4
I'm glad to learn that entire businesses exist thanks to the fact that Java has overly verbose exception outputs which are designed to hide the information you are seeking between 200 lines of call stack prints.

Re: Show HN: Java Bullshifier

#8
Hi, Alex from OverOps here. We've created the "Bullshifier" internally to stress test edge cases with our own monitoring tool (http://www.overops.com).

Whenever an exception or a logged error / warning happens in production, it shows you the complete source code leading to it, and the full variable state across the entire call stack.

Using Java Bullshifier, we're able to generate random applications with call stacks that can go thousands of frames deep and other quirky behaviors. This helps us make sure the overhead is unnoticed, even in the most extreme cases.

Would be happy to answer any questions.

Re: Show HN: Java Bullshifier

#9
It was about time somebody creates something like this. I do have a complain, classes are named random. If you used a tool that generates human like names, it would still be random but looked much better.

I will see to create a similar rails tool. I intend to test just stress of people who will look at the code and try to understand what it does.

Re: Show HN: Java Bullshifier

#10

I'm glad to learn that entire businesses exist thanks to the fact that Java has overly verbose exception outputs which are designed to hide the information you are seeking between 200 lines of call stack prints.

When something blows, arent you just happy to get as much information as possible?

I remember when developing in VB classic, youd get something lile "error -68377388484". Perhaps you prefer this?

Post reply on HN