Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Pricing? No, *licensing* (Score 2) 127

It's all very nice that they've decided to try and up the single-thread performance. However, it's worth noting that the only thing worthwhile to run on a SPARC nowadays (thanks to Oracle's PMITA licensing structure) is Oracle DB. You buy an Oracle box to run Oracle. Any other workload is nonsensical, as you'll get better single-thread performance from x86, and you'll get way more cycles per dollar from... well, just about any other hardware/OS combination out there.

So as you consider purchasing this higher-clocked box, I've been told that the Oracle licensing for this machine will be 0.5 per core, while the T3 is 0.25 per core. Basically Oracle will cost approximately twice as much per core on this machine. I'm not a DBA... does that make any sense, when databases are traditionally I/O-bound?

Incidentally, my first paragraph caused me pain to type... I'm my organization's SPARC and Solaris expert, and I was a big pusher of the platform. Oracle's takeover and subsequent psychotic support costs and absolute blindness to any workload not DB-oriented was a fair kick in the pants to me. I'll fully admit that I'm not impartial.

Submission + - No right to lawyer during questioning, SCC Rules (www.ctv.ca)

An anonymous reader writes: Canadians do not have a constitutional right to have a lawyer present during questioning by authorities, the Supreme Court of Canada said today.
Open Source

Submission + - CBC Bans Use of Creative Commons Music on Podcasts (michaelgeist.ca) 3

An anonymous reader writes: The producers of the popular CBC radio show Spark have revealed (see the comments) that the public broadcaster has banned programs from using Creative Commons licenced music on podcasts. The decision is apparently the result of restrictions in collective agreements the CBC has with some talent agencies. In other words, groups are actively working to block the use of Creative Commons licenced alternatives in their contractual language. It is enormously problematic to learn that our public broadcaster is blocked from using music alternatives that the creators want to make readily available. The CBC obviously isn't required to use Creative Commons licenced music, but this highlights an instance where at least one of its programs wants to use it and groups that purport to support artists' right to choose the rights associated with their work is trying to stop them from doing so.

Submission + - Why Contributor Agreements Are Community-Toxic (computerworlduk.com)

WebMink writes: "A project dubbed "Harmony", imitated by Canonical, is trying to get so-called "contributor agreements" standardised to save corporations money. But the process could also standardise on copyright aggregation, where community participants donate their work to corporate sponsors. Many big open source communities — including Linux, Apache, GNOME and Mozilla — avoid doing so and have large communities as a consequence. This comprehensive article explores the reasons corporations want copyright aggregation and the reason it's toxic to open source communities."

Comment Anyone read any of Keith Laumer's Bolo books? (Score 1) 317

To give a quick rundown, Keith Laumer came up with the idea of "Bolos", which are essentially oversized, insanely-armed sentient tanks. There's a number of novels and short stories (I recommend Road to Damascus, which I think might even be available for free on the web) all of varying quality.

The running theme through the novels is the machines exemplifying military virtue, while the humans often screw things up and generally fear their own creations. I find them refreshing because it's nice to read a book where our creations aren't interested in stomping our faces with a metal-shod boot.

It gives some interesting ideas on the autonomous battle-robot theme.

  - A war-bot is not really capable of mercy, which I think is the main point a lot of people are making so far.

  - A war-bot is not really capable of war-CRIMES, either. It's not going to care that you blew up its buddy.

  - The lack of self-preservation instinct can prevent rash action. You can program a robot to TAKE a shot or two before reacting.

  - The other side of the coin is that once the robot decides to engage you, it's on. If you pull a gun in front of a squad of soldiers, accidentally or deliberately, they MIGHT let you have a second or two to reconsider your actions and surrender. With a robot, you're paste.

  - You have to consider the difference between TRULY autonomous robots and robots working in conjunction with humans. I'm talking about the difference between a squad of bots operating alone and bots assisting/protecting human soldiers. I'd call the latter far more dangerous, and not because I'm worried about friendly fire. A squad of humans and their bots patrolling a nasty neighbourhood in Baghdad or Kandahar is going to WANT their metal buddies dialed up to "Paranoid" so that they can react to suicide bombers fast enough to avoid getting hurt themselves. That combination can do far more damage than a squad of humans or of robots deployed alone. You get all the bad decision-making of humans combined with the threat-reaction and firepower of machines.

It should probably be mentioned that we already have an example of a semi-autonomous battle robot... the Phalanx CIWS. Flaws with it aside, that's an example of a machine that decides when and what to kill. I even got the impression from a Navy guy I knew that sometimes the people it protected were a bit scared of it... if you wandered into its engagement envelope you were dead, no ifs or maybes. A Slashdotter familiar with the thing might have some interesting perspective.

I apologize for the semi-rambling of my post. It's early.

Slashdot Top Deals

Lots of folks confuse bad management with destiny. -- Frank Hubbard

Working...