Any plans to support Android in the near future?
Takipi – Java debugging reinvented
11–20 of 39 posts
Re: Takipi – Java debugging reinvented
#12What people sometimes fail to realize is that proper testing disciplines can mitigate practically all bugs in production. I haven't seriously used a debugger in 2 years, methinks. So giving developers "X-ray vision" to their servers in production, however innovative, is not a real solution.
Applications fail; it's a real life fact. The most talented teams face bugs, even in applications which undergo extensive testing. Not to mention scenarios which are very hard to anticipate and simulate, mainly ones related to fast scaling.
Re: Takipi – Java debugging reinvented
#13How well would this handle Spring code (in full autowired, horrible stack trace glory)?
When you install Takipi, you are asked to enter your top packages (e.g. "com.mycompany;org.foobar.common"). Code outside of the filter will not be shown to you when viewing stack traces.
In addition, if, for an example, an exception is thrown by Spring AND caught by Spring, you will not receive an event for that case.
Re: Takipi – Java debugging reinvented
#14Any plans to support Android in the near future?
Takipi is mainly designed for production/staging debugging, and thus targets servers and development environments.
Re: Takipi – Java debugging reinvented
#15Any plans to support Android in the near future?
Takipi is mainly designed for production/staging debugging, and thus targets servers and development environments.
Sorry, to clarify, I meant support us developers making apps on the PC for Android (not using your tool directly on Android) :)
Re: Takipi – Java debugging reinvented
#16This seems pretty legit. I really like the personality you gave the site with its design.
Do you have any plans to support GitHub repositories as a location to pull source from in the event we don't really want to deploy a jar with our source in it?
Re: Takipi – Java debugging reinvented
#17Earlier quoted context omitted.
Takipi is mainly designed for production/staging debugging, and thus targets servers and development environments.
Sorry, to clarify, I meant support us developers making apps on the PC for Android (not using your tool directly on Android) :)
I'm sorry, Android development is currently not supported.
Re: Takipi – Java debugging reinvented
#18I know it works on the JVM level, but we use Glassfish a lot in production and I'm interested in finding out exactly how practical it is to use Takipi with Glassfish?
Re: Takipi – Java debugging reinvented
#19What people sometimes fail to realize is that proper testing disciplines can mitigate practically all bugs in production. I haven't seriously used a debugger in 2 years, methinks. So giving developers "X-ray vision" to their servers in production, however innovative, is not a real solution.
As you are down voted I wonder: I have the same experience here. Very few serious problems (1/year) that come from developer bugs. Others seem to have much more, e.g. when people ask me if the devs here have pager duty (which they haven't).
I also wonder if we test too much (ca. 85% path coverage, 15k unit tests (3x rewritten), automatic selenium tests, explorative manual tests, automatic API tests, developer acceptance tests).
Re: Takipi – Java debugging reinvented
#20I know it works on the JVM level, but we use Glassfish a lot in production and I'm interested in finding out exactly how practical it is to use Takipi with Glassfish?
Very practical :)
Takipi fully supports Glassfish, as well as all other major web servers and containers.