Comment Re:I don't get "smartphones are too expensive" (Score -1) 150
you're a moron.
you're a moron.
I think the copyright laws in the US need reform, but frankly if I were to write a book, I'd like my descendants to benefit for some while.
So sell your book within a reasonable copyright term and give your descendants the money. Problem solved.
Is it centuries old in North Korea?
I'm not really sure why the PC police even care about this. Did they not have a reason to dislike the North Korean government until the government used a term that these people have decided is offensive?
The "training" of exceptional people does not have the same nature as training for other people. Exceptional people train themselves and some help can accelerate the process, but it is not the usual case of a teacher training them.
That is simply not true for other disciplines. Exceptional musicians are trained by teachers. Exceptional athletes have coaches. Exceptional scientists learn their skills from teachers. So again, why do you think programmers are different?
Exceptional people are exceptional because of their obsessive unquenchable interest in a subject. Exceptional people don't need "training", they just need experience, and even without experience, can still be much better than "normals". A lot of training focuses on rules of thumbs, and dumbs down those rules of thumbs to the point of being "written in stone". There are so many things taught as "never do this", when really they mean, "you're too stupid to know when to do this correctly". Training can help, but much of it is a waste of time.
In every other discipline that I can think of, the people who are exceptional in their field have undergone extensive training. Scientists, engineers, musicians, artists, athletes -- the list goes on and on. It takes training for people to reach the potential of their innate ability. Why do you think that programming is somehow different?
...while you can train people to be competent, you can't train them to be exceptional.
Two things:
First off, American companies love programmers that are merely "competent" -- or that don't even meet that standard. That's why jobs keep getting shipped overseas to shops that can hire three incompetent programmers for the cost of one good programmer here in the US. The tech companies' actions speak louder than their words here.
Second, while you might not be able to train everyone to become exceptional, it's safe to say that most people with the ability to become exceptional will not do so without training. Mr. Graham is relying on the argument that the only way to get more exceptional programmers in the US is to import them. That is flat-out not true.
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.
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.
at a cost of roughly a tank of gas in a premium sedan.
Roughly, not exactly. Pegging the price of a battery switch to the price of gas really wouldn't make any sense, although it might make sense to make it based on the cost of electricity in the area, assuming that that varies.
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.
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.
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.
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.
The conventional wisdom that it's political suicide in Florida to support normalization of relations with Cuba just isn't true any longer. 56% of Americans in general support it. That number increases to 62% if you focus only on responses from the Hispanic/Latino community, and it increases to 63% if you just ask people from Florida.
The "angry Scarface extra" demographic in Florida is dying (both metaphorically and literally.) The times, they are a-changing.
New York... when civilization falls apart, remember, we were way ahead of you. - David Letterman