Comments on: No New APIs? http://stuffthathappens.com/blog/2008/05/13/no-new-apis/ Technology and Geek Stuff by Eric Burke Mon, 26 Jul 2010 14:36:32 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Anthony Petrov http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-14058 Anthony Petrov Mon, 09 Jun 2008 12:25:29 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-14058 In fact you can use the AWTUtilities w/o any problems on any platforms now. Go check how to do it here: http://weblogs.java.net/blog/joshy/archive/2008/06/java_doodle_fad.html In fact you can use the AWTUtilities w/o any problems on any platforms now. Go check how to do it here:
http://weblogs.java.net/blog/joshy/archive/2008/06/java_doodle_fad.html

]]> By: Alex Miller http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-11041 Alex Miller Thu, 15 May 2008 05:06:00 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-11041 From having worked on several software products over the years, this sort of release and API game is just the tip of the standard-working-practice for releases (and certainly not Sun specific). Customers want features, and they want them now. Products release at a certain rate, usually determined by a variety of forces outside your control (fiscal cycles, industry cycles, engineering cycles, etc). Rarely do these two worlds align. Another example - certain federal agencies have very strict rules over what kind of certification must be done for a "major" or "minor" release and huge games are played to stay within these rules while avoiding security recertification (an annoying and lengthy process). As to your questions - if you can deal with the restrictions and are willing to modify your app when "official" support exists in an API, then go for it. If not, then tough. Wait for Java 7. I understand the frustration but any release schedule is walking a tightrope - for a product as complicated and widely used as Java it's extremely challenging I'm sure. From having worked on several software products over the years, this sort of release and API game is just the tip of the standard-working-practice for releases (and certainly not Sun specific). Customers want features, and they want them now. Products release at a certain rate, usually determined by a variety of forces outside your control (fiscal cycles, industry cycles, engineering cycles, etc). Rarely do these two worlds align.

Another example – certain federal agencies have very strict rules over what kind of certification must be done for a “major” or “minor” release and huge games are played to stay within these rules while avoiding security recertification (an annoying and lengthy process).

As to your questions – if you can deal with the restrictions and are willing to modify your app when “official” support exists in an API, then go for it. If not, then tough. Wait for Java 7. I understand the frustration but any release schedule is walking a tightrope – for a product as complicated and widely used as Java it’s extremely challenging I’m sure.

]]> By: Eric Burke http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-10975 Eric Burke Wed, 14 May 2008 11:41:48 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-10975 But why not just call it Java 7, making it part of the official API right away? It feels like we're making compromises in the name of keeping the name "6u10" instead of moving to "7". But why not just call it Java 7, making it part of the official API right away? It feels like we’re making compromises in the name of keeping the name “6u10″ instead of moving to “7″.

]]> By: Aekold http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-10960 Aekold Wed, 14 May 2008 07:47:32 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-10960 But official API is not changed. Backdoor classes existed in Java always, and many projects used it behind the scene. Like SwingUtilities2 or Base64Decoder, didn't you ever saw it? So, if you are writing legacy application and want it to run everywhere - transparency is not for you. But if you are mature hacker and using undocumented API - you can do it. Think of it like of technology preview, and hope it will be added to official API of Java 7. But official API is not changed. Backdoor classes existed in Java always, and many projects used it behind the scene. Like SwingUtilities2 or Base64Decoder, didn’t you ever saw it?
So, if you are writing legacy application and want it to run everywhere – transparency is not for you. But if you are mature hacker and using undocumented API – you can do it. Think of it like of technology preview, and hope it will be added to official API of Java 7.

]]> By: Ophir Radnitz http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-10915 Ophir Radnitz Tue, 13 May 2008 22:19:30 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-10915 Thank you. Brilliant post. Thank you. Brilliant post.

]]> By: Eric Burke http://stuffthathappens.com/blog/2008/05/13/no-new-apis/comment-page-1/#comment-10906 Eric Burke Tue, 13 May 2008 18:21:01 +0000 http://stuffthathappens.com/blog/2008/05/13/no-new-apis/#comment-10906 One more question...will the first JavaFX implementation use these new APIs behind the scenes, and how will that affect portability? One more question…will the first JavaFX implementation use these new APIs behind the scenes, and how will that affect portability?

]]>