RSS feed [root] /discussion /weblog /java



title search:


Tue Jun 09 00:02:05 HKT 2020


(google search) (amazon search)
download zip of files only

Tue Jun 09 00:02:20 HKT 2020 From /weblog/java/discussion


(google search) (amazon search)

Wed Jun 03 15:55:56 HKT 2020 From /weblog/java/discussion


How to write a (toy) JVM -

(google search) (amazon search)

Mon Sep 21 11:47:50 HKT 2015 From /weblog/java/discussion


(google search) (amazon search)

Fri Aug 07 16:51:03 HKT 2015 From /weblog/java/discussion


java-server-application-troubleshooting-using-jdk-tools -[..]ication-troubleshooting-using-jdk-tools/

(google search) (amazon search)

Mon Feb 11 11:47:44 HKT 2013 From /weblog/java/discussion

idea of improving java language

These look interesting, worth to take a look:

1) Auto null checking:[..]ebourne?entry=adding_auto_null_checks_to
I don't think this is a good idea as I don't think there is a way can handle default object reference more generic then NULL. However, I would like to have a way to customize NULL behaviour (or default NULL object). Say, for String, I will think empty string ("") is same as NULL. Thus, I would like to have define something like:

public final class Strinig {
null {
return "";
// the rest of string implementation

Then the default reference of String, rather than point to NULL, now it point to an empty String.

2) Add closure to Java:[..]ebourne?entry=adding_closures_to_java_or
Not much comment, it is something nice to have but I don't think really add a lot of value, just like java5 foreach loop.

3) Auto casting:[..]lebourne?entry=adding_auto_casts_to_java
I guess generic already does this?

Of course, there are still some other problem on some people's mind, like:

On the other hand, somebody don't like to change java language as it probably make your code less portable.

4) Some idea of useful util language -

5) API for adding feature -[..]s?track=NL-461&ad=636686&thread_id=49035

A lot more other idea -

Drop extends -[..]at-if-java-8-dropped-extends.html?page=2

(google search) (amazon search)

Tue Dec 25 21:14:19 HKT 2012 From /weblog/java/discussion


Use annotation for default data, rather than hard code it -

(google search) (amazon search)

Tue Oct 02 20:31:57 HKT 2012 From /weblog/java/discussion


In core libraries like StringBuffer we should prefer the lesser evil of code duplication to the loss of performance. -[..]lder%7D-are-inconsistent-td34479926.html

(google search) (amazon search)

Wed Apr 18 23:22:31 HKT 2012 From /weblog/java/discussion


Discussion about reducing latency -[..]n-with-my-channels-nirvana-and-azul.html

(google search) (amazon search)

Thu Jan 27 22:41:09 HKT 2011 From /weblog/java/discussion


A lot of difference implementation of factorial -

(google search) (amazon search)

Thu Dec 06 00:28:42 HKT 2007 From /weblog/java/discussion


Cohen goes on to describe when and how to use each of these methods:

* Basic - breakpoints
* Primal - debug messages
* Hot Shot - dynamic proxy
* Brute Force - run-time profiler
* New Age - through aspects

A good overview -

Follow up discussion -[..]_id=47708&asrc=EM_NLN_2697526&uid=703565

(google search) (amazon search)

Tue Dec 19 01:57:42 HKT 2006 From /weblog/java/discussion

port other code to java

This look like a nice way to get legacy code to work with java, if it really work with more compehensive project[..]rilliant-c-to-mips-to-java-bytecode.html

(google search) (amazon search)

Sat Nov 11 23:43:25 HKT 2006 From /weblog/java/discussion


Some interesting points, but I guess this guy will improve his productivity after familiar with java environment? -[..]tsort=0&tid=156&mode=thread&cid=13845934

(google search) (amazon search)

Mon May 29 11:58:43 HKT 2006 From /weblog/java/discussion

comment of final

I personally like to declare everything in final and immulatable so that it give me feel it more safe (e.g.: variable won't be replace with other value unexpected; method won't be override unexpected). The following is some discussion, see if you interested.[..]/2005/06/how-often-do-you-use-final.html[..]rd-particular-in-javautilconcurrent.html

Here is a few update that against using final, mainly against using final class but not final method and variable:[..].MichaelFeathers.ItsTimeToDeprecateFinal[..]gView?showComments=true&entry=3325667363

And here is some support using final:
Prevent security and memory leak in rare case:[..]a-tip-10-constructor-exceptions-are.html

(google search) (amazon search)

Fri May 19 14:41:12 HKT 2006 From /weblog/java/discussion

speed of sun

Also, top 25 bugs seem always the same?

Here is one nice blog about opensource java, see if anyone agree his position:

(google search) (amazon search)

Mon Mar 27 12:09:38 HKT 2006 From /weblog/java/discussion

java transaction blog entry

Contain quite a number of link to useful resource:[..]e/archive/2006/03/transactions_ar_1.html

(google search) (amazon search)

Mon Feb 20 16:55:21 HKT 2006 From /weblog/java/discussion

problem of java logging at shared VM

There is a problem of logging if you run multiple web application at single JVM, you can take a look here to learn more about this.[..]ging_java_logmanager_shared_hosting.html

In our own expeerience, logging is not the major problem, it is easy to write a logging library. The main problem is updating individual application instance without affecting the other application instance. Finally we run individual tomcat for every application we host, which spend a lot more memory :-(

(google search) (amazon search)

Mon Nov 28 17:57:19 HKT 2005 From /weblog/java/discussion

security of csharp and java

For me it is a security features overview of java and .net more than a
comparison. Useful resource!

Overall, I believe C# provides greater expressiveness and is more suited to writing performance-critical code than Java, while sharing Java's elegance and simplicity, which makes both much more appealing than C++.

(google search) (amazon search)

Fri Oct 14 18:42:28 HKT 2005 From /weblog/java/discussion

Arrays and Collections

(google search) (amazon search)

Thu Jul 07 01:55:24 HKT 2005 From /weblog/java/discussion

Deprecation Discussion

Discuss whether deprecation api should be removed... My opinions is remove after a period, what is yours?[..]/jclingan?entry=deprecation_of_java_apis

(google search) (amazon search)