Follow Slashdot stories on Twitter


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Designed in the US, produced elsewhere (Score 1) 72

Ok, we design things in California.

Often that design process is that a US company contacts a design company in Taiwan, which produces a bespoke design for which the real designer will not claim rights to. It's then "Designed in the USA", because someone in the US approved and paid for the design.

Comment Re:The current system is stupid. (Score 1) 171

No, that won't work. Changes may have taken place in-between the two copies of robots.txt.

An example: A newspaper.
At the first fetch of robots.txt, an article might not exist. The first version of it has not yet been verified, and is published with a new robots.txt that tells robots not to crawl it. Then, the article is modified and verified, and a new robots.txt published that now allows crawling it.
Yet, a spider may have caught the first robots.txt from before the article, the article while it was in bad shape, and the second robots.txt from after it was corrected. Both robots.txt files agree that it can be cached, yet the copy that was crawled was never meant for caching, and the robots.txt at the time it was published even said so.

Comment Re:The current system is stupid. (Score 1) 171

The problem with robots.txt is that it doesn't contain a validity period.

Say I add mustnotbecrawled.html, a link to it in existingpage.html, and a modification to /robots.txt that bans crawling of mustnotbecrawled.html. The problem is that a robot might have downloaded robots.txt right before my publishing, and does not see that it shouldn't crawl it. So it does.

It could be argued that a crawler should always re-load robots.txt if encountering a document newer than the last server transmit time for robots.txt, but that adds a lot of extra requests.

Some propose using the meta tag for excluding browsers, but that has its own problems. Like only working for XML type documents. And being applied after the fact. If I have a several megabytes HTML, and want to exclude it to save bandwidth, the meta tag won't work. It adds a little bit extra bandwidth.

I think this should be handled at user-agent level, where crawlers identify themselves as a crawler, and the web server can make the decision on whether to serve them based on that.

Comment Re:Pretty obvious (Score 0) 382

Let's take a far simpler feature example, like when the tar utility added the xz compression flag -J. It didn't ruin everyone's work-flows.

By the time of -J, the damage had already been done. When tar gained the ability to compress/decompress with -z, it broke compatibility for a long time until bugs were fixed, as well as opened for a new generation of scripts that no longer used multi-threaded compression (like pigz) but instead sent everything through a single bottleneck, greatly increasing runtime on multicore systems, and blocking on slow IO systems (including, ironically, tapes, which tape archive was made for). tar using compression internally might be the most common reason for processes being in D state long enough to be observed.
It's a prime example of something that should have been left well enough alone. It did not solve any real problems.

Comment Re:Becaue you aren't offering to do the work. (Score 1) 382

Isn't that just an unnecessarily complex way to say "right"?

No, wrongness is a scale between dead right and dead wrong, and comprises all possible degrees between the two, including slightly wrong, mostly wrong and almost completely wrong.

Then, there's "not even wrong", which is in a class by itself.

Comment Re:Becaue you aren't offering to do the work. (Score 4, Informative) 382

Just FYI, "Static Friction"== inertia

No, it isn't. You're almost precisely wrong.
Static friction is a threshold that has to be overcome before inertia becomes a factor, and includes Van der Waal forces, electrostatic forces and surface bonding. When you carefully walk up or drive down an icy hill, static friction is what prevents you from sliding. But once you start sliding, inertia is what prevents static friction from winning, even when you reach the bottom of the hill.

Comment Re:Pretty obvious (Score 2) 382

All too often people suggest adding something that's not relevant to the application, is already there, or just wouldn't be useful.

Or, in the Unix/Linux world, functionality that's already well covered by existing tools, and adding it will only introduce incompatibilities and a subset of what the dedicated tools already do.
Examples include editors that won't do calls to standard commands like sort, date and sendmail, but instead implement their own limited versions that bloat the code, lack functionality, and introduce bugs.

Too many programs try to include the kitchen sink. I don't want that. I want tools that do just one thing, but do it exceedingly well. A spork with built-in flashlight is not what you should aim for.

Comment Re:In other words... (Score 1) 438

You seem to be making the mistake recruiters are these days and assuming that if someone isn't a carbon copy of a current employee (good luck finding that) they're unhireable. I'd argue this erroneous assumption is the cause of most unemployment today.

No, I make the mistake of believing that there are people out there that can figure things out without having all their food chewed for them. Too often i get disappointed.

Slashdot Top Deals

"Catch a wave and you're sitting on top of the world." - The Beach Boys