Off the Top: Java Entries


May 25, 2006

Developing the Web for Whom?

Google Web Developer Toolkit for the Closed Web

Andrew in his post "Reading user interface libraries" brings in elements of yesterday's discussion on The Battle to Build the Personal InfoCloud. Andrew brings up something in his post regarding Google and their Google Web Developer Toolkit (GWT. He points out it is in Java and most of the personal web (or new web) is built in PHP, Ruby [(including Ruby on Rails), Python, and even Perl].

When GWT was launched I was at XTech in Amsterdam and much of the response was confusion as to why it was in Java and not something more widely used. It seems that by choosing Java for developing GWT it is aiming at those behind the firewall. There is still much development on the Intranet done in Java (as well as .Net). This environment needs help integrating rich interaction into their applications. The odd part is many Intranets are also user-experience challenged as well, which is not one of Google's public fortés.

Two Tribes: Inter and Intra

This whole process made me come back to the two differing worlds of Internet and Intranet. On the Internet the web is built largely with Open Source tools for many of the big services (Yahoo, Google, EBay, etc.) and nearly all of the smaller services are Open Source (the cost for hosting is much much lower). The Open Source community is also iterating their solutions insanely fast to build frameworks (Ruby on Rails, etc.) to meet ease of development needs. These sites also build for all operating systems and aim to work in all modern browsers.

On the Intranet the solutions are many times more likely to be Java or .Net as their is "corporate" support for these tools and training is easy to find and there is a phone number to get help from. The development is often for a narrower set of operating systems and browsers, which can be relatively easy to define in a closed environment. The Google solution seems to work well for this environment, but it seems that early reaction to its release in the personal web it fell very flat.

13 Reasons

A posting about Top 13 reasons to CONSIDER the Microsoft platform for Web 2.0 development and its response, "Top 13 reasons NOT to consider the Microsoft platform for Web 2.0 development" [which is on a .Net created site] had me thinking about these institutional solutions (Java and .Net) in an openly developed personal web. The institutional solutions seem like they MUST embrace the open solutions or work seamlessly with them. Take any one of the technical solutions brought up in the Microsoft list (not including Ray Ozzie or Robert Scoble as technical solutions) and think about how it would fit into personal site development or a Web 2.0 developed site. I am not so sure that in the current state of the MS tools they could easily drop in with out converting to the whole suite. Would the Visual .Net include a Python, PHP, Ruby, Ruby On Rails, or Perl plug-in?The Atlas solution is one option in now hundreds of Ajax frameworks. To get use the tools must had more value (not more cost or effort) and embrace what is known (frogs are happy in warm water, but will not enter hot water). Does Atlas work on all browsers? Do I or any Internet facing website developer want to fail for some part of their audience that are using modern browsers?

The Web is Open

The web is about being browser agnostic and OS agnostic. The web makes the OS on the machine irrelevant. The web is about information, media, data, content, and digital objects. The tools that allow us to do things with these elements are increasingly open and web-based and/or personal machine-based.

Build Upon Open Data and Open Access

The web is moving to making the content elements (including the microconent elements) open for use beyond the site. Look at the Amazon Web Services (AWS) and the open APIs in the Yahoo Developer Network. Both of these companies openly ease community access and use of their content and services. This draws people into Amazon and Yahoo media and properties. What programming and scripting languages are required to use these services? Any that the developer wants.. That is right, unlike Google pushing Java to use their solution, Amazon and Yahoo get it, it is up to the developer to use what is best for them. What browsers do the Amazon and Yahoo solutions work in? All browsers.

I have been watching Microsoft Live since I went to Search Champs as they were making sounds that they got it too. The Live Clipboard [TechCrunch review] that Ray Ozzie gave at O'Reilly ETech is being developed in an open community (including Microsoft) for the whole of the web to use. This is being done for use in all browsers, on all operating systems, for all applications, etc. It is open. This seems to show some understanding of the web that Microsoft has not exhibited before. For Microsoft to become relevant, get in the open web game, and stay in the game they must embrace this approach. I am never sure that Google gets this and there are times where I am not sure Yahoo fully gets it either (a "media company" that does not support Mac, which the Mac is comprised of a heavily media-centric community and use and consume media at a much higher rate than the supported community and the Mac community is where many of the trend setters are in the blogging community - just take a look around at SXSW Interactive or most any other web conference these days (even XTech had one third of the users on Mac).

Still an Open Playing Field

There is an open playing field for the company that truly gets it and focusses on the person and their needs. This playing field is behind firewalls on Intranet and out in the open Internet. It is increasingly all one space and it continues to be increasingly open.



November 9, 2003

Apple Mac OS X as a great application development platform

Steve Neiderhauser has written an overview of what makes Apple a great application development platform. I cringe each time I hear somebody that has never understood application development or design state that Apple is a only a designer's platform. I bought an Apple laptop because of OS X, so that I could have a mobile UNIX platform for developing Web Applications and continuing my UNIX and OpenSource application development skills. I quickly found that the OS X platform was great for anytime of development, but I have not had the time to stay on top of my own development projects, as much I would like. I also found out that much of the Palm OS was built and maintained on Macs and UUNet has been largely a Mac-based company for its business practices.



September 3, 2003

JBuilder 9 on Mac OS X

Hmmm, for future use, MacOSX Hints provides Installing JBuilder 9 on OS X. I have run previous versions on Windows and Linux, but have not attempted on OS X yet.



April 16, 2003

Java and AppleScript intro

Mac OS X Hints offers an Intro to Java that interacts with AppleScript. This intro works with iTunes, but can work with any AppleScript available application.



January 27, 2003

Poi aims to open MS file formats to Java

Chris pointed me to an excellent overview of Poi. Poi is an Apache Jakarta project that aims to open Microsoft file formats to Java. Somehow I think I will be following Poi for a while.



April 3, 2002

PHP with Java tutorial over at Dev Shed. Why not JSP? PHP is quicker to write and quicker to run.


March 30, 2002

Java founder, James Gosling has a Q & A session with Computerworld regarding .Net. This may not be an unbiased review, but Gosling repeats much of what most Microsoft developers I know have brought up. The memory problems and security, with very little that can be done to improve these two elements and keep in the MS family.


January 30, 2002

Web Services Interoperability from James†Snell on O'Reilly Net's XML.Com. This wonderful piece demonstrates, with code, the interaction that is currently possible with standard development environments. This is familiar territory for me from a recent past life, although it was not using SOAP, like these examples do.


November 14, 2001

Jim Jagielski writes about It Don't Amount to Beans, which discusses Java 2 Enterprise Edition (J2EE) application servers. This article states what many complain about, that Java Web solution is not for everything. Knowing your needs, knowing your resources, knowing what you need to process, and knowing the speed and efficiency of scripting languages (Perl, PHP, etc) will greatly help your overal project and application. The article gets at poorly implementing JSP where it is not needed or where it performs poorly. Java can kick some serious behind when used properly and with enough resources behind it. This article helps to sharpen minds.

Previous Month

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.