Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Comment Re:Not a problem here (Score 2) 322

Selfishness? No, Selfishness is having too many kids, it's rather selfless to not reproduce.

Selfishness is not having kids but expecting that you're going to be cared for by other peoples kids. It's selfishness when it's done by the individual, and it's selfish when it's done as an "immigration" policy. Face it. We, as a culture, transformed sex into a sport, and now we survive by stealing other peoples children. It's worst in North America... this continent is where genetic material comes to die.

Comment Re:Stupid (Score 1) 356

Also answering to your followup post.

If someone downloads my code, uses it without my license, then he is not my customer. Also if my not customer "sells" it to another person, that person still is not my customer (your used car/manufactor example)

Picking random lawsuits does not suit you. (Except you are a lawyer).

What the supreeme court decides is irrelevant: for 80% of the planets population.

It is common sense that a manufactor is liable for flaws in his car regardless if it is resold as a used car.

Regarding your example in the make file: sorry, a make file has legitimated uses of the "rm" command.

So having me putting one into it makes me not liable beyond doing it with "intent".

On top of that, a makefile runs with the users permissioins, it is close to impossible that it ruins any data of "the customer".

And don't forget: he is supposed to have back ups. I'm notliable that my script deletes a file of him and he has no back up to restore it.

Those liability disclaimers are just bollocks.

What you think such a disclaimer is worth in a european court?

I buy a software from e.g. Apple and they have a disclaimer: "uh oh, we don't warrant that this software is usefull for any purpose!"? Rofl, for what exactly am I paying then? What is the damage if I "pirate" the software?

A disclaimer does not shield you from liability if I can proof that your mistake was a serious overight (and not a simple mistake) or was intention.

Not having a disclaimer does not change much, I still have to proof that you damaged me by intention. And if I use your software for free, it is completely my own fault, regardless of license or not.

Comment New information vs expectations (Score 2) 214

Everyone knew this case was at the SCOTUS, and everyone knew that patenting something that occurs naturally was not what patent law was supposed to do.

There is NEVER certainty regarding a SCOTUS ruling. Expectations cover a spectrum and not everyone makes the same bet. SCOTUS could have ruled in such a way that this company lost their patent protection altogether which appears to not have happened. Just because what you outlined is the most likely outcome does not mean it is the only possible outcome. Some people were clearly betting on other, more pessimistic, outcomes than the one that actually occurred. It's pretty much the same thing as betting on the long shot in a horse race instead of betting on the favorite. The odds are against you but if you are right the profit is much higher.

Stocks usually move at new information, not at confirmation of old information.

The SCOTUS ruling IS new information. Prior to the decision there were expectations regarding the ruling but it could not be treated as a certainty.

Comment Re:Creation vs Reality (Score 1) 434

A well written book will can transport me (and let me admit here that I own a literary agency, and am the son of one of the golden age SF writers, a hugo, and other, award winner... I know at least a little bit about well written books.)

Yes, when I'm reading a well written story I'm transported to a different place as well. I feel sorry for those who don't read.

I'm also compelled to remind you that the real world disagrees with your perception.

Perception can never match reality, it's far too complex and we're far too simple.

I should send you a copy of Nobots when it's done (what's online is a crappy error-filled first rough draft).

Comment Re:No shit (Score 1) 286

It wasn't that driving while on the phone was worse than drunk driving, but that it was as dangerous. The difference is when you're drunk, you're drunk from when you start the trip until after you get there. With a phone you're only dangerous for the part of the trip you're on the phone. Plus, someone drunk is less likely to be wearing a seat belt than if they were sober.

Comment Markets are chaotic and (usually) rational (Score 3, Informative) 214

Ah yes. Thanks. I keep trying to apply rationality to the stock market.

It is extremely rational behavior. Think of it like playing a poker hand. You have imperfect information so you make your bets based on the likelihoods of various results. Some results are more likely that others and you play accordingly. As more information becomes available your betting strategy may change. That is exactly what is happening here.

One has to understand what is driving prices for the stock market to make any sense. Information about company performance is at the core but it is NOT what drives prices. There is no direct link between a company's financial performance and their stock price. What drives prices is peoples expectations and in some cases people's expectations about other people's expectations. (and even expectations about expectations about expectations... you can keep going) If you invest in the stock market you are placing a bet not so much on what a company will do but on what other people will think about the company. When you buy IBM stock you are saying in essence "I expect more people to find this valuable in the future". Any secondary market (stocks, baseball cards, tulips, real estate, etc) works this way. It's shockingly rational (with some exceptions) but highly chaotic and thus hard to predict.

Comment Re:Apple Puckery (Score 1) 262

You couldn't be more wrong. They do not use the legacy file system as you know it. They use a task specific file system. It's evident in every aspect of iCloud, and iTunes.

You're bewildered. The device uses a filesystem just as we know it. The user doesn't get to see it, but it is there. Additionally, there's a filesystem exposed to the user that consists of app-on-desk and/or-app-in-folder; this is horribly broken, but nonetheless allows the user to organize apps in the way that the computing community has long determined to be desirable.

You should ask yourself this: Why are there named user folders in iOS in the first place? There are two obvious reasons: to reduce clutter, and so you can *organize* your apps: games, photography, etc. To argue that organization at the user defined level isn't Apple's goal is ridiculous, that's exactly what the folders have done all along. They just have not done it well. Now that the count limits have been sundered, they'll be better; but you mark my words, these other limits are also impacting the device's ability to do work, and creating one-app-only zones where anything that can be done to a file must be in the one app that owns it, with the notable exception of the photos, where Apple has made the mistake of again creating a unique filesystem for them that doesn't benefit anything else. It is form over function, and it's well known to be the wrong path. Why did it work with iOS at all? Because these devices started out as non-general-purpose computing platforms. But now they're much more powerful, and so they're going to have to come with a general purpose filesystem to complement them. There are several ways to do that, but the current implementation is only a partial image of one of them, and amusingly in the case of your arguing position, it's a limited version of the bog-standard computer filesystem we're all familiar with.

You see the files specific to the task you are working on.

No. You don't. That's part of the problem. If I have a text file, there should be all manner of apps that might have business with that file. Text editors. Log viewers. Spellcheckers. Many more. But because the paradigm is primarily app-owns-file, this sharing is crippled. You can't use the synergy of multiple apps to work on files, and that shoots the device, and the user, right in the foot. If, on the other hand, one could organize one's data and access it via that organization, without relying on a broken idea of app-owns-document, then that synergy would be brought up to the level of a modern computer system. It's a failed, crippled vision and Apple has already begun to revise it with iOS 7. Further, not only should apps be able to see whatever files you want them to, you should be able to put one swatch of (for instance) text files in one folder, related to one task, and another swatch for another task in another folder. This prevents you from having to wade through every file for every task that you ever did.

I'm not looking at it from the perspective of a "geek", as you wrongly assume, or the least bit concerned about multiple shells, etc.; I'm looking at it from the perspective of a business owner for whom the functionality of iOS falls far short of what I need just with conventional file management for mundane, non-geeky files. Would geeks benefit from such changes? Sure. Would the left side of the Gaussian be bewildered and lost? Unlikely. The existence of the ability to create subfolders does not have to be used. The search facility is still there, much like Spotlight exists on OSX. You *can* use such a system like a drooling idiot; but it makes no sense whatsoever to limit everyone to that status.

Imagine the iOS device after years of use. Full of files, many perhaps of the same name. You search for "mom" but there are 40 instances. Which one is the one you want? Without folder organization, how can you tell? This is just one of the obvious pitfalls. We need date; we need organizational context; we need sharing among apps for all files; we need limits lifted and tree structured folders implemented. And it's going to happen or Apple will be left behind. Mark my words, I've been watching computers since the 70's and there's just no way going back that far is the way to go.

Comment The market works on expectations (Score 4, Interesting) 214

Oddly, Myriad Genetics stock actually rose on that information.

That's not really surprising. All that means is that the market expected the news to be worse than it actually was. Once the ruling was handed down and the uncertainty removed, the stock rebounds based on the new information. You'll see this all the time where a company has a terrible quarter and their stock price goes up because while it was indeed terrible, it wasn't as terrible as expected.

Comment Re:Apple Puckery (Score 1) 262

The file system is not revealed at all.

Wrong. The apps on desk, apps in folders functionality IS a filesystem. It's broken, and stupid, but it's still a filesystem. There's a perfectly good filesystem within the context of the actual OS -- it couldn't run without one -- but the user has their own. Apple partially addressed their mistakes with iOS 7, allowing many items in a folder (finally) and I expect they'll allow subfolders next time around as people continue to demand them. It's entirely irrelevant if they expose *the* filesystem, the point was, the unit USES a filesystem, and the user needs A filesystem; the apps=on-desk and/or-in-folder functionality IS, in fact, A filesystem, albeit a crippled and pitiful one. Apple will either up the iPad's game to be more capable or it will be left in the dust as this class of devices becomes more powerful overall. People on the right side of the Gaussian are interested in doing real work on these tablets (and perhaps even on the phones.) You can't do that until applications can work in synergy, apps don't have to reinvent every feature in order to make use of it, apps can share data, there's a reasonable way to organize both apps *and* data, and limits on folder content count are lifted (and as I said, Apple's already addressing the fact that they screwed that up badly.)

When I download or create a file, I need to be able to get at it with all of the apps that can deal with it. I need to be able to put it somewhere so that I can find it again with minimal effort -- and no, that doesn't mean typing its name into a search box -- it means "tap."

You'll see. Apple's stuck in the 1970s. Back then, we looked at, and tried, no folders, and limited file counts. We got past that as fast as we could, because it sucks. Apple's always had a problem with form over function; the mac mini is an example where they realized it and fixed it. The new Mac Pro and the filesystem exposed to the user in iOS are two areas you'll see change in rather short order now.

Comment Re:Silver Bullet (Score 1) 172

I found write performance hit a huge wall once the things started filling up. Perfect to kb/s in an instant and then getting stuck at that speed, and of course since an erase is a write recovery from that state took ages. The answer I suppose is to not let them get anywhere near full - where that point is will undoubtedly vary by model based on their internal controllers. I can't recall where it fell over but I think it was still under 90% with one set of SSDs.
I replaced them with spinning storage and people were happy, but that was something that didn't need a lot of file operations per second.

Slashdot Top Deals

Executive ability is deciding quickly and getting somebody else to do the work. -- John G. Pollard