The ability to create decoupled software components , combine them into a coherent, functional application, and deploy them into a standards-based container (i.e., an "application server") is a HUGE step in programmer productivity.
How about modifying the GPL/LGPL (and other) license(s) to prohibit use of software by or in support of the RIAA?
They'd be forced to use all M$-ware and eventually be put out of business by the obscene licensing fees.
Autocaching to mitigate the Slashdot Effect
on
Slash 2.2.0 Released
·
· Score: 1
How about an autocache mechanism that retrieves linked-to pages (with size limits, depth limits, expirations, blah blah) and caches them for some period after the story is posted?
Slashdot Mirror
The ability to create decoupled software components , combine them into a coherent, functional application, and deploy them into a standards-based container (i.e., an "application server") is a HUGE step in programmer productivity.
I've had to use Transl8it on more than one occasion to try to figure out what someone was saying.
So much for the burden of communication resting on the sender, rather than the receiver...
Maybe they should have at least done a Release Candidate...
Just like I have to pay the phone company not to be listed ("linked-to") in the white pages!
How about modifying the GPL/LGPL (and other) license(s) to prohibit use of software by or in support of the RIAA?
They'd be forced to use all M$-ware and eventually be put out of business by the obscene licensing fees.
How about an autocache mechanism that retrieves linked-to pages (with size limits, depth limits, expirations, blah blah) and caches them for some period after the story is posted?