pdeva1

10 ms·

151.
Java 7 Design Flaw leads to huge backward step for the JVM(chrononsystems.com)
6 points by pdeva1 14y ago|0 comments
152.
'No Compilation' and why Eclipse rocks(chrononsystems.com)
1 points by pdeva1 14y ago|0 comments
153.
Converting Eclipse to a fully 'Dark' theme(eblog.chrononsystems.com)
2 points by pdeva1 14y ago|0 comments
154.
Chronon 4 'Ops' : A new kind of monitoring tool(chrononsystems.com)
1 points by pdeva1 14y ago|0 comments
155.
by pdeva1 14y ago
Try Chronon. While Omniscent is a research project, Chronon is a full blown product http://www.chrononsystems.com/
156.
Recording full Java execution in real time: Inside Chronon 3 Recorder(eblog.chrononsystems.com)
1 points by pdeva1 14y ago|0 comments
157.
LightTable detailed critique: Concept vs Reality(eblog.chrononsystems.com)
193 points by pdeva1 14y ago|132 comments
158.
Chronon Time Travelling Debugger Free for Open Source(eblog.chrononsystems.com)
1 points by pdeva1 15y ago|0 comments
159.
Hidden evils of Java's boolean array(eblog.chrononsystems.com)
2 points by pdeva1 15y ago|1 comments
160.
Hidden evils of Java's String.split() and String.replace()(eblog.chrononsystems.com)
3 points by pdeva1 15y ago|0 comments
161.
Java Bytecode manipulation : Tools of the trade(eblog.chrononsystems.com)
2 points by pdeva1 15y ago|2 comments
162.
by pdeva1 15y ago
the java bytecodes remain unchanged from jvm 5 to 6. The bytecode is all the jvm sees. Thus the backward compatibility does work almost perfectly. Also jvm 6 has been out for long enough now to have ironed out any potential issues if there
163.
by pdeva1 15y ago
the point of the article is that, whether its supported or not, enterprises still continue to use it. It is similar in regards to IE 6 that MS itself has campaigns to tell enterprises to switch from IE 6 ( http://www.ie6countdown.com/ ), b
164.
by pdeva1 15y ago
yup, that is what "backward compatibility" stands for...
165.
JVM 5 is the new IE6(eblog.chrononsystems.com)
42 points by pdeva1 15y ago|16 comments
166.
How we improved our product by listening closely to our users(eblog.chrononsystems.com)
3 points by pdeva1 15y ago|0 comments
167.
Post Execution Logging solves the Java Logging mess(chrononsystems.com)
1 points by pdeva1 15y ago|0 comments
168.
Logging is fundamentally broken(eblog.chrononsystems.com)
1 points by pdeva1 15y ago|0 comments
169.
Using mind maps for design(eblog.chrononsystems.com)
1 points by pdeva1 15y ago|0 comments
170.
-Xmx is hurting the usability of Java(eblog.chrononsystems.com)
5 points by pdeva1 15y ago|2 comments
171.
Is the traditional Debugger still relevant in 2011?(eblog.chrononsystems.com)
1 points by pdeva1 15y ago|0 comments
172.
Method Size Limit in Java(eblog.chrononsystems.com)
28 points by pdeva1 15y ago|7 comments
173.
by pdeva1 15y ago
ironically it seems to work best on IE 9, due to IE's hardware acceleration
174.
Chronon Systems - Beta report card(eblog.chrononsystems.com)
1 points by pdeva1 16y ago|0 comments
175.
by pdeva1 16y ago
or you could just work at home...