Slashdot Mirror
Domain: dautelle.com
Stories and comments across the archive that link to dautelle.com.
Stories · 7
-
Initializing all Java classes at Start-Up
Jean-Marie Dautelle writes "Java classes are initialized at first-use only which can introduce significant runtime delays detrimental to real-time or games applications (for which accurate scheduling is often required). To solve this problem, the latest open-source Javolution library supports initialization of all Java classes at start-up (e.g. javolution.lang.ClassInitializer.initializeAll(); // Initialize runtime classes (rt.jar) and all classes in classpath). Note: Runtime class initialization (rt.jar) takes typically a few seconds and about 3 Mbytes of memory." -
JADE Project Reborn As Javolution And jScience
dautelle writes "Because of trademark issues we had to rename our Java Addition to Default Environment (JADE) project. We did a little more than that, we created two new projects with additional features and capabilities: Javolution (javolution.org) and jScience (jscience.org). Java developers, please update your bookmarks. You may also read the 'Top 10 reasons' why you should consider using Javolution in your current Java project or how you can take part in this immense undertaking that the jScience project represents." -
Trademarking Open-Source Projects?
dautelle asks: "I had the nasty surprise to receive a letter from a company in New-Zealand asking me to stop using the 'jade' name they have recently trademarked (my open source project has been Java Addition to Default Environment or JADE for short, long before their trademark filing date). I am going to comply, but I wonder if our open-source projects should be trademarked (cost >300$) to prevent such misfortune?" -
Trademarking Open-Source Projects?
dautelle asks: "I had the nasty surprise to receive a letter from a company in New-Zealand asking me to stop using the 'jade' name they have recently trademarked (my open source project has been Java Addition to Default Environment or JADE for short, long before their trademark filing date). I am going to comply, but I wonder if our open-source projects should be trademarked (cost >300$) to prevent such misfortune?" -
Trademarking Open-Source Projects?
dautelle asks: "I had the nasty surprise to receive a letter from a company in New-Zealand asking me to stop using the 'jade' name they have recently trademarked (my open source project has been Java Addition to Default Environment or JADE for short, long before their trademark filing date). I am going to comply, but I wonder if our open-source projects should be trademarked (cost >300$) to prevent such misfortune?" -
Improving The Java Core Library
dautelle writes "Many Java developers are frustrated by the not-so-open process to improve/correct/augment the Java core libraries. Unless you work for Sun or belong to a JSR expert group, there is very little you can do to influence the future of the Java platform. Even the JCP route can be a frustrating one (e.g. JSR-108 withdrawn by Sun because not enough progress made in a timely manner). To address this serious issue, the charter of the Java Addition to Default Environment (JADE for short) has been extended, along with the release of JADE 7.0. Participation to the jade.* package development is truly open (unlike javax.*). The library already provides numerous useful classes, bug fixes, enhanced implementations of existing classes, etc. Hopefully in the near future, the library could become so useful that it becomes a de-facto complement to the JDK." -
Improving The Java Core Library
dautelle writes "Many Java developers are frustrated by the not-so-open process to improve/correct/augment the Java core libraries. Unless you work for Sun or belong to a JSR expert group, there is very little you can do to influence the future of the Java platform. Even the JCP route can be a frustrating one (e.g. JSR-108 withdrawn by Sun because not enough progress made in a timely manner). To address this serious issue, the charter of the Java Addition to Default Environment (JADE for short) has been extended, along with the release of JADE 7.0. Participation to the jade.* package development is truly open (unlike javax.*). The library already provides numerous useful classes, bug fixes, enhanced implementations of existing classes, etc. Hopefully in the near future, the library could become so useful that it becomes a de-facto complement to the JDK."