Implementation makes a difference. Early versions of NT were quite good, but unpopular because you needed 16MB of RAM (if I recall correctly) to run them in an era when a high end personal computer shipped with 4MB of RAM. Over the years they tried to hold the line, at one point getting the minimum down to 12MB of RAM, but perhaps not coincidentally stability got really bad.
Yes, publishers and middlemen have all kinds of rationalizations for trying to kill e-books, but calling any of them "legitimate" is shilling so hard you could pence a crown.
All the arguments based on classical economic theory only work if the assumptions of classical economics hold, particularly the assumption that there is a free market.
Amazon is arguing for its freedom to set prices it charges in its ebook store; that would be no concern of the publishers if we lived in a world where ebook users could simply buy books in non-proprietary formats from any Internet storefront they wanted. But we don't live in such a world. We live in a world where most ebook readers are controlled by Amazon and inextricably linked to its store. It wouldn't have been hard for Amazon to build the Kindle that way. Define some public book trading protocols, bootstrap the standard by building those protocols into the Kindle and Amazon's online store, and instantly the world is a better place for everyone except printers and bricks-and-mortar bookstores with no Internet presence. But Amazon didn't do that, because the Kindle is designed to tie the user to Amazon, the way the iPad is designed to tie the user to Apple.
So what we're looking at is a maneuver by Amazon to corner the market on books *in general* by killing off the traditional paper book trade. Preserving the ability to buy most books from someone other than Amazon seems like a legitimate reason to me.
Re:Maybe the author needs to get out more
on
Amazon's eBook Math
·
· Score: 2
No dude, your books are not so incredible that people will buy them no matter what the price.
Nobody's book is so incredible that people would buy them no matter what the price. If my only way to get Shakespeare was to pay a ten thousand dollar license fee I'd find a way to do without.
Authors/publishers/developers/etc need to get over this idea of their digital goods being "worth" a certain amount. No, you need to figure out what you need to do to maximize your profits since there is zero per unit cost. Usually, that is going to mean selling cheap, but selling lots.
You really shouldn't assume that anyone who disagrees with you does so because they're stupid. Publishers know their marginal and fixed costs and certainly have a pretty good idea of the price elasticity of their books. The situation is more complicated than you know.
You can't compare Hachette to Valve, because Valve owns the whole Steam ecosystem, and delivers its services to users' commodity PC hardware with no intermediaries (other than Internet service). In the case of Hachette v. Amazon, we're looking at a situation where Amazon owns the point of sale, and has more control over the users' devices than the user himself has. And yes, you can read ebooks on a PC but few people will want to do that. And yes you can download ebooks in non-proprietary formats like epub from sources other than Amazon, convert the format to.mobi, and use file transfer to move the converted file onto the kindle; but that's a significant barrier for most people.
So what we're looking at is a move by Amazon to take control of the book market in a way it cannot as long as paperback and hardback sales remain strong. Amazon *looks* like a friend of the consumer because they're calling for lower prices. If they get what they want, then ebooks may well make a significant market share headway against paper books.
You might think that's fine, but it's not *generic* formats and *commodity* hardware we're talking about. It's formats and hardware controlled by an inextricably linked to *one* company. And that may mean lower prices today, but what will it mean ten years down the pike when Amazon corners the market on books?
It's urban black culture that disparages intellect.
I'd be interested in your source for this particular tidbit, particularly how it shows blacks are any worse than whites in this regard.
I went to high school with a lot of tough white guys from South Boston and Charlestown in Boston, back when Whitey Bulger was still a big deal in Southie. Let me tell you most of them didn't see intellect as their path into the middle class. A few did, but not many. I've also worked with PhD scientists who were black and came from urban black neighborhoods. You get a mix of attitudes everywhere, whether it's in a black ghetto or white ghetto or a middle-class white neighborhood, but usually being academically advanced doesn't make you popular unless you live in town with a big Jewish population.
Speaking of Whitey, his people used to spread the myth that he kept drugs off the street in Southie. In fact he was kicking the Italian mob out of Southie so he could have the drug trade all to himself. Whitey wasn't a hero, he was a parasite. So why did people believe the lie? Wishful thinking. The people who got education and became professionals moved out of the neighborhood, so the one example of guys who rose in life that you saw every day were the mob. And you had to hope they were good lads at heart, because they had the neighborhood by the balls.
There's often a "we're all in this together" thing going on in poor, downtrodden neighborhoods. Part of that is a resentment of anyone who acts like their above the rest, and that includes people who flaunt their education or sophistication. But that's because intellectual accomplishments don't seem to be within the reach of everybody. You don't get that attitude in cultures which believe in self-improvement.
So let's *not* talk race. Let's talk education and economic opportunity. If people have a way up, see that way, and believe they can do it, they will rise.
Connection tracking can be expensive. If you need that, it's going to cut into the performance of your server, so it can be beneficial to do that on a separate box.
Of course. But putting your servers behind a separate firewall isn't the same as putting them on the same network as the clients with *no* firewall.
In any case, we're talking about an in-store POS system with TWO clients. We're not talking about an Internet facing server that has to handle thousands of connections per hour. Even if the server had FIFTY client terminals the impact on performance would be nil.
Well, I think the first two films are a mixed bag. I rather liked getting meet Radagast, and to see what Gandalf was up to in Dol Guldur.
A screenplay adapted from a book has to stand on its own as well as live up to the book. Where the movies have fallen down is living up to the book. The consensus of my writer friends is that the screenwriting team (Walsh, Boyes, Jackson and del Tormo) doesn't trust Bilbo to carry the story, which deeply undercuts the themes of THE HOBBIT. Lack of respect for THE HOBBIT novel is pretty common among LotR fans. They often dismiss it as "just" a fairy-tale -- an attitude which would have disgusted Tolkien himself. It would have been better if writing this screenplay had been entrusted to someone who loved THE HOBBIT for itself, and understood it better.
Surprisingly, I thought the non-canonical character Tauriel was one of the best parts of the movies. Yes, she was there to give the story a so-called "strong female character", but that's a silly objection. Writers always put characters in stories for some reason; the question is whether they fit in and come to life. I think adding a strong non-canonical character is better than giving so much screentime to a weak but canonical one: Legolas. No disrespect to Orlando Bloom, but the writers dont' give him much to work with. The part could have been played by the CGI model they used in the action scenes.
One of the reasons I'm accepting of the whole Tauriel subplot is that it carries a deeply Tolkienian theme: the love between mortal and elvenkind. That was a profound part of Tolkien's personal mythology. On the gravestone he shares with his wife Edith, he added "Luthien" to her name and "Beren" to his. So I don't view weaving that theme into a dramatic treatment of the HOBBIT story as disrespectful to the author at all.
Re:as opposed to the other kind of corporation?
on
Comcast Confessions
·
· Score: 1
Here's the interesting thing, though. Let's agree that bottom-feeding is the natural ground state of a corporation; what that means is that nearly everybody is doing it, which means bottom-feeders on average don't make any more profit than you'd get investing in a mutual fund, but involve a lot more risk.
If you want to make *more* profit, you have to be about something *in addition to* profit. A great company has an identity which has value. This, by the way, is how Carly Fiorina ruined HP. She re-imagined HP as something more generic.
Air gapping the sensitive information is one of those things that looks easy on paper but runs afoul of the fact that people don't like to work that way. It's inefficient. It's not like people have *two* jobs, one sensitive the other not. They have one job in which sensitive bits are intertwined with regular bits, so in practiced people tend to cheat and do *some* sensitive work on the non-sensitive network.
Even if the users are unrealistically conscientious about never doing anything sensitive on their non-secure PCs, this intertwining of sensitive with ordinary information means that you can probably deduce a lot from apparently innocuous data. Imagine you discover the following information from poking around on an engineer's "non-sensitive" computer:
(1) He is exchanging email with certain university researchers setting up face to face meetings. (2) He has downloaded datasheets for several families of exotic electronic components. (3) He has telephone appointments in his calendar with salesmen from Unobtanium Corp. (4) His browsing history shows he's been reading up on certain mathematical topics on Wolfram Alpha.
Now put this all together and another expert in his field might be able to deduce a lot more than you'd expect than if you looked at any one of these factors. The interconnected nature of an engineer's work means that if you remove all the sensitive bits it leaves a hole of a characteristic shape.
Until someone install something else on the network segment. Like a wireless access point. Or until malware takes over one of the trusted hosts.
Security vulnerabilities always involve violations of some assumptions you make, e.g. that anything coming from a certain set of hosts is benign, or that if a process on a server opens up an IP port it's *supposed* to do that. You want the security of a system to depend on as few assumptions as possible. If it does no harm in day to day operations and offers protection when your assumptions fail, why *not* run a software firewall?
It doesn't have to be linear to be useful. It simply has to be able to sort a set of choices into order -- like movie reviews. Nobody thinks a four star movie is "twice as good" as a two star movie, but people generally find the rank ordering of movies by stars useful provided they don't read to much into the rating. In fact the ordering needn't be unique; there can be other equally useful metrics which order the choices in a slightly different way. *Over certain domains of values* minor differences in orderings may not matter very much, especially as your understanding of your future requirements is always somewhat fuzzy (e.g. the future cost of bandwidth or computing power).
The problem with any metric occurs outside those domains; some parameters may have discontinuities in their marginal utility. A parameter's value may be good enough and further improvements yield no benefit; or the parmater's value may be poor enough to disqualify a choice altogether. In such cases such a metric based on continuous functions will objectively misorder choices.
For example Suppose A is fast enough but has poor compression ratios; B is not quite fast enough but has excellent compression ratios. There's really only one viable choice: A; but the metric may order the choices B,A.
On the other hand suppose A has better compression ratios than B; B is faster than A, but A is already so fast that it makes no practical difference. The rational ordering of choices is A,B but the metric might order them B,A.
This kind of thing is always a problem with boiling choices down to a single composite number. You have to understand what goes into that number and how those things relate to your needs. You have to avoid making your decisions on one number alone. But some people *will* fasten on a single number because it makes the job of choosing seem easier than it does. Just don't be one of those people.
After Gygax's treatment of Arneson and the way he attempted to attack other games in the roleplaying hobby, I find it hard to feel much sympathy for him.
Well, if you put yourself in his shoes you might well play hardball with other games in the hobby.
D&D as a system wasn't really all special; there were competing systems back in the days he was at TSR which were every bit as enjoyable and arguably easier to play. But D&D had two big things going for it. First, when the three basic manuals for AD&D were published it had by far the best organized and written materials. The Monster Manual was particularly useful. Second it had the network effect: it was the best system to learn to play because everyone else knew how to play it. You could start a campaign at a drop of a hat -- no need to bring everyone up to speed on yet another set of rules.
So put yourself in his position. The future success of D&D is contingent on no other game reaching critical mass. You're completely dependent on D&D, you have no other marketable skills or assets. You have a company with over a hundred employees (which is surely a mistake on your part), and that company has nothing else bringing in cash *but* D&D products. You've made D&D your life work. It's not a situation to bring out the best in people.
Different requirements drive different designs. Before WW2 seaplanes were common because of the lack of runways. After WW2 airports proliferated, and seaplanes couldn't keep up with technical advances due to the compromises involved in allowing them to land and take off from water. But that doesn't mean there aren't applications for aircraft with a flying boat's capabilities, it just means there isn't enough of a market in places like the US to support an industry. Even so, here in North America there are some 70 year-old WW2 Catalinas being used in aerial firefighting. China is a vast country which is prone to many kinds of natural disasters that could make airlifting in supplies difficult, so they may see potential applications we don't.
It's also interesting to note that seaplanes were highly useful in the pacific theater of WW2, and there hasn't been a protracted struggle for sea control *since* WW2. Also, China is a country with no operational aircraft carriers; aside from its training ship the Liaoning, it has a handful of amphibious assault ships that can carry a few helicopters. The US by contrast has ten supercarriers and nine amphibious assault ships that dwarf the aircraft carriers of WW2. The technology and expertise to run a carrier fleet like America's would take many years for China to develop. It's conceivable that the manufacturers imagine a military market for aircraft like this in the interim.
It's exactly as many syllables as "ebola" but carries more information, what's not to like?
Indeed, it carries MUCH more precision than just "Ebola", which can mean any of the following:
"Ebola River" is a tributary to the Congo River.
"Ebola Hemorrhagic Fever" was the name of a disease first discovered in people living in the remote Ebola River watershed.
"Ebola Virus" (abbrev. "EBOV") is the infectious agent that causes "Ebola Hemorrhagic Fever"
"Ebolavirus" is the taxonomic genus to which the "Ebola virus" belongs.
"Ebola Virus Disease (abbrev. "EVD") is now the more common name for Ebola Hemorrhagic Fever. We can call it that because we have definitively identified the infectious agent that causes the disease (EBOV). Changing the name pre-emptively differentiates EVD from other hemorrhagic diseases that might arise from the same area.
Laymen simply say "Ebola" and let their audience sort out what they mean -- if indeed they mean anything precisely. I once had this conversation with an elderly relative.
Relative: 90% of bats have rabies.
Me: That's hard to believe.
Relative: It's true! I read it in the paper.
So I went to the paper and found out that she had it hopelessly garbled. TEN percent of bats SUBMITTED FOR TESTING had positive SCREENING tests.
I worked in public health informatics for many years, and it's a longstanding tradition to use three letter codes. I think this is the legacy of old systems which provided three or four character fields for codes, but it certainly speeds things along when you're keying data into a spreadsheet.
The tradition isn't formalized, and so it's application is somewhat irregular, but it's important in this case to realize that public health surveillance makes a strong distinction between a *disease* (a disorder of structure or function in an organism like a human) and an *infectious agent* (the parasite, bacterium, virus or prion that transmits the disease). That's because you can find the infectious agent without finding any cases of the disease -- for example in an asymptomatic human, in a disease carrying vector like a mosquito etc. Non-specialist use the same terms to refer to either the disease or the agent (this naming by association is called "metonymy", a word every system designer should be familiar with). So of course the abbreviations experts use seem nonsensical to non-specialists.
The abbreviation "EVD" maskes perfect sense -- it is the *disease* caused by the Ebola Virus (EBOV). A non-specialist uses terms loosely and would say things like "They found Ebloa in Freetown." A specialist wouldn't use such loose language. He'd say "We found a human case of EVD in Freetown," or "We had a serum with a positive titer for EBOV from Freetown."
There's only one thing you need to know about the H-1B program to see that it's not about providing skilled labor *here*: after 6-10 years of working the visa holder is kicked out of the country to make room for a less experienced visa holder.
If H-1B led automatically to a green card, then we'd be keeping the *most* expert workers here, rather than replacing them with less experienced ones. Change that *one* aspect of the program, and it's be an asset to the US as a nation.
I went back and got a degree after 25 years. It's not the *degree*, it's the *education* that matters, and I got a lot more out of the education than my younger peers. This was a new perspective on things I was already familiar with, and I was able to connect a lot of dots I wouldn't have been able to when I was eighteen. I could immediately see what stuff was good for, and I discovered a number of things that would solve commonplace problems I'd seen occur over and over again, even with personnel wit advanced degrees.
Then I got out and discovered that the world didn't want to hire a fifty year old who'd been "out of work" (going to school) for three years....
Well, you are unlikely to be the *only* one who doesn't think this is all that impressive, because you're unlikely to be the only one who didn't read the article or looking up the device on the company's website.
The robot in question is designed to capture energy from surface waves for propulsion. So it is not a deep submersible, it waddles along a six meters below the surface, tethered to a streamlined surface buoy that it drags along and uses to capture wave energy. Making it through a major storm is a significant proof-of-concept for such a system.
It's not the human *touch* that people crave in a complicated interaction with a system. It's human *versatility*.
Thus more personnel does no good, if those personnel are rigidly controlled, lack information to advise or authority to act. The fact that they're also expected to be jolly and upbeat as they follow their rigid and unyielding rules only turns the interaction with them into a travesty of a social interaction.
What would work better is a well-designed check-in system that handles routine situations nearly all the time, along with a few personnel who have the training and authority to solve any passenger problems that come up.
I can only go with the experience of my friends, who've gone both routes successfully.
It's true that traditional publishers expect mid-list authors to shoulder most of the promotion efforts these days. I never said they didn't. Fiction authors are now expected to maintain a platform, which used to be a non-fiction thing. Certainly traditional publishers have become more predatory and less supportive than they were twenty years ago. I don't have an inside track on why that is, but I suspect there are several causes. One is that POD allows publishers to make an reliable though modest profit from their mid-list authors, which ironically makes them more risk averse. But publishers still provide production and editing services on a MS that'd cost you maybe ten thousand dollars if you were contracting those services out. They also get your book in bricks-and-mortar bookstores, which is a bridge too far for most indy authors, even the successful ones.
A lot of the bad feeling that publishers get from indy authors comes from two sources. First, a long history with rejection. Second the lack of respect indy authors get relative to traditionally published authors. We can see it in this discussion elsewhere, where one poster puts "authors" in quotes when referring to indy authors. And it's easy to see why because most indy authors just aren't good enough to get traditionally published. *Some* indy authors put out a product that's every bit as good as the mid-list authors from the big publishing houses, but most just dump their terrible manuscripts on Amazon with a clip-art cover and no copy editing, much less developmental editing.
The statistic that most indy authors make their investment back plus 40% didn't impress me, because (a) that counts the author's labor as free and (b) most indy authors don't invest much cash in their projects. The percentage of indy authors that clear, say, five thousand dollars in profit are very small.
It's not that indy publishing doesn't have its points, and my traditionally published friends are certainly thinking about dipping their toe in the water. But it's not as cheap as it looks if you want a comparable product, and you give up certain things. I was in Manhattan recently and went to the 5th Avenue branch of the NYPL. My traditionally published friends' books were either on the shelves our out circulating. The NYPL had *none* of my indy author friends' books, even though at least one of them has made the New York Times best seller list.
I don't think it's as simple as Amazon is good or Amazon is evil. Amazon is powerful, and that needs watching.
Now I have a number writer friends, one of whom is published both with traditional imprints like TOR and with Amazon's new in-house publishing imprints. She has good things to say about Amazon's imprints, but one thing you have to take into account is that nobody will stock your book *but* Amazon if you publish with them. That's giving up a lot, so they treat authors reasonably well. But that doesn't mean the corporation actually cares about authors. Amazon needs reliable mid-list authors to make their publishing ventures a success, and by cutting out the middleman can afford generous royalties. But if Amazon succeeds in putting a stake in the heart of traditional publishing, I wouldn't care to speculate on what will happen to authors.
Nor should what traditional publishers do for authors be underestimated. I have friends who are successful indy writers, but it's not like being a writer, it's more like running a small publishing house yourself. They hire story editors, copy editors and artists, and manage promotion and publicity. It's a lot of work; that plus actually writing pretty much precludes a day job. It's not for everyone.
It's a lot like being an engineer. Engineers are smart people who usually have a lot of insight into the companies they work for, but that doesn't mean that most engineers want to run businesses. Some do, but most would rather have other people take care of that stuff so they can concentrate on what they feel they're best at.
Many writers choose the indy market because it's the only way they'll ever get published. They just dump their manuscript on the market without editing, design or promotion and hope for the best. They rarely succeed. Others choose the indy route because they thrive on running and controlling their own small business, the way some engineers step naturally into the role of entrepreneur. They're well positioned for the future. But most writers need support to reach their full potential.
It's actually 'Breeches' and now we finally know Step 2.
Years ago, when static electricity was bad news for computers, I had the idea for a "data processing shoe" that would have a little conductive ribbon that would drag along the floor and ground out static electricity. Such a thing is of course no longer needed, but given the apparent popularity of data breeches these days maybe the concept could be resurrected as a fashion statement.
Slashdot Mirror
Implementation makes a difference. Early versions of NT were quite good, but unpopular because you needed 16MB of RAM (if I recall correctly) to run them in an era when a high end personal computer shipped with 4MB of RAM. Over the years they tried to hold the line, at one point getting the minimum down to 12MB of RAM, but perhaps not coincidentally stability got really bad.
Yes, he designed stuff for our enemy, but if I had lived in the civil war times I might have built something like the CSS submarine Hunley.
With slave labor, no less.
Yes people are limited by their culture and time, but not *that* limited. Braun deserves condemnation for using slave labor in WW2.
Yes, publishers and middlemen have all kinds of rationalizations for trying to kill e-books, but calling any of them "legitimate" is shilling so hard you could pence a crown.
All the arguments based on classical economic theory only work if the assumptions of classical economics hold, particularly the assumption that there is a free market.
Amazon is arguing for its freedom to set prices it charges in its ebook store; that would be no concern of the publishers if we lived in a world where ebook users could simply buy books in non-proprietary formats from any Internet storefront they wanted. But we don't live in such a world. We live in a world where most ebook readers are controlled by Amazon and inextricably linked to its store. It wouldn't have been hard for Amazon to build the Kindle that way. Define some public book trading protocols, bootstrap the standard by building those protocols into the Kindle and Amazon's online store, and instantly the world is a better place for everyone except printers and bricks-and-mortar bookstores with no Internet presence. But Amazon didn't do that, because the Kindle is designed to tie the user to Amazon, the way the iPad is designed to tie the user to Apple.
So what we're looking at is a maneuver by Amazon to corner the market on books *in general* by killing off the traditional paper book trade. Preserving the ability to buy most books from someone other than Amazon seems like a legitimate reason to me.
No dude, your books are not so incredible that people will buy them no matter what the price.
Nobody's book is so incredible that people would buy them no matter what the price. If my only way to get Shakespeare was to pay a ten thousand dollar license fee I'd find a way to do without.
Authors/publishers/developers/etc need to get over this idea of their digital goods being "worth" a certain amount. No, you need to figure out what you need to do to maximize your profits since there is zero per unit cost. Usually, that is going to mean selling cheap, but selling lots.
You really shouldn't assume that anyone who disagrees with you does so because they're stupid. Publishers know their marginal and fixed costs and certainly have a pretty good idea of the price elasticity of their books. The situation is more complicated than you know.
You can't compare Hachette to Valve, because Valve owns the whole Steam ecosystem, and delivers its services to users' commodity PC hardware with no intermediaries (other than Internet service). In the case of Hachette v. Amazon, we're looking at a situation where Amazon owns the point of sale, and has more control over the users' devices than the user himself has. And yes, you can read ebooks on a PC but few people will want to do that. And yes you can download ebooks in non-proprietary formats like epub from sources other than Amazon, convert the format to .mobi, and use file transfer to move the converted file onto the kindle; but that's a significant barrier for most people.
So what we're looking at is a move by Amazon to take control of the book market in a way it cannot as long as paperback and hardback sales remain strong. Amazon *looks* like a friend of the consumer because they're calling for lower prices. If they get what they want, then ebooks may well make a significant market share headway against paper books.
You might think that's fine, but it's not *generic* formats and *commodity* hardware we're talking about. It's formats and hardware controlled by an inextricably linked to *one* company. And that may mean lower prices today, but what will it mean ten years down the pike when Amazon corners the market on books?
It's urban black culture that disparages intellect.
I'd be interested in your source for this particular tidbit, particularly how it shows blacks are any worse than whites in this regard.
I went to high school with a lot of tough white guys from South Boston and Charlestown in Boston, back when Whitey Bulger was still a big deal in Southie. Let me tell you most of them didn't see intellect as their path into the middle class. A few did, but not many. I've also worked with PhD scientists who were black and came from urban black neighborhoods. You get a mix of attitudes everywhere, whether it's in a black ghetto or white ghetto or a middle-class white neighborhood, but usually being academically advanced doesn't make you popular unless you live in town with a big Jewish population.
Speaking of Whitey, his people used to spread the myth that he kept drugs off the street in Southie. In fact he was kicking the Italian mob out of Southie so he could have the drug trade all to himself. Whitey wasn't a hero, he was a parasite. So why did people believe the lie? Wishful thinking. The people who got education and became professionals moved out of the neighborhood, so the one example of guys who rose in life that you saw every day were the mob. And you had to hope they were good lads at heart, because they had the neighborhood by the balls.
There's often a "we're all in this together" thing going on in poor, downtrodden neighborhoods. Part of that is a resentment of anyone who acts like their above the rest, and that includes people who flaunt their education or sophistication. But that's because intellectual accomplishments don't seem to be within the reach of everybody. You don't get that attitude in cultures which believe in self-improvement.
So let's *not* talk race. Let's talk education and economic opportunity. If people have a way up, see that way, and believe they can do it, they will rise.
Connection tracking can be expensive. If you need that, it's going to cut into the performance of your server, so it can be beneficial to do that on a separate box.
Of course. But putting your servers behind a separate firewall isn't the same as putting them on the same network as the clients with *no* firewall.
In any case, we're talking about an in-store POS system with TWO clients. We're not talking about an Internet facing server that has to handle thousands of connections per hour. Even if the server had FIFTY client terminals the impact on performance would be nil.
Well, I think the first two films are a mixed bag. I rather liked getting meet Radagast, and to see what Gandalf was up to in Dol Guldur.
A screenplay adapted from a book has to stand on its own as well as live up to the book. Where the movies have fallen down is living up to the book. The consensus of my writer friends is that the screenwriting team (Walsh, Boyes, Jackson and del Tormo) doesn't trust Bilbo to carry the story, which deeply undercuts the themes of THE HOBBIT. Lack of respect for THE HOBBIT novel is pretty common among LotR fans. They often dismiss it as "just" a fairy-tale -- an attitude which would have disgusted Tolkien himself. It would have been better if writing this screenplay had been entrusted to someone who loved THE HOBBIT for itself, and understood it better.
Surprisingly, I thought the non-canonical character Tauriel was one of the best parts of the movies. Yes, she was there to give the story a so-called "strong female character", but that's a silly objection. Writers always put characters in stories for some reason; the question is whether they fit in and come to life. I think adding a strong non-canonical character is better than giving so much screentime to a weak but canonical one: Legolas. No disrespect to Orlando Bloom, but the writers dont' give him much to work with. The part could have been played by the CGI model they used in the action scenes.
One of the reasons I'm accepting of the whole Tauriel subplot is that it carries a deeply Tolkienian theme: the love between mortal and elvenkind. That was a profound part of Tolkien's personal mythology. On the gravestone he shares with his wife Edith, he added "Luthien" to her name and "Beren" to his. So I don't view weaving that theme into a dramatic treatment of the HOBBIT story as disrespectful to the author at all.
Here's the interesting thing, though. Let's agree that bottom-feeding is the natural ground state of a corporation; what that means is that nearly everybody is doing it, which means bottom-feeders on average don't make any more profit than you'd get investing in a mutual fund, but involve a lot more risk.
If you want to make *more* profit, you have to be about something *in addition to* profit. A great company has an identity which has value. This, by the way, is how Carly Fiorina ruined HP. She re-imagined HP as something more generic.
Air gapping the sensitive information is one of those things that looks easy on paper but runs afoul of the fact that people don't like to work that way. It's inefficient. It's not like people have *two* jobs, one sensitive the other not. They have one job in which sensitive bits are intertwined with regular bits, so in practiced people tend to cheat and do *some* sensitive work on the non-sensitive network.
Even if the users are unrealistically conscientious about never doing anything sensitive on their non-secure PCs, this intertwining of sensitive with ordinary information means that you can probably deduce a lot from apparently innocuous data. Imagine you discover the following information from poking around on an engineer's "non-sensitive" computer:
(1) He is exchanging email with certain university researchers setting up face to face meetings.
(2) He has downloaded datasheets for several families of exotic electronic components.
(3) He has telephone appointments in his calendar with salesmen from Unobtanium Corp.
(4) His browsing history shows he's been reading up on certain mathematical topics on Wolfram Alpha.
Now put this all together and another expert in his field might be able to deduce a lot more than you'd expect than if you looked at any one of these factors. The interconnected nature of an engineer's work means that if you remove all the sensitive bits it leaves a hole of a characteristic shape.
Until someone install something else on the network segment. Like a wireless access point. Or until malware takes over one of the trusted hosts.
Security vulnerabilities always involve violations of some assumptions you make, e.g. that anything coming from a certain set of hosts is benign, or that if a process on a server opens up an IP port it's *supposed* to do that. You want the security of a system to depend on as few assumptions as possible. If it does no harm in day to day operations and offers protection when your assumptions fail, why *not* run a software firewall?
It doesn't have to be linear to be useful. It simply has to be able to sort a set of choices into order -- like movie reviews. Nobody thinks a four star movie is "twice as good" as a two star movie, but people generally find the rank ordering of movies by stars useful provided they don't read to much into the rating. In fact the ordering needn't be unique; there can be other equally useful metrics which order the choices in a slightly different way. *Over certain domains of values* minor differences in orderings may not matter very much, especially as your understanding of your future requirements is always somewhat fuzzy (e.g. the future cost of bandwidth or computing power).
The problem with any metric occurs outside those domains; some parameters may have discontinuities in their marginal utility. A parameter's value may be good enough and further improvements yield no benefit; or the parmater's value may be poor enough to disqualify a choice altogether. In such cases such a metric based on continuous functions will objectively misorder choices.
For example Suppose A is fast enough but has poor compression ratios; B is not quite fast enough but has excellent compression ratios. There's really only one viable choice: A; but the metric may order the choices B,A.
On the other hand suppose A has better compression ratios than B; B is faster than A, but A is already so fast that it makes no practical difference. The rational ordering of choices is A,B but the metric might order them B,A.
This kind of thing is always a problem with boiling choices down to a single composite number. You have to understand what goes into that number and how those things relate to your needs. You have to avoid making your decisions on one number alone. But some people *will* fasten on a single number because it makes the job of choosing seem easier than it does. Just don't be one of those people.
After Gygax's treatment of Arneson and the way he attempted to attack other games in the roleplaying hobby, I find it hard to feel much sympathy for him.
Well, if you put yourself in his shoes you might well play hardball with other games in the hobby.
D&D as a system wasn't really all special; there were competing systems back in the days he was at TSR which were every bit as enjoyable and arguably easier to play. But D&D had two big things going for it. First, when the three basic manuals for AD&D were published it had by far the best organized and written materials. The Monster Manual was particularly useful. Second it had the network effect: it was the best system to learn to play because everyone else knew how to play it. You could start a campaign at a drop of a hat -- no need to bring everyone up to speed on yet another set of rules.
So put yourself in his position. The future success of D&D is contingent on no other game reaching critical mass. You're completely dependent on D&D, you have no other marketable skills or assets. You have a company with over a hundred employees (which is surely a mistake on your part), and that company has nothing else bringing in cash *but* D&D products. You've made D&D your life work. It's not a situation to bring out the best in people.
Different requirements drive different designs. Before WW2 seaplanes were common because of the lack of runways. After WW2 airports proliferated, and seaplanes couldn't keep up with technical advances due to the compromises involved in allowing them to land and take off from water. But that doesn't mean there aren't applications for aircraft with a flying boat's capabilities, it just means there isn't enough of a market in places like the US to support an industry. Even so, here in North America there are some 70 year-old WW2 Catalinas being used in aerial firefighting. China is a vast country which is prone to many kinds of natural disasters that could make airlifting in supplies difficult, so they may see potential applications we don't.
It's also interesting to note that seaplanes were highly useful in the pacific theater of WW2, and there hasn't been a protracted struggle for sea control *since* WW2. Also, China is a country with no operational aircraft carriers; aside from its training ship the Liaoning, it has a handful of amphibious assault ships that can carry a few helicopters. The US by contrast has ten supercarriers and nine amphibious assault ships that dwarf the aircraft carriers of WW2. The technology and expertise to run a carrier fleet like America's would take many years for China to develop. It's conceivable that the manufacturers imagine a military market for aircraft like this in the interim.
He said multiple things. /sh*t/ matches sht, shht, shhht, shhhht, shhhhhhhhhhhhhhht
and an infinity of variants on the theme.
No cussing here.
...or if he's using shell style wildcards, he could mean "pure and utter sherbet."
And Mussolini made the trains run on time?
Reports of trains *not* running on time certainly decreased, but that's not quite the same thing...
It's exactly as many syllables as "ebola" but carries more information, what's not to like?
Indeed, it carries MUCH more precision than just "Ebola", which can mean any of the following:
"Ebola River" is a tributary to the Congo River.
"Ebola Hemorrhagic Fever" was the name of a disease first discovered in people living in the remote Ebola River watershed.
"Ebola Virus" (abbrev. "EBOV") is the infectious agent that causes "Ebola Hemorrhagic Fever"
"Ebolavirus" is the taxonomic genus to which the "Ebola virus" belongs.
"Ebola Virus Disease (abbrev. "EVD") is now the more common name for Ebola Hemorrhagic Fever. We can call it that because we have definitively identified the infectious agent that causes the disease (EBOV). Changing the name pre-emptively differentiates EVD from other hemorrhagic diseases that might arise from the same area.
Laymen simply say "Ebola" and let their audience sort out what they mean -- if indeed they mean anything precisely. I once had this conversation with an elderly relative.
Relative: 90% of bats have rabies.
Me: That's hard to believe.
Relative: It's true! I read it in the paper.
So I went to the paper and found out that she had it hopelessly garbled. TEN percent of bats SUBMITTED FOR TESTING had positive SCREENING tests.
I worked in public health informatics for many years, and it's a longstanding tradition to use three letter codes. I think this is the legacy of old systems which provided three or four character fields for codes, but it certainly speeds things along when you're keying data into a spreadsheet.
The tradition isn't formalized, and so it's application is somewhat irregular, but it's important in this case to realize that public health surveillance makes a strong distinction between a *disease* (a disorder of structure or function in an organism like a human) and an *infectious agent* (the parasite, bacterium, virus or prion that transmits the disease). That's because you can find the infectious agent without finding any cases of the disease -- for example in an asymptomatic human, in a disease carrying vector like a mosquito etc. Non-specialist use the same terms to refer to either the disease or the agent (this naming by association is called "metonymy", a word every system designer should be familiar with). So of course the abbreviations experts use seem nonsensical to non-specialists.
The abbreviation "EVD" maskes perfect sense -- it is the *disease* caused by the Ebola Virus (EBOV). A non-specialist uses terms loosely and would say things like "They found Ebloa in Freetown." A specialist wouldn't use such loose language. He'd say "We found a human case of EVD in Freetown," or "We had a serum with a positive titer for EBOV from Freetown."
There's only one thing you need to know about the H-1B program to see that it's not about providing skilled labor *here*: after 6-10 years of working the visa holder is kicked out of the country to make room for a less experienced visa holder.
If H-1B led automatically to a green card, then we'd be keeping the *most* expert workers here, rather than replacing them with less experienced ones. Change that *one* aspect of the program, and it's be an asset to the US as a nation.
I went back and got a degree after 25 years. It's not the *degree*, it's the *education* that matters, and I got a lot more out of the education than my younger peers. This was a new perspective on things I was already familiar with, and I was able to connect a lot of dots I wouldn't have been able to when I was eighteen. I could immediately see what stuff was good for, and I discovered a number of things that would solve commonplace problems I'd seen occur over and over again, even with personnel wit advanced degrees.
Then I got out and discovered that the world didn't want to hire a fifty year old who'd been "out of work" (going to school) for three years....
Well, you are unlikely to be the *only* one who doesn't think this is all that impressive, because you're unlikely to be the only one who didn't read the article or looking up the device on the company's website.
The robot in question is designed to capture energy from surface waves for propulsion. So it is not a deep submersible, it waddles along a six meters below the surface, tethered to a streamlined surface buoy that it drags along and uses to capture wave energy. Making it through a major storm is a significant proof-of-concept for such a system.
It's not the human *touch* that people crave in a complicated interaction with a system. It's human *versatility*.
Thus more personnel does no good, if those personnel are rigidly controlled, lack information to advise or authority to act. The fact that they're also expected to be jolly and upbeat as they follow their rigid and unyielding rules only turns the interaction with them into a travesty of a social interaction.
What would work better is a well-designed check-in system that handles routine situations nearly all the time, along with a few personnel who have the training and authority to solve any passenger problems that come up.
I'm pretty sure birth control exists.
I can only go with the experience of my friends, who've gone both routes successfully.
It's true that traditional publishers expect mid-list authors to shoulder most of the promotion efforts these days. I never said they didn't. Fiction authors are now expected to maintain a platform, which used to be a non-fiction thing. Certainly traditional publishers have become more predatory and less supportive than they were twenty years ago. I don't have an inside track on why that is, but I suspect there are several causes. One is that POD allows publishers to make an reliable though modest profit from their mid-list authors, which ironically makes them more risk averse. But publishers still provide production and editing services on a MS that'd cost you maybe ten thousand dollars if you were contracting those services out. They also get your book in bricks-and-mortar bookstores, which is a bridge too far for most indy authors, even the successful ones.
A lot of the bad feeling that publishers get from indy authors comes from two sources. First, a long history with rejection. Second the lack of respect indy authors get relative to traditionally published authors. We can see it in this discussion elsewhere, where one poster puts "authors" in quotes when referring to indy authors. And it's easy to see why because most indy authors just aren't good enough to get traditionally published. *Some* indy authors put out a product that's every bit as good as the mid-list authors from the big publishing houses, but most just dump their terrible manuscripts on Amazon with a clip-art cover and no copy editing, much less developmental editing.
The statistic that most indy authors make their investment back plus 40% didn't impress me, because (a) that counts the author's labor as free and (b) most indy authors don't invest much cash in their projects. The percentage of indy authors that clear, say, five thousand dollars in profit are very small.
It's not that indy publishing doesn't have its points, and my traditionally published friends are certainly thinking about dipping their toe in the water. But it's not as cheap as it looks if you want a comparable product, and you give up certain things. I was in Manhattan recently and went to the 5th Avenue branch of the NYPL. My traditionally published friends' books were either on the shelves our out circulating. The NYPL had *none* of my indy author friends' books, even though at least one of them has made the New York Times best seller list.
I don't think it's as simple as Amazon is good or Amazon is evil. Amazon is powerful, and that needs watching.
Now I have a number writer friends, one of whom is published both with traditional imprints like TOR and with Amazon's new in-house publishing imprints. She has good things to say about Amazon's imprints, but one thing you have to take into account is that nobody will stock your book *but* Amazon if you publish with them. That's giving up a lot, so they treat authors reasonably well. But that doesn't mean the corporation actually cares about authors. Amazon needs reliable mid-list authors to make their publishing ventures a success, and by cutting out the middleman can afford generous royalties. But if Amazon succeeds in putting a stake in the heart of traditional publishing, I wouldn't care to speculate on what will happen to authors.
Nor should what traditional publishers do for authors be underestimated. I have friends who are successful indy writers, but it's not like being a writer, it's more like running a small publishing house yourself. They hire story editors, copy editors and artists, and manage promotion and publicity. It's a lot of work; that plus actually writing pretty much precludes a day job. It's not for everyone.
It's a lot like being an engineer. Engineers are smart people who usually have a lot of insight into the companies they work for, but that doesn't mean that most engineers want to run businesses. Some do, but most would rather have other people take care of that stuff so they can concentrate on what they feel they're best at.
Many writers choose the indy market because it's the only way they'll ever get published. They just dump their manuscript on the market without editing, design or promotion and hope for the best. They rarely succeed. Others choose the indy route because they thrive on running and controlling their own small business, the way some engineers step naturally into the role of entrepreneur. They're well positioned for the future. But most writers need support to reach their full potential.
It's actually 'Breeches' and now we finally know Step 2.
Years ago, when static electricity was bad news for computers, I had the idea for a "data processing shoe" that would have a little conductive ribbon that would drag along the floor and ground out static electricity. Such a thing is of course no longer needed, but given the apparent popularity of data breeches these days maybe the concept could be resurrected as a fashion statement.