People from Alabama may absurdly drawl out certain vowels but they don't murder the language in the way that only a non-native speaker can. Have you been to a Stop-n-Go lately? Sheesh.
We employ computers instead of people because we are short-sighted nitwits with no comprehension of anything other than a simple number that constitutes the bottom line. A computer will not do anything that is above and beyond its call of duty, yet people do this everyday. Too bad we're too "expensive".
The CIM schema does boggle the mind. It is huge and models things that seem downright silly. Finding the correct place in the tree for parenting your subclass can be, at least, time consuming.
However, you aren't forced to use the schema. From what I have seen, most of the software that exposes management through CIM declares a new namespace and forgoes use of the CIM schema altogether.
My point of mentioning that CIM has a XML-based RPC protocol was only to show how WS-Management doesn't offer anything new. The common approach is to use a more efficient protocol like Java's RMI, but the XML option is there in case you need to support communications between CIMOMs that don't share a common, binary RPC protocol.
Regarding SNMP v/s CIM, that is a lot like arguing C v/s C++ (or religion, for that matter). Don't want to go there.
CIM is a fine, object-oriented replacement for SNMP, is mature and has XML-based communications over HTTP.
http://www.dmtf.org/standards/cim/
Microsoft already has a CIMOM implementation in its WMI service, although it uses DCOM to implement RPCs. Sun also has a CIMOM implementation for Solaris.
I find it very strange that the WS-Management.PDF doesn't even reference CIM.
> The scene with the baby-killing was sick. Pure and > simple. It added nothing to the story.
It was disturbing, but didn't you notice the look on Number 6's face during her escape from the crimescene? It wasn't a maniacal grin; she looked to be in aguish. It was the look a child has after breaking a toy, which explains a lot about the Cylon mentality.
> Some Epic music like the original had would have > been great.
I guess you missed the flyover during the decommissioning ceremony.:) Seriously, it was kind of nice to not have some overwhelming John Williams score blaring at me throughout the flick.
> The Galactica needs to be BIGGER. You get the > sense that she's about the size of a modern > aircraft carrier. That's big, but nowhere near > as big as the concept of a "BattleStar" calls > for.
Funny you mention that, because in the Sci Fi "insider" they discuss how the Galactica was modeled after British aircraft carriers of the mid 1900's.
> The uniforms suck. The flight suits are okay, > but the wrestling outfits are terrible!
I didn't mind Starbuck's so much, but Adama in tights was disturbing.
> Plus that cigar makes Starbuck come across a > little disgusting.
Oh, grow up. Lots of hotties smoke cigars. I loved when she decked Tigh, that had me hooked from the start.
Dude, you're from the 12 colonies of man? Awesome! Let me assure you that Earth does exist, and that anybody on/. will gladly be your slave for a hour in a Viper or on Number 6. We sent directions about 25 years ago, look for them en route to Alpha Centauri.
As far as why the Cylons want to kill you, perhaps it's because you created them to be your slaves? Just guessing.:)
I would have to say that job postings which declare "employees" are "paid" in stock instead of money are the absolute worst. That bullshit might have worked to some degree in 1998, but I think we've all seen the man behind the curtain by now.
That's a gross generalization. A better statement would be "JDO insulates you from needing to know a lot about database implementations". That is, your businless logic need not be concerned with which SQL dialect it needs to use depending on which RDBMS you are talking to. JDBC syntax goes a long way towards insulating you from quirky non-standard syntax, but java to SQL type mappings are a different story altogether. When you know that you are always going to deploy against a certain flavor of database, then these aren't issues. However, for those of us that don't like to tell our bosses that we can't change database vendors without a major development effort, vendor neutrality is a hot button issue.
What JDO provides is a "standardized" implementation of the abstraction that most software engineers would write to insulate business logic from persistence, rather than having JDBC code strewn throughout all layers of the application.
The GUI coder needn't know how the objects are persisted any more than the server-side coder needs to know about widgets and whatnot. Somebody on your team needs to understand SQL, because even with JDO you are going to need to delve into some sort of SQL coding to get a workable solution (e.g. DDL for the production database, specialized queries not supported by the JDO specification).
BTW my company uses TJDO as the O/R mapper for our J2EE application. We were able to migrate from PostgreSQL to Oracle 8 in the period of a few days. YMMV, but that says a lot towards the utility of JDO and maintaining vendor neutrality.
It seems like an entirely different device would be in order for this type of input. As you certainly know, there are workarounds known as "input methods" for the standard keyboards. From what I hear they are terrible to use.
If it's anything like the ALT-#### sequence on windows to generate accented and tilded characters of the Latin-1 set, then I know your pain.
Idiot. I read the article. Apparently you don't have the common sense necessary to filter out the bullsh*t posted on the Internet.
You think Mickey D's or BK is going to give you anything besides lovehandles and a heart attack? If you had half a brain you'd realize that nobody is going to be giving away something that can be used as fuel.
This occurred to me as well. Corn oil goes for a whopping $7.50 a gallon. Granted, edible oil would probably be of substantially higher quality that what you put in your gas tank.
To your claim that it needs diesel as well, there are engines that run on biodiesel alone. Greasel's FAQ states that diesel has to be used for warmup and shutdown. Perhaps more expensive conversions have solved this with electric fuel heaters and pumps.
Slashdot Mirror
Dude, is this slashdot or frickin zdnet? Since when does Bill Gates get props here?
The less that I have in common with that guy, the better.
OK, I get the utility. This usage is analogous in flow to try/catch blocks used for error handling.
However, in the interest of proving your point, perhaps posting an example that avoids other pitfalls (e.g. leaking memory) would be more instructive?
Oh, you're playing games alright...
People from Alabama may absurdly drawl out certain vowels but they don't murder the language in the way that only a non-native speaker can. Have you been to a Stop-n-Go lately? Sheesh.
We employ computers instead of people because we are short-sighted nitwits with no comprehension of anything other than a simple number that constitutes the bottom line. A computer will not do anything that is above and beyond its call of duty, yet people do this everyday. Too bad we're too "expensive".
The CIM schema does boggle the mind. It is huge and models things that seem downright silly. Finding the correct place in the tree for parenting your subclass can be, at least, time consuming.
However, you aren't forced to use the schema. From what I have seen, most of the software that exposes management through CIM declares a new namespace and forgoes use of the CIM schema altogether.
My point of mentioning that CIM has a XML-based RPC protocol was only to show how WS-Management doesn't offer anything new. The common approach is to use a more efficient protocol like Java's RMI, but the XML option is there in case you need to support communications between CIMOMs that don't share a common, binary RPC protocol.
Regarding SNMP v/s CIM, that is a lot like arguing C v/s C++ (or religion, for that matter). Don't want to go there.
CIM is a fine, object-oriented replacement for SNMP, is mature and has XML-based communications over HTTP.
.PDF doesn't even reference CIM.
http://www.dmtf.org/standards/cim/
Microsoft already has a CIMOM implementation in its WMI service, although it uses DCOM to implement RPCs. Sun also has a CIMOM implementation for Solaris.
I find it very strange that the WS-Management
Methinks Muad'Dib would approve.
Yeah, they should have snagged 105 E 5th when they had the chance!
Slashdotted already. This has to be a record.
Terry Bussell, Gov. Kenny Guinn's adviser on homeland security, ruled out terrorism...
Whew, that's a relief.
All together now!
Euphemize and redirect!
Euphemize and redirect!
It's the American way, as is verbing words.
A. Russell Jones may not know dick about oss, but he's a genious on the topic of "how to spike your web traffic for one day".
> The scene with the baby-killing was sick. Pure and > simple. It added nothing to the story.
:) Seriously, it was kind of nice to not have some overwhelming John Williams score blaring at me throughout the flick.
It was disturbing, but didn't you notice the look on Number 6's face during her escape from the crimescene? It wasn't a maniacal grin; she looked to be in aguish. It was the look a child has after breaking a toy, which explains a lot about the Cylon mentality.
> Some Epic music like the original had would have > been great.
I guess you missed the flyover during the decommissioning ceremony.
> The Galactica needs to be BIGGER. You get the
> sense that she's about the size of a modern
> aircraft carrier. That's big, but nowhere near
> as big as the concept of a "BattleStar" calls
> for.
Funny you mention that, because in the Sci Fi "insider" they discuss how the Galactica was modeled after British aircraft carriers of the mid 1900's.
> The uniforms suck. The flight suits are okay,
> but the wrestling outfits are terrible!
I didn't mind Starbuck's so much, but Adama in tights was disturbing.
> Plus that cigar makes Starbuck come across a
> little disgusting.
Oh, grow up. Lots of hotties smoke cigars. I loved when she decked Tigh, that had me hooked from the start.
Dude, you're from the 12 colonies of man? Awesome! Let me assure you that Earth does exist, and that anybody on /. will gladly be your slave for a hour in a Viper or on Number 6. We sent directions about 25 years ago, look for them en route to Alpha Centauri.
:)
As far as why the Cylons want to kill you, perhaps it's because you created them to be your slaves? Just guessing.
I would have to say that job postings which declare "employees" are "paid" in stock instead of money are the absolute worst. That bullshit might have worked to some degree in 1998, but I think we've all seen the man behind the curtain by now.
Hey buddy, this is "news for nerds". Who let the MBA in here?
ARGH! Boddington's is shit! Make mine Guinness, Bass or a Sammy. Pilsner Urquell, Red Hook or Old Speckled Hen.
Anything, almost, but a Boddington's!
Hey, can I use that for my band?
That's a gross generalization. A better statement would be "JDO insulates you from needing to know a lot about database implementations". That is, your businless logic need not be concerned with which SQL dialect it needs to use depending on which RDBMS you are talking to. JDBC syntax goes a long way towards insulating you from quirky non-standard syntax, but java to SQL type mappings are a different story altogether. When you know that you are always going to deploy against a certain flavor of database, then these aren't issues. However, for those of us that don't like to tell our bosses that we can't change database vendors without a major development effort, vendor neutrality is a hot button issue.
What JDO provides is a "standardized" implementation of the abstraction that most software engineers would write to insulate business logic from persistence, rather than having JDBC code strewn throughout all layers of the application.
The GUI coder needn't know how the objects are persisted any more than the server-side coder needs to know about widgets and whatnot. Somebody on your team needs to understand SQL, because even with JDO you are going to need to delve into some sort of SQL coding to get a workable solution (e.g. DDL for the production database, specialized queries not supported by the JDO specification).
BTW my company uses TJDO as the O/R mapper for our J2EE application. We were able to migrate from PostgreSQL to Oracle 8 in the period of a few days. YMMV, but that says a lot towards the utility of JDO and maintaining vendor neutrality.
I'd pay money to see you use it.
It seems like an entirely different device would be in order for this type of input. As you certainly know, there are workarounds known as "input methods" for the standard keyboards. From what I hear they are terrible to use.
If it's anything like the ALT-#### sequence on windows to generate accented and tilded characters of the Latin-1 set, then I know your pain.
Depends on the vibrator.
BWARRRRRRRRRRRRRRRRRR!
I'd love to see my boss apply his hunt-and-peck approach to typing on that vertical keyboard. He'd probably end up in traction.
You think Mickey D's or BK is going to give you anything besides lovehandles and a heart attack? If you had half a brain you'd realize that nobody is going to be giving away something that can be used as fuel.
Why am I replying to an AC?
This occurred to me as well. Corn oil goes for a whopping $7.50 a gallon. Granted, edible oil would probably be of substantially higher quality that what you put in your gas tank.
To your claim that it needs diesel as well, there are engines that run on biodiesel alone. Greasel's FAQ states that diesel has to be used for warmup and shutdown. Perhaps more expensive conversions have solved this with electric fuel heaters and pumps.
-brian