What's with the general disdain for Java here? It seems as though some Slashdotters are always looking for a reason to slam Java (FYI, Java != Sun's implementation of Java).
Ok, maybe Java's not totally free, but neither are you and I. It's free enough, and an excellent platform for enterprise application development. I can't think of another language that gives me the productivity and yet preserves flexibility of platform and vendor (well, except maybe Perl).
I recently noticed that while linking up a new XP machine with my Win2k laptop via a crossover cable, that the XP home networking wizard 'required' the user to make a setup floppy that needed to be installed on all non-XP machines on the home LAN (not sure why).
My laptop doesn't have a floppy, but I was able to just fiddle with TCP/IP settings. Somehow I doubt that your average end user would be able to manage that though.
Nice to see a book that pulls together several of the great OpenSource development tools that are out there. I've often thought that with enough time and effort, one could put together a truly amazing development system with nothing but OSS and elbow grease. Unfortunately, I've only been able to really internalize Ant and CVS so far. Imagine a well integrated suite of the following...
NetBeans ArgoUML JRefactory JUnit Ant CVS Bugzilla Tomcat JBoss Linux
...and of course a little Perl to glue it all together.;)
I agree that under current law the guy doesn't seem to have much of a case, since the information was publicly available at city offices. But expectations about access to information are rising and this will soon seem like an unreasonable burden on the public.
Why should I have to take a day off work to spend at the county office, photocopying every code I might concievably need, instead of quickly looking up what I need to know on the Internet in the evenings when I need it.
At the very least, local governments should require the the copyright holder to allow city offices to maintain the information online. I'm sure they could still manage to sell a few copies of the hardcover version.
Bottom line is that if I want to give away
my intellectual property for the greater good,
that's my business. Our constitution mandates
freedom and democracy, not capitalism.
No matter what you do it would be a good idea to adopt an MVC (model-view-controller) architecture. However, depending on the flexibility vs performance requirements of your application, there are a vast number of possibilities in implementation.
If performance is key, then use MVC to separate your Gnome and KDE code based on some compiler flags.
If flexibility is key (and this is more my area of expertise) then package the application into CORBA or EJB components. This will allow you to select from multiple GUI interfaces (standalone, applet, or HTML) depending on the client type or location. The cool part is that you can use them all interchangably and/or at the same time.
Slashdot Mirror
What ever happened to "Transaction Authority Markup Language (XAML)"?
It would appear that the xaml.org website is no longer online.
What's with the general disdain for Java here? It seems as though some Slashdotters are always looking for a reason to slam Java (FYI, Java != Sun's implementation of Java).
Ok, maybe Java's not totally free, but neither are you and I. It's free enough, and an excellent platform for enterprise application development. I can't think of another language that gives me the productivity and yet preserves flexibility of platform and vendor (well, except maybe Perl).
I recently noticed that while linking up a new XP machine with my Win2k laptop via a crossover cable, that the XP home networking wizard 'required' the user to make a setup floppy that needed to be installed on all non-XP machines on the home LAN (not sure why).
My laptop doesn't have a floppy, but I was able to just fiddle with TCP/IP settings. Somehow I doubt that your average end user would be able to manage that though.
Amazingly, I haven't seen any mention of Jakarta, an all-Java project of the Apache Software Foundation (ASF).
Here's my list...
Nice to see a book that pulls together several of the great OpenSource development tools that are out there. I've often thought that with enough time and effort, one could put together a truly amazing development system with nothing but OSS and elbow grease. Unfortunately, I've only been able to really internalize Ant and CVS so far. Imagine a well integrated suite of the following...
Bugzilla
;)
NetBeans
ArgoUML
JRefactory
JUnit
Ant
CVS
Tomcat
JBoss
Linux
...and of course a little Perl to glue it all together.
The guy is an admitted sensationalist...
"I purposely went a little over the top just to test the water." (second sentence of second paragraph)
...so take it for what it's worth.
I agree that under current law the guy doesn't seem to have much of a case, since the information was publicly available at city offices. But expectations about access to information are rising and this will soon seem like an unreasonable burden on the public. Why should I have to take a day off work to spend at the county office, photocopying every code I might concievably need, instead of quickly looking up what I need to know on the Internet in the evenings when I need it. At the very least, local governments should require the the copyright holder to allow city offices to maintain the information online. I'm sure they could still manage to sell a few copies of the hardcover version.
Bottom line is that if I want to give away
my intellectual property for the greater good,
that's my business. Our constitution mandates
freedom and democracy, not capitalism.
No matter what you do it would be a good idea to adopt an MVC (model-view-controller) architecture. However, depending on the flexibility vs performance requirements of your application, there are a vast number of possibilities in implementation.
If performance is key, then use MVC to separate your Gnome and KDE code based on some compiler flags.
If flexibility is key (and this is more my area of expertise) then package the application into CORBA or EJB components. This will allow you to select from multiple GUI interfaces (standalone, applet, or HTML) depending on the client type or location. The cool part is that you can use them all interchangably and/or at the same time.
Personally, I vote for a JCalendar...