The Focus of Technology Moves To People With Bathroom Tissue.
Bathroom Tissue Represents Best Practices.
Bathroom Tissue Has Excellent Feng Shui.
Quality Is Maximized, Waste Is Minimized.
Bathroom Tissue Has A Ballistic Trajectory.
Certainly there are other reasons why Bathroom Tissue is important and you're welcome to list them here, but I think this captures the central vision in a way that most anyone who craps can grasp and access.
BTW, I will also use this moment to state that Bathroom Tissue is a terrible name for this new vision of paper-based people-centric product. Except that is for every other name we have at the moment (for example, like "next generation of the arsewipe"). So I will continue to use Bathroom Tissue until something better comes along.
OK, don't agree? Please straighten me out. Why does bathroom tissue matter (or not) to you?
Well said. Another option is substituting capital for labor. This can be done in a number of ways for software development and IT, among them:
Increase developer productivity by buying them faster machines.
Always attempt to solve performance and scaling problems with more hardware. Don't give programmers an optimization problem unless more hardware completely fails to improve the situation.
Don't attempt to fix any problem where hardware is or is suspected to be the problem. Replace the hardware.
Don't attempt to fix any software problem that could be solved by replacing the hardware (OS borked -- throw out the whole machine).
Pay a premium for hardware with better reliability.
A quick search turned up this paper on the economics of IT with a section on capital-labor substitution.
LimeWire is open source and is safe.
I did a quick check of several other open source P2P apps (BitTorrent, eMule, Phex, and Shareaza). None are bundled with malware and if they have a license agreement it is only the GPL.
All of the proprietary apps checked are unsafe, and it is well known that others not checked (e.g., Grokster) are also not safe.
Coralized feeds ought to help sites with lots of subscribers. One nice thing about RSS traffic, I suspect, is that it is less bursty than requests for web pages. You can plan for traffic as the number of subscribers to your feed increases vs. your web pages getting/.'d.
Actually Ibiblio is hosting the files on behalf of CC on behalf of the winners. The files are also uploaded to the Internet Archive
herehere and
here. IA has offered to host any CC-licensed content free of charge.
That sounds like a rather lame excuse. I doubt any forums would allow a complete copy&paste of all of the html on that page. It includes html, head, style, and body elements and a doctype declaration, not to mention images. The RDF may be placed anywhere in the page.
Exactly. BTW, check out the Creative Commons tech challenges page. We'd like (many) more folks to build applications like Verify -- but that's just one of many application ideas.
Just because you can't place RDF metadata everywhere you post an article doesn't mean you shouldn't in its canonical location, which presumibly you always link to. I don't see metadata at http://www.goingware.com/tips/legal-downloads.html, nor a button, though the notice you give on that page is perfectly adequate legally (but IANAL).
As a travel site word66 might be more interested in compatibility with Wikitravel. Fortunately both of you are using CC BY-SA.
There has been some demand for CC BY-SA/GFDL compatibility on the cc-licenses mailing list (see last month's archives in particular). We'll see if anything can be done...
Light and Matter has some electronic textbooks freely available under a Creative Commons license.
As the classroom becomes more digital, I predict we'll see a strong move to "courseware" as opposed to simple digital versions of textbooks. One reason (among many) is that courseware is easy to do in the form of "software as service" and thus has little worry about unauthorized copying. But some people are doing courseware that may be freely copied and reused. Check out MIT OpenCourseWare and the Rice Connexions Repository.
Also, why not collaborative creation of textbooks using a Wikipedia model?
I quoted from the beginning of the paper. Further down, it seems that all roads, even "smooth" ones, have small bumps. I think that rather than smooth road they meant "typical US highway". See http://www.osti.gov/hvt/2001-01-2071.pdf.
This article made me think "hey, what about regerative shock absorbers?" Not "natural vibrations", but anyway... it was being studied (PDF), as of 2001 anyway. That paper says that based on experiments, "the average vehicle on the average road driving at 45 mph might be able to recover up to 70% of the power that is needed for such a vehicle to travel on a smooth road at 45 mph". Anyone know of more current research or implementation plans?
Slashdot Mirror
Certainly there are other reasons why Bathroom Tissue is important and you're welcome to list them here, but I think this captures the central vision in a way that most anyone who craps can grasp and access.
BTW, I will also use this moment to state that Bathroom Tissue is a terrible name for this new vision of paper-based people-centric product. Except that is for every other name we have at the moment (for example, like "next generation of the arsewipe"). So I will continue to use Bathroom Tissue until something better comes along.
OK, don't agree? Please straighten me out. Why does bathroom tissue matter (or not) to you?
Toilet paper anyone?
http://ccmixter.org/
Why shouldn't engineers from around the world have an equal chance to compete?
I say let anyone live and work anywhere in the world, and most slashdot commenters should be ashamed.
- Increase developer productivity by buying them faster machines.
- Always attempt to solve performance and scaling problems with more hardware. Don't give programmers an optimization problem unless more hardware completely fails to improve the situation.
- Don't attempt to fix any problem where hardware is or is suspected to be the problem. Replace the hardware.
- Don't attempt to fix any software problem that could be solved by replacing the hardware (OS borked -- throw out the whole machine).
- Pay a premium for hardware with better reliability.
A quick search turned up this paper on the economics of IT with a section on capital-labor substitution.True for any ship, no? The seasteading folks have done some research on rogue waves and how to avoid or defend against them.
I like it. Has potential as a seastead-based business.
LimeWire is open source and is safe. I did a quick check of several other open source P2P apps (BitTorrent, eMule, Phex, and Shareaza). None are bundled with malware and if they have a license agreement it is only the GPL. All of the proprietary apps checked are unsafe, and it is well known that others not checked (e.g., Grokster) are also not safe.
Sounds like pure hyperbole to me. Seems like OS development is inherently pretty decentralized.
http://83.149.90.123.nyud.net:8090/interview_with_ slon.mp3
For two years, the crew lived inside the hermetically enclosed structure, farming for a living. Serendipitously, the crew could not grow enough plant food to support a calorically normal diet. I assume astronaut health is extremely closely monitored, could provide some good data on short term impact of calorie restriction.
Ex: Slashdot RSS via Coral
PHP6? Nah, with Sun involved, the next version will be PHP10 and the version after that PHP10 Platform Standard Edition 50.
CC is interested in desktop metadata developments. See this CC weblog post from a few days ago.
You have another option -- put the RDF in a separate file and reference it with a link tag. See http://creativecommons.org/technology/metadata/ext end#link
Actually Ibiblio is hosting the files on behalf of CC on behalf of the winners. The files are also uploaded to the Internet Archive here here and here. IA has offered to host any CC-licensed content free of charge.
LINKing to RDF is an option, but there are reasons it isn't CC's recommended method. See http://creativecommons.org/technology/metadata/ext end#html.
That sounds like a rather lame excuse. I doubt any forums would allow a complete copy&paste of all of the html on that page. It includes html, head, style, and body elements and a doctype declaration, not to mention images. The RDF may be placed anywhere in the page.
Exactly. BTW, check out the Creative Commons tech challenges page. We'd like (many) more folks to build applications like Verify -- but that's just one of many application ideas.
Just because you can't place RDF metadata everywhere you post an article doesn't mean you shouldn't in its canonical location, which presumibly you always link to. I don't see metadata at http://www.goingware.com/tips/legal-downloads.html , nor a button, though the notice you give on that page is perfectly adequate legally (but IANAL).
There has been some demand for CC BY-SA/GFDL compatibility on the cc-licenses mailing list (see last month's archives in particular). We'll see if anything can be done...
Replying to myself -- I should've searched before posting. Wikibooks does exist.
As the classroom becomes more digital, I predict we'll see a strong move to "courseware" as opposed to simple digital versions of textbooks. One reason (among many) is that courseware is easy to do in the form of "software as service" and thus has little worry about unauthorized copying. But some people are doing courseware that may be freely copied and reused. Check out MIT OpenCourseWare and the Rice Connexions Repository.
Also, why not collaborative creation of textbooks using a Wikipedia model?
"1491", an intriguing article in the Atlantic magazine last year claims this may be so.
I quoted from the beginning of the paper. Further down, it seems that all roads, even "smooth" ones, have small bumps. I think that rather than smooth road they meant "typical US highway". See http://www.osti.gov/hvt/2001-01-2071.pdf.
This article made me think "hey, what about regerative shock absorbers?" Not "natural vibrations", but anyway ... it was being studied (PDF), as of 2001 anyway. That paper says that based on experiments, "the average vehicle on the average road driving at 45 mph might be able to recover up to 70% of the power that is needed for such a vehicle to travel on a smooth road at 45 mph". Anyone know of more current research or implementation plans?