Show HN: God mode in production code – a new way to debug in Scala
1–10 of 84 posts
Re: Show HN: God mode in production code – a new way to debug in Scala
#2Looks great!
Re: Show HN: God mode in production code – a new way to debug in Scala
#3I've been tracking down a NullPointerError in Play's new JSON inception handling. Eclipse's debugger has gotten me nowhere, I look forward to seeing how this one works!
Re: Show HN: God mode in production code – a new way to debug in Scala
#4I know that at least from my experience debugging our apps in production did become harder as we scaled out in terms of servers, users and code. I do wonder if its something that should be handled at the code level (by being more defensive, taking a more immutable approach) or by having better debugging tools. Anyone knows if this supports Ruby?
Re: Show HN: God mode in production code – a new way to debug in Scala
#5looks promising.
Re: Show HN: God mode in production code – a new way to debug in Scala
#6I know that at least from my experience debugging our apps in production did become harder as we scaled out in terms of servers, users and code. I do wonder if its something that should be handled at the code level (by being more defensive, taking a more immutable approach) or by having better debugging tools. Anyone knows if this supports Ruby?
Or by using a better type system. Or by using the type system that's available in the language. Because it's all too easy to ignore the types and for example call `get` on a Scala Option value, or `fromJust` on a Haskell Maybe. Both will throw an exception at runtime if the Option/Maybe is empty.
Re: Show HN: God mode in production code – a new way to debug in Scala
#7I'd give my firstborn for a debugger/profiler like this in .NET
Re: Show HN: God mode in production code – a new way to debug in Scala
#8I know that at least from my experience debugging our apps in production did become harder as we scaled out in terms of servers, users and code. I do wonder if its something that should be handled at the code level (by being more defensive, taking a more immutable approach) or by having better debugging tools. Anyone knows if this supports Ruby?
Or by using a better type system. Or by using the type system that's available in the language. Because it's all too easy to ignore the types and for example call `get` on a Scala Option value, or `fromJust` on a Haskell Maybe. Both will throw an exception at runtime if the Option/Maybe is empty.
Type safety does help a lot. The real hard ones I found to track down are the ones where you have to chase for a particular state to re-occur and you can't get a repro from ops or qa. At least for me these are the main bummers...
Re: Show HN: God mode in production code – a new way to debug in Scala
#9There's a very strong founding team around this company. I don't do Java too much these days, but if I were, I'd definitely use Takipi.
Re: Show HN: God mode in production code – a new way to debug in Scala
#10What about python?