Prashant Deva - DZone Member

JavaScript String Functions

Apr 04, 2012 · Jimmy Vu

Minor correction of a mistake on my part:

The answert to the first question should read:

further our mission of 'No more Non Reproducible Bugs'

not

further our mission of 'Non Reproducible Bugs'

Sorry I was too excited with all the stuff happening today :)

Look Back On Your Application's Past With Chronon

Apr 04, 2012 · James Sugrue

Minor correction of a mistake on my part:

The answert to the first question should read:

further our mission of 'No more Non Reproducible Bugs'

not

further our mission of 'Non Reproducible Bugs'

Sorry I was too excited with all the stuff happening today :)

The traditional debugger : is it still relevant in 2011?

Jul 19, 2011 · Prashant Deva

neither do you

The traditional debugger : is it still relevant in 2011?

Jul 19, 2011 · Prashant Deva

i think that applies to you here more than me since you continue posting without any technical argument to back up your position.

The traditional debugger : is it still relevant in 2011?

Jul 19, 2011 · Prashant Deva

as usual a comment just based on the like/dislike factor lacking any technical merit

The traditional debugger : is it still relevant in 2011?

Jul 19, 2011 · Prashant Deva

Maybe you havent looked around, but dzone and javalobby are an aggregation of blog posts. What javalobby and dzone provide is a way to surface those blog posts and invite discussions on them. I dont see too many blog posts which start off with the credentials of the author. If you are looking for independent, third party, peer reviewed journal articles you are in the wrong place. Specifying my nature of involvement with Chronon wouldnt add to anything to the technical content of the blog post. If you think the blog post is biased or wrong argue that on technical terms not on the basis of my involvement with Chronon. So far you havent come up with any.

The traditional debugger : is it still relevant in 2011?

Jul 18, 2011 · Prashant Deva

if you know of great alternative why not post about them. We know of our alternative to the debugger and we have posted them. How javalobby formats or posts their items is not under our control. Our aim with the post was to give clear, technical arguments for why we think our approach is better. This is no different than any post on javalobby or dzone which gives technical comparison between 2 products/algorithms/approaches. Your whole tone throughout seems you see this an 'infomercial' just because we are talking about our product. It would have been had we not given solid technical arguments, but that is not the case here. The post has open commenting and anyone is open to challenging the technical details put through or suggest better alternatives.

The traditional debugger : is it still relevant in 2011?

Jul 18, 2011 · Prashant Deva

just because people use it doesnt mean its the right or wrong approach to the problem. you use the traditional debugger cause there is no other alternative. though i bet you used log files for that server that crashed after running for 4 weeks. This is the same as saying noone should have invented the iphone or the touch interface cause traditional phones work so well. We have put forward real technical reasons why our approach is better. If you feel its not why not make real technical arguments yourself rather than just calling our post spam. as usual, your post lacks any technical merit or argument other than the fact you dont like us just cause...

The traditional debugger : is it still relevant in 2011?

Jul 18, 2011 · Prashant Deva

if you think any of the points in that post are not valid why not make a technical argument instead of trashing it just because our software is commercial.

Is the traditional debugger still relevant in 2011?

Jul 18, 2011 · James Sugrue

Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.

Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.

Is the traditional debugger still relevant in 2011?

Jul 18, 2011 · James Sugrue

Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.

Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.

Is the traditional debugger still relevant in 2011?

Jul 18, 2011 · James Sugrue

Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.

Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.

Coding Horror: Online Newspapers, Offline

Jun 14, 2011 · Gerd Storm

So would everyone I guess. But they are the reality of this world and will exist in some form in a large codebase.

Coding Horror: Online Newspapers, Offline

Jun 14, 2011 · Gerd Storm

So would everyone I guess. But they are the reality of this world and will exist in some form in a large codebase.

Method Size Limit in Java

Jun 14, 2011 · James Sugrue

So would everyone I guess. But they are the reality of this world and will exist in some form in a large codebase.

Method Size Limit in Java

Jun 14, 2011 · James Sugrue

So would everyone I guess. But they are the reality of this world and will exist in some form in a large codebase.

Learn Haskell: Lesson 1: Hello, World!

Jun 08, 2011 · Gerd Storm

This is exactly the kind of misconception I am talking about.

If your app uses extra memory then yes, there will be extra GC.

However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.

Learn Haskell: Lesson 1: Hello, World!

Jun 08, 2011 · Gerd Storm

This is exactly the kind of misconception I am talking about.

If your app uses extra memory then yes, there will be extra GC.

However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.

Misconceptions regarding Java heap size arguments

Jun 08, 2011 · James Sugrue

This is exactly the kind of misconception I am talking about.

If your app uses extra memory then yes, there will be extra GC.

However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.

Misconceptions regarding Java heap size arguments

Jun 08, 2011 · James Sugrue

This is exactly the kind of misconception I am talking about.

If your app uses extra memory then yes, there will be extra GC.

However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.

Loop Recognition: a compact benchmark in four programming languages C++/Java/Go/Scala

Jun 04, 2011 · Dev Stonez

Nice analysis of the claims of this paper by Jeremy Manson http://jeremymanson.blogspot.com/2011/06/scala-java-shootout.html

Misconceptions regarding Java heap size arguments

May 17, 2011 · James Sugrue

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Misconceptions regarding Java heap size arguments

May 17, 2011 · James Sugrue

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Learn Haskell: Lesson 1: Hello, World!

May 17, 2011 · Gerd Storm

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Learn Haskell: Lesson 1: Hello, World!

May 17, 2011 · Gerd Storm

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Learn Haskell: Lesson 1: Hello, World!

May 17, 2011 · Gerd Storm

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Misconceptions regarding Java heap size arguments

May 17, 2011 · James Sugrue

1. As said in your link itself, the gc will choose the lower of 1/4 or 1gb as max heap size. So even though you have 24gb of ram, the max heap size wont be larger than 1gb.
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.

Learn Haskell: Lesson 1: Hello, World!

May 16, 2011 · Gerd Storm

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Learn Haskell: Lesson 1: Hello, World!

May 16, 2011 · Gerd Storm

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Learn Haskell: Lesson 1: Hello, World!

May 16, 2011 · Gerd Storm

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Misconceptions regarding Java heap size arguments

May 16, 2011 · James Sugrue

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Misconceptions regarding Java heap size arguments

May 16, 2011 · James Sugrue

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Misconceptions regarding Java heap size arguments

May 16, 2011 · James Sugrue

You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.

Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.

Public Beta Open For Chronon: The Time Travelling Debugger

Mar 07, 2011 · James Sugrue

currently we are focused on eclipse only

Public Beta Open For Chronon: The Time Travelling Debugger

Mar 07, 2011 · James Sugrue

currently we are focused on eclipse only

Public Beta Open For Chronon: The Time Travelling Debugger

Mar 07, 2011 · James Sugrue

currently we are focused on eclipse only

Rapid SVN

Jul 14, 2010 · Christopher Penkin