EDUCAUSE | Java

E07 Podcast: Interactive Services on Mobile Devices for Higher Education

gbayne — Tue, 23 Sep 2008 18:00:30 -0500

This forty-eight minute podcast presents a session from the EDUCAUSE 2007 Annual Conferece. The session, "Interactive Services on Mobile Devices for Higher Education," consists of a panel from the University of North Carolina at Wilmington discussing a new initiative to develop and test a wide range of information services accessible through mobile devices. This session compares the relative costs and advantages of applications based on SMS text messaging, WAP browsers, and Java MIDlets as well as the structuring of the relationship between the faculty start-up and the institution to develop and pursue the resulting initiatives. A PDF is also available for this session.

This session features:

Jeff Brown, Professor of Mathematics, University of North Carolina at Wilmington
Robert R. Hoon, Associate General Counsel, University of North Carolina at Wilmington
Debra Saunders-White, Vice Chancellor, ITSD & CIO, University of North Carolina at Wilmington
Ronald J. Vetter, Department of Computer Science, University of North Carolina at Wilmington

The down side of open sourcing Java

StuartYeates — Wed, 29 Nov 2006 05:31:14 -0600

Sun vice president and fellow Graham Hamilton has apparently left sun over their open sourcing of Java.

Hamilton, who in the past spearheaded Sun's work on compliance, interoperability and portability in Java sees the open sourcing of the platform as a bad thing because it erodes the technical uniformity of the platform, by allowing others to build incompatible versions. He is, of course, right. Open sourcing Java will allow third parties to fork the platform, but I have no doubt that the network effect would cause these to wither and die.

cheers, stuart

Sun open source the technology formerly known as Java

StuartYeates — Mon, 13 Nov 2006 05:55:44 -0600

There's been huge coverage of the fact that Sun Microsystems has announced that it will release the core products which it has been marketing as Java as open source.

What much of the coverage doesn't mention is that what they're open sourcing is not "Java," since they're not relinquishing that trademark, but merely something technically indistinguishable from it. Sun is likely to provide a comprehensive test suite and allow those that pass with flying colours to use certain trademarks in restricted ways, much as they did a few years ago with their 100% Java program several years ago.

The move from Sun is a logical response to the increasing maturity of the already GPL'd classpath and gcj projects, which taken together amount to a reimplementation of Java. By GPL'ing the "real" Java, Sun prevents the open source community from abandoning it for the the new contender.

Having two separate implementations of Java is actually a great thing, because it promotes competition between them. The Classpath/gcj implementation, for example is already available on far more platforms than Sun's java, simply because it is built the same portable framework as gcc, the Gnu Compiler Collection.

Read more on almost every tech news site.

cheers stuart

Agile Java Book Review

mmorton8 — Thu, 06 Jul 2006 08:43:00 -0500

I have written a Book Review for InfoQ on Agile Java.

Using Netbeans/Derby to Teach Web Development

mmorton8 — Wed, 05 Jul 2006 14:26:57 -0500

This last semester I taught Java Web Development here at UNO. It was a great experience from the standpoint that it made me learn things even deeper. I hope my students got something out of it. I was also fortunate enough to have taken the approach of trying to facilitate learning rather than playing the "I know everything" game (in fact I don't :) ). This allowed me to leverage knowledge in the classroom and I think all had a better experience because of it. We went over many items and even put some of it into practice. The thing that really saved my rear though was Netbeans + Derby. Without that I probably would have created a bunch of people who decided that Java web development sucked. Even though it is only hard because it has gotten so complex and layered. Netbeans allowed me to skip all of the Tomcat setup. Derby allowed me to to skip the DB setup and Netbeans made integrating all of it a piece of cake. Great work guys! I am glad to see the Swing crew come though.

Sun announce more software to be open sourced

StuartYeates — Fri, 09 Jun 2006 10:22:52 -0500

Sun have announced that their Sun Java System Portal Server (jsr168) system, is to be released as open source. They've already released some of the more minor components, a few portlets.

I'd like to put this down to high ideals on the part of Sun, but I find it hard. They've seen that the portal market is being consolidated by merges, both planned and in progress and they don't want to be left out in the cold. By open sourcing their portal server they place themselves to merge with the other contenders and greatly reduce the cost of supporting and maintaining the software going forward.

Is Java yesterday's technology?

StuartYeates — Tue, 27 Dec 2005 13:42:09 -0600

Bruce Eckel has written an article entitled "The departure of the hyper-enthusiasts" in which he suggests that a tipping point has been reached in programming ecosystem and that Java, long the darling child, is now on the way out. One of the new contenders is Ruby with it's Ruby on rails web framework.

In software engineering, ideas are largely embodied in formalisms and tools, and the most important of these are languages and their implementations respectively. Each generation of software engineering ideas leads to new languages and new implementations, with new ideas and a different balance of old ideas. Few of these languages take off in the real world, even if they are things of beauty to the academic software engineers, because in the real world the most important factor is retraining. There are huge numbers of technical people who have programming as part of their job, and retraining them to use a new language is a huge stumbling block, one traditionally solved by basing one language on a previous one. Just as Java was promoted as "better C++, with garbage collection," Ruby is "better Perl, with objects that work." Of course, promoting a new language by comparison to an existing one invites programmers to bring their old bad habits with them.

Those who are likely to be bitten hardest by a transition to a new language are not the programmers or the techies, but the institutions or organisations which have standardised on language-specific protocols and specifications for key pieces of infrastructure. Java isn't going to go away in the next ten years, and probably not in the next fifteen, but if they've invested a huge amount of time and effort in a Java-only system, within the next three to five years institutions are going to find that the new buzzwords, the new toys, the new tools and, more importantly, the new bright-young-things are going to pass them by.

Those who have language-independent (or readily bridge-able) protocols and specifications will have little to worry about. Staff will need to be retrained / up-skilled, but this only need be done incrementally, since Java and Ruby should play nicely together.

Java 5 catches up with C#

StuartYeates — Fri, 02 Dec 2005 11:00:03 -0600

I have just returned from Java 5 catches up with C# by Barry Cornelius, a talk he gave here at the RTS. I've got to admit that while Barry is right, Java 5 is catching up with C# in the sheer number of features, I seem to disagree with him on whether this is a good thing.

There are, generally speaking, two ways of designing a computer programming language. The first is to take an underlying metaphor and build a language around it, adding the bear minimum number of features to it to be able to achieve everything you want to achieve. This approach is usually based on the work of very small teams and results in small, fast and efficient languages that every user needs to be re-trained to use, because none of their old ways of working can be directly adapted. The second way of designing a computer programming language is to take a list of features that might be required and build a language around them. This approach is usually based on committee or consensus decision making and results if large, slow, complex languages which anyone can use, because it supports their existing ways of working.

In short, I'm a fan of languages built using the former method (C, Scheme, RISC assembler, Modula-2, Java 0.1, etc) and Barry appears to be a fan of languages built using the latter model (C++, LISP, C#, Java 5, Ada, etc).

But don't let that put you off the paper if you're interested in in Java and C#, because at the end of the day it's a question of taste.

An Interview with Alfred Essa about Open Source, Web 2.0, and .LRN

mpasiewicz — Wed, 09 Nov 2005 11:42:00 -0600

This 30 minute recording with Alfred Essa, Executive Director of the .LRN Consortium, gathers his thoughts on open source, blogs, podcasts, java, .LRN and a range of other topics.

OSS Watch Edinburgh Event

StuartYeates — Tue, 05 Jul 2005 03:55:00 -0500

The OSS Watch Building Open Source Communities conference seemed to go pretty well yesterday. We had a broad range of people, with a broad range of interests and everyone seem to find something useful.

I had a great day, catching up with old friends and new, including: Gustav Delius University of York; Jim Farmer, Sakai Educational Partnership Program; Sean Keogh, OXILP; Bill Olivier, Development Director (Systems and Technology) JISC; Andrew Savory and Helen Sharp, Open University.