Views
- State: visible
stuff
Up one levelAll stuff goes here.
-
Do You Want To Remain A Sharecropper?
-
Laws of Software Complexity
-
A Critique of One Hot J2EE Book
-
Multiface Coding in J2EE
-
Why Can't Locking Be Abstracted Away?
-
Manageability Reloaded!
-
Thou Shalt Not Inherit
-
The Most Scalable EJB Idiom
-
Corporate Open Source Repositories You Never Knew Existed
-
Reuse Via String Substitution
-
Rules of Acquisition Must Be Declared
-
A Monopoly Creates Less Jobs
-
Like Eliminating Half The Autos
-
The Fallacies of Inheritance
-
Enhanced EJB Architecture
-
Taxonomy Of Object Composition
-
Pair Programming With Yourself!
-
Is .NET A Gateway To Go Offshore?
-
The Growing Market Of Microsoft To Java Migration Tools
-
AspectWerkz's Replacement Libraries
-
The Excruciating Slow Pace of XML Standardization
-
JBI Deals With the Heterogenous Network
-
Loose Coupling and Mediation
-
Why Document Passing is Loosely Coupled
-
Dataflow and Query Processing
-
Have Web Services Companies Self-Willed a Market into Existence?
-
SOAP, OSI Layer 6 and Aspect Oriented Programming
-
SOA and Accessor Methods Don't Mix
-
Components are Like Runtime Classes
-
Weblogic Workshop's Asynchronous Components
-
Assess Your Software Process Ignorance Quotient
-
Open Source Rule Engines Written In Java
-
Fallacies of a Perfect Computing World
-
Open Source Workflow Engines Written in Java
- A review of active open source workflow projects that are written in Java.
-
Is JetBrains Selling Arms to the Enemy?
-
Open Source Portal Servers Written in Java
- A list of "open source" portal servers written in Java.
-
Checker Shadow Illusion
- A light check in the shadow is the same gray as a dark check outside the shadow. From http://www-bcs.mit.edu/people/adelson/illusions_demos.html
-
Lightness Illusions
-
Temporal Anomalies In Movies Explained
-
What If Schemas Didn't Exist?
-
The Mind Electric takes over WebMethods
-
Counter Intuitive Rules for Software Success
-
The Swing Connection Reloaded
-
Why Is Microsoft Interested In C++?
-
Text Makes a Powerful Comeback!
-
Novel Open Source Template Engines Written In Java
-
Why Can't Microsoft Deliver 64-Bit .NET?
-
Eclipse Must Be Truly Rich!
-
Open Source Identity Management Solutions Written in Java
-
Open Source Knowledge Management Solutions Written in Java
-
Rendezvous Enabled Distributed Build!
-
How To Build The Ideal Content Management System
-
Non Viral Open Source XQuery Written In Java
-
Open Source EAI Written In Java
-
Open Source Agent Systems Written In Java
-
Has Java Reached The Inefficiency Phase?
-
Is Longhorn All Bull or Full of Holes?
-
The Story Of Jython
-
The Economics of Google's Hardware Infrastructure
-
Open Source Structured Graphics Libraries Written in Java
-
Open Source Graph or Network Visualization Written in Java
-
Google Deskbar Forges A New Desktop Paradigm
-
Clay Shirky Predicts the Demise of The Semantic Web
-
Open Source Full Text Search Engines Written In Java
-
How Much Faster is Java on a 64 Bit AMD Opteron?
-
Open Source Distributed Cache Solutions Written in Java
-
Open Source LOAF Written in Java
-
Obfuscated LOAF
- Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications. Definitions "Package" refers to the collection of files distributed by the Copyright Holder, and derivatives of that collection of files created through textual modification. "Standard Version" refers to such a Package if it has not been modified, or has been modified in accordance with the wishes of the Copyright Holder as specified below. "Copyright Holder" is whoever is named in the copyright or copyrights for the package. "You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.) "Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions they received it. You may make and give away verbatim copies of the source form of the Standard Version of this Package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. You may apply bug fixes, portability fixes and other modifications derived from the Public Domain or from the Copyright Holder. A Package modified in such a way shall still be considered the Standard Version. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following: place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. use the modified Package only within your corporation or organization. rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version. make other distribution arrangements with the Copyright Holder. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following: distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version. accompany the distribution with the machine-readable source of the Package with your modifications. give non-standard executables non-standard names, and clearly document the differences in manual pages (or equivalent), together with instructions on where to get the Standard Version. make other distribution arrangements with the Copyright Holder. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. You may embed this Package's interpreter within an executable of yours (by linking); this shall be construed as a mere form of aggregation, provided that the complete Standard Version of the interpreter is so embedded. The scripts and library files supplied as input to or produced as output from the programs of this Package do not automatically fall under the copyright of this Package, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this Package. If such scripts or library files are aggregated with this Package via the so-called "undump" or "unexec" methods of producing a binary executable image, then distribution of such an image shall neither be construed as a distribution of this Package nor shall it fall under the restrictions of Paragraphs 3 and 4, provided that you do not represent such an executable image as a Standard Version of this Package. C subroutines (or comparably compiled subroutines in other languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this Package shall not be considered part of this Package, but are the equivalent of input as in Paragraph 6, provided these subroutines do not change the language in any way that would cause it to fail the regression tests for the language. Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. The End
-
How to Choose an Open Source Library
-
Isn't It a Bit Too Early for Eclipse Vendor Consolidation?
-
Java Jobs Statistics and Trends
-
Loosely Coupled Java Based Languages
-
The Exception Debate: Why Gosling and Hejlsberg are Both In Error
-
The Elevator Pitch for Web Based Continuations
-
The Secret World of Exception Handling Frameworks
-
Quick Take on the Pi Calculus
-
Ulterior Motive Behind BEA and IBM Joint Spec?
-
Encapsulation and Representation are Orthogonal
-
Holy Omniscient Debugging!
-
Eclipse Embeds OSGi Based MicroKernel
-
How to Automagically Make the Technorati 100
-
The 13th Guy Illusion
-
Strings, Algebraic Datatypes and Quasi Quotes
-
A Definition of "Services"
-
Open Source Under The Microscope
-
Open Source Profilers for Java
-
13 Exceptional Exception Handling Techniques
-
The 8 Laws of Software Evolution
-
Open Source Automated Test Tools Written in Java
-
Anemic Domain Model and SOA
-
Open Source Web Crawlers Written in Java
-
Is there a Preferred Axis for Loose Coupled-ness?
-
101 Reasons Why Java is Better than .NET (Reloaded)
-
WebServices' Greatest Achilles Heel
-
Easy To Remember URL For 101 Reasons Why Java Is Bettter
-
J2EE Clustering Without An Operating System
-
First Steps Toward A Dirt Cheap Terabyte Server
-
What Happens When You Have A Terabyte Of Personal Storage?
-
Can't Be A Respectable Java Developer Without One Of These!
-
Open Source PageFlow (a.k.a. State Machine) Written In Java
-
Most Valuable Personalities in Java
-
Open Source Manageability For My Sony Ericsson T610 Phone
-
Will The Lightweight Container Best The MicroKernel AppServer?
-
Lazy Evaluation And Object Composition
-
How Do You Know That You Are Not Leaking Money?
-
What's This? An Embeddable REST Microkernel!
-
Infoworld Says Manageability Missing In Java Desktop
-
Continuing Review of a REST Based Microkernel
-
A Theory of Patches
-
High Time For A New Kind Of Computer Science
-
The Next Thing After Java Technology
-
XML Fallacies Revealed
-
Why Object Oriented Encapsulation is Obsolete
-
The Eclipse Juggernaut Moves On (Part 2)
-
Why Class Based Domain Modeling Does Not Work
-
Open Source XML Diff Written in Java
-
How Many Java Web Frameworks Can You Name?
-
Text Files Unfairly Compared To The Internal Combustion Engine
-
Integration at the Glass and the 80/20 Point
-
5 Rules of Model View Separation
-
Another Crack At Bookmark Manageability
-
Open Source Personal Proxy Servers Written In Java
-
Scala The Groovy Killer?
-
Mildly Complex Webapp in 2 Man Months!?
-
"Showcase" Applications For Java Web Frameworks
-
Is Over Abstraction Java's Achilles Heel?
-
Even More Wisdom on Designing Usable APIs
-
Usable APIs: Dependency Injection, Failure Strategies, Duck Typing and REST
-
Design Patterns Periodic Table
-
Resign Patterns: Ailments of Unsuitable Project-Disoriented Software
-
HTML Screen Scraping Tools Written in Java
-
Loose Coupling and its connection to Robustness
-
Is Quick And Dirty Good Enough?
-
Six Operators of Modularity
-
Modularity and the Conservation of Profits
-
Questioning Meyer's Definition of Modularity
-
Open Source Projects That Use Java NIO
-
Open Source Probabilistic Networks Written In Java
-
Open Source Java Collections API Extensions
-
Six Sigma and The Knowledge Based Economy
-
Loosely Coupled Dimensions [Updated]
-
Prototype Based Programming Makes A Comeback!
-
Why Pessimistic Transactions Aren't Practical
-
Contracts and Interaction Operators
-
Transactions and SOA
-
Gavin King Torpedoes JDO!
-
Why IT Doesn't Matter Rebutted
-
Why Time Travel is a Necessity
-
Uniformity and Recombinant Computing
-
Tuple Spaces for Human Interaction
-
Coupling Stuff from Pragmatic Programmers
-
A Couple of Pragmatic Uses of AOP
-
Free Google GMail Account For The Lucky Reader
-
Compatibility and Evolution in an Asynchronous World
-
The Importance Of "Requires"
-
The Trouble with Evolving XML Schemas
-
XML Schema is a Case of Premature Optimization
-
How To Achieve Flexible XML Messaging
-
Don't Dismiss Structure Shyness
-
Nuggets of Wisdom from eBay's Architecture
-
Are Abstraction Layers in Messaging Necessary?
-
The RESTfulness of Speech Acts
-
The Imminent Rise of REST and Fall of SOAP
-
When To Choose Code Generation Over Reflection
-
Google Enabled Search at Manageability
-
Requirements Without Measurement Are Nothing More Than Utterances
-
Ten Fallacies of Software Analysis and Design
-
The Honest Truth: EJB Is Your Scapegoat
-
Top Ten Truly Obscure But Useful Java Projects - Circa 2004
-
Open Source JMS (Java Message Service) Implementations
-
Open Source JDBC Proxy Drivers
-
Rod Johnson on J2EE Without EJB
-
The Architecture of Participation
-
Open Source ETL (Extraction, Transform, Load) Written in Java
-
The Architecture of Participation versus Hacking
-
Killer "Slicing and Dicing" Eclipse Plugins
-
Deconstructing Dependency Injection
-
Java Unbound
-
Open Source Microsoft Project Alternative Released
-
How to Distinguish Configuration from Code
-
Configuration using Aspects
-
One Million and Counting
-
Groovy and Del.icio.us
-
Home UPnP Media Servers Not Ready for Prime Time
-
How To Be A True Republican
-
What Works? Repetition or Silence?
-
Open Source Document Management Solutions Written in Java
-
Google Desktop Internals Exposed!
-
High Time to Get Rid of the Stack
-
The Conceptual Underpinnings of JotSpot
-
Surprise! Creator of Minix is the VoteMaster!
-
Simplicity Trumps Complex Analysis
-
Microsoft's Standardized Verb Set
-
Manageability at Yahoo's Tech Tuesday