Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Good luck not doing that (Score 1) 292

Because Amazon does not publish information about that format, there is exactly one tool that is known to generate this format in a guaranteed forward-compatible way. That tool, kindlegen, was written by Amazon, and the licensing terms from 2.0 onwards (the first version to support nontrivial formatting) do not allow you to use it for creating content that is sold outside Amazon's store. So in order to distribute content elsewhere, you have to either...

Although I haven't used the tool myself, Amazon's description says that "KindleGen is a command line tool which enables publishers to work in an automated environment with a variety of source content including HTML, XHTML or EPUB." So unless there is something more to the licensing terms than you're suggesting, there shouldn't be any problem with creating your content in an open format, and then using KindleGen to generate the content for the Amazon store.

Submission + - The Magic of Pallets

HughPickens.com writes: Jacob Hodes writes in Cabinet Magazine that there are approximately two billion wooden shipping pallets in the holds of tractor-trailers in the United States transporting Honey Nut Cheerios and oysters and penicillin and just about any other product you can think of. According to Hodes the magic of pallets is the magic of abstraction. "Take any object you like, pile it onto a pallet, and it becomes, simply, a “unit load”—standardized, cubical, and ideally suited to being scooped up by the tines of a forklift. This allows your Cheerios and your oysters to be whisked through the supply chain with great efficiency; the gains are so impressive, in fact, that many experts consider the pallet to be the most important materials-handling innovation of the twentieth century." Although the technology was in place by the mid-1920s, pallets didn’t see widespread adoption until World War II, when the challenge of keeping eight million G.I.s supplied—“the most enormous single task of distribution ever accomplished anywhere,” according to one historian—gave new urgency to the science of materials handling. "The pallet really made it possible for us to fight a war on two fronts the way that we did." It would have been impossible to supply military forces in both the European and Pacific theaters if logistics operations had been limited to manual labor and hand-loading cargo.

To get a sense of the productivity gains that were achieved, consider the time it took to unload a boxcar before the advent of pallets. “According to an article in a 1931 railway trade magazine, three days were required to unload a boxcar containing 13,000 cases of unpalletized canned goods. When the same amount of goods was loaded into the boxcar on pallets or skids, the identical task took only four hours.” Pallets, of course, are merely one cog in the global machine for moving things and while shipping containers have had their due, the humble pallet is arguably "the single most important object in the global economy."

Comment Re:Case insensitive file systems were a bug (Score 1) 148

Sorry - if the tools that we have for managing the labels that humans wish to place on their objects are lacking, we should fix the tools, not the labels. For example, I've named my dog "Crankshaft" - does that confuse mechanics? The only thing we humans have is the ability to manipulate symbols. I'd prefer to have no restrictions on the labels that I use, since they simply refer to objects.

It's a common problem in the programming field to make a virtue out of overgeneralization, even when it conflicts with other virtues, such as ease of use or security. What actual benefit do you get from allowing the inclusion of control characters in filenames? How does that benefit compare with the amount of pain and extra effort involved in dealing with those filenames?

The other thing is that "fixing the tools" is a complete non-starter. You're talking about "fixing" a large subset -- possibly even a majority -- of programs on Unix systems, in a way that will be incompatible with existing tools. The elegance of putting some minor restrictions on filenames into the filesystem is that it works with virtually all existing user-level software, with no changes to that software required.

Comment Re:Established science CANNOT BE QUESTIONED! (Score 1) 719

In other words, one group of "skeptics" has appointed themselves to be the gatekeepers of the definition of skepticism, and is now throwing a tantrum because there are other people using term that don't match the definition that this group came up with.

If this "Committee for Skeptical Inquiry" is worried that they'll be confused with the climate-change skeptics, then they need to come up with another term for themselves. Demanding that the English language change to suit their own preferences is stupid, and the only reason why it's getting any support here on Slashdot is because of the personal animosity that most of us have towards the climate-change skeptics.

And yes, I'm going to purposefully use the term "climate-change skeptics" from now on.

Comment Re:Case insensitive file systems were a bug (Score 4, Insightful) 148

A quick glance at that article seems more like a compelling case for teaching people how to write shell scripts properly.

If you read the article, you'll find that writing shell scripts to handle filenames containing every possible character "properly" is so difficult that virtually everyone gets it wrong. When something's been around for close to 40 years and still nobody can get it right, maybe it's time to admit that it's the tool that's broken.

Comment Re:Case insensitive file systems were a bug (Score 4, Informative) 148

Obviously every character except for the path separator and the string terminator should be valid. Why should the file system restrict what character encoding I want to use for my names other than restrictions that simply make implementation easier.

This article makes a pretty convincing case that we'd be better off with some restrictions on filenames. It's hard to argue the point that allowing certain characters in filenames causes more problems than it solves.

Comment Re:What? (Score 1) 440

The context of this discussion is that TechyImmigrant claimed that someone who would support deporting an illegal immigrant "has something against immigrants." So TechyImmigrant was equating the two. I simply pointed out that doing that is dishonest.

I have several reasons for being against illegal immigration while not being against legal immigration. I did not expound on them in my post, as they were not relevant to the point I was making, but I still see no reason why you should immediately jump to the conclusion that those reasons do not exist.

Comment Re:I bet... (Score 1) 448

And do you make the same bet that women commit the same crimes as men, or youth as elderly?

Men and women from the same culture and class demonstrate very different behavior, as do young and old people. I have never seen any evidence to support the notion that there are significant behavioral differences associated with skin color. If you've got some evidence that shows that black people are more likely to commit crimes than white people that were raised the same way, I'd love to see it.

Comment Diary entry from 2150 (Score 1) 440

Told kid about nano-cam dust today. He's only 4 years old, so he didn't know about them yet, and I'm trying to teach him basic hygiene. I explained for that for nearly a a hundred years we have all lived in an environment where other peoples' cameras are always in our homes. We track them in, on our shoes. The AC intake blows them in. The servers the cameras send video too, aren't owned by people who are practicing subterfuge. It's not like they snuck "spy" dust onto our porches in the hopes we'd track them in. It just happens; it's an inevitable consequence of the stuff blowing around everywhere.

My great grandparents complained about it. They thought they had a reasonable expectation of privacy in their homes, because nanotech was new. They didn't see the dust, so they didn't know it was there. In the absence of sensual confirmation, the default expectation (at least to the layman) was that it wasn't there. That was naive, but my grandparents didn't work with nanotech or even use consumer models themselves, so perhaps their ignorance could be forgiven. (Just as my own ignorance of hyperspace can perhaps be forgiven, since I'm not a miner.)

My grandparents, though, grew up with the stuff, though it was still a bit expensive, so it wasn't totally ubiquitous yet. By their time, almost everyone at least knew about it, and if in a gathering of any five people you were to say "nobody sees me inside my home," chances were there would have been a few guffaws and someone would likely point out that the statement was likely incorrect. Sometimes the stuff got innocently tracked into your house, and sometimes it was manipulated into getting there, through subterfuge. The law and social norms lagged, though, and people debated privacy a lot.

By the time their children (my parents) grew up, though, it was all over. Everyone knew about nano-cam dust, and unless you did a rad-flash a few minutes earlier, fucking in your own bed was just as public as doing it in Times Square.

And now my kid knows too. It's just something everyone is expected to know about and deal with. If I were to write a story about it, I think I would set the story in the time of my grandparents, back when society was truly conflicted and in the midst of change. I bet those were interesting times.

Slashdot Top Deals

Anyone can make an omelet with eggs. The trick is to make one with none.

Working...