Standard? Um we're talking about RFIDs here. Each manufacturer has their own little twist on things. You may get someone to cough up which manufacturer they use - if they know. Then you're only looking at a few antenna/scanner combinations. But, as for doing something like "war-walking" good luck with that.
Problem with that idea is antennas are specific to the type of RFID technology used. So you'd probably need a collection of dozens of scanner and antenna combinations to pull that off.
Your experience is essentially the opposite of mine. I (now) use eclipse on OSX as my primary development environment. It works nearly flawlessly. I can't say the same for eclipse on windows. Then again, I'm using a pile of eclipse extensions, maybe you're not. Just thought I'd chime in with my $.02.
Okay off-topic for the article, but not the parent.
Should be a -- or a simple,.
Semi-colon replaces a conjunction,
you can't place a conjunction where the colon is.
Colon is generally used to denote "read ahead
more detail comming" usually used where an
itemized list, quotation or other such construct
is used. This is just a simple
dramatic pause so either a -- or , will suffice.
Even if it entered the court record it would still retain its copyright (assuming its valid in the first place). This is most definately NOT a reasonable request.
In 1989 he was awarded Most Popular and Best Selling Artist of the Year in Germany and was invited to perform 'Freedom' on the Berlin Wall New Year's Eve 1989.
Without the rampant piracy of the early releases of windows, MS would not have the monopoly it has today.
MS's complaints about piracy always ring a tad bit ironic to me.
Meaning if you switch over to another OS now you don't end up oweing SCO the full license for linux ($699 or something) that they're claiming you now owe. You'll probably just end up oweing a mere $500 (or whatever - even I couldn't stomach reading the details on that in the article).
Like another poster said, it depends on what part of J2EE you're talking about here. In general, J2EE components rely on containers (specific to the component) which do a lot of lifting for you.
I'm unaware of any C/C++ implementation of an EJB container for instance. However with the Axis C/C++ implementation (notice I've segue'd back into the topic here), it opens up the possibility of a C/C++ client talking to a SOAP-wrapped J2EE server tier.
I used to be a pretty heavy C++ guy back in the day. I've been doing almost exclusively Java for the last (gawd!) 7 or so years. I really don't miss C++ at all. Especially the maintenance headaches induced by implementations of large domain models. The larger the model the more it seemed to spin out of control with C++. It still has a tendency to spin out of control with Java, but not to the same degree.
One thing I haven't seen is comparisons regarding energy costs for the various solutions. This would, of course, include AC costs (including initial costs of the larger AC unit) as well. With the reduced energy consumption of the PowerPC series I imagine this could be another substantial savings.
"The adoption of Java was based on Web development"
What? Adoption of Java is based on platform portability and scalable distributed enterprise computing. (With the.NET dirty little secret of: if you want to do anything meaningful you still have to use COM/COM+).NET is neither.
Pish-tosh. Now, the adoption of Perl WAS based on web development.
Its a pity the article doesn't go into EOF (Enterprise Object Framework) and WebObjects. Two of the real crowning-achievements of the folks at NeXT. EOF was the first usable Object-Relational mapper and, in my opionion, still the only usable one. While WebObjects combined with EOF was the pre-cursor to the whole n-tier application-server thing.
I was really disappointed for OSX for unix geeks.
This book should be titled OS X for Unix newbies. I expected more of a cross-reference style approach:
Here's how you do it in *nix Here's how you do it in OS X.
What I got was some very basic Unix tutorials. My NextStep 0.8 documentation (circa '87) is MUCH more helpful than this book.
Slashdot Mirror
Standard? Um we're talking about RFIDs here. Each manufacturer has their own little twist on things. You may get someone to cough up which manufacturer they use - if they know. Then you're only looking at a few antenna/scanner combinations. But, as for doing something like "war-walking" good luck with that.
Problem with that idea is antennas are specific to the type of RFID technology used. So you'd probably need a collection of dozens of scanner and antenna combinations to pull that off.
Nice idea though.
Your experience is essentially the opposite of mine. I (now) use eclipse on OSX as my primary development environment. It works nearly flawlessly. I can't say the same for eclipse on windows. Then again, I'm using a pile of eclipse extensions, maybe you're not. Just thought I'd chime in with my $.02.
Okay off-topic for the article, but not the parent. Should be a -- or a simple ,.
Semi-colon replaces a conjunction,
you can't place a conjunction where the colon is.
Colon is generally used to denote "read ahead
more detail comming" usually used where an
itemized list, quotation or other such construct
is used. This is just a simple
dramatic pause so either a -- or , will suffice.
Even if it entered the court record it would still retain its copyright (assuming its valid in the first place). This is most definately NOT a reasonable request.
The real reason apple pulled rhapsody off the market(the x86 pre-cursor to OSX) was fear of MS pulling office apps.
Personally, I just call it Ishmael.
Hasselhoff:
:)
In 1989 he was awarded Most Popular and Best Selling Artist of the Year in Germany and was invited to perform 'Freedom' on the Berlin Wall New Year's Eve 1989.
I rest my case.
I'm betting if they invited David Hasselhoff as a guest lecturer the strike would be that much more effective.
'cuz we all know: Germans love David Hasselhoff.
Without the rampant piracy of the early releases of windows, MS would not have the monopoly it has today. MS's complaints about piracy always ring a tad bit ironic to me.
I concur. Is this a book about _how_ to evaluate frameworks, or does it actually evaluate some. The review is sorely lacking.
"there were 17 critical vulnerabilities. For Windows Server 2003, there were four. For Red Hat Linux 6, they were five to ten times higher"
Red Hat 6? Steve, do a little research here. We're at 9.x now.
Let's compare apples to apples RH 6 was around during NT4 right? Now, let's count the security holes.
SCO is offering _discounts_ on licenses.
Meaning if you switch over to another OS now you don't end up oweing SCO the full license for linux ($699 or something) that they're claiming you now owe. You'll probably just end up oweing a mere $500 (or whatever - even I couldn't stomach reading the details on that in the article).
For god sakes. If they come across a large black obilisk, please leave it alone and put it back. You just don't know where those things have been.
Like another poster said, it depends on what part of J2EE you're talking about here. In general, J2EE components rely on containers (specific to the component) which do a lot of lifting for you.
I'm unaware of any C/C++ implementation of an EJB container for instance. However with the Axis C/C++ implementation (notice I've segue'd back into the topic here), it opens up the possibility of a C/C++ client talking to a SOAP-wrapped J2EE server tier.
I used to be a pretty heavy C++ guy back in the day. I've been doing almost exclusively Java for the last (gawd!) 7 or so years. I really don't miss C++ at all. Especially the maintenance headaches induced by implementations of large domain models. The larger the model the more it seemed to spin out of control with C++. It still has a tendency to spin out of control with Java, but not to the same degree.
I could go on here, but I think I've said enough.
One thing I haven't seen is comparisons regarding energy costs for the various solutions. This would, of course, include AC costs (including initial costs of the larger AC unit) as well. With the reduced energy consumption of the PowerPC series I imagine this could be another substantial savings.
You're all forgetting the "Collect Underpants" phase of this evil scheme.
.com bubble bursting. Nobody was collecting underpants, and thus no profits.
This is the key that lead to the
Are we all so destined to repeat history?
"The adoption of Java was based on Web development"
.NET dirty little secret of: if you want to do anything meaningful you still have to use COM/COM+) .NET is neither.
What? Adoption of Java is based on platform portability and scalable distributed enterprise computing. (With the
Pish-tosh. Now, the adoption of Perl WAS based on web development.
*ducks*
Combine all that with nutritional information harvested from grocery store loyalty systems and you've got a real predictor there.
Its a pity the article doesn't go into EOF (Enterprise Object Framework) and WebObjects. Two of the real crowning-achievements of the folks at NeXT. EOF was the first usable Object-Relational mapper and, in my opionion, still the only usable one. While WebObjects combined with EOF was the pre-cursor to the whole n-tier application-server thing.
Perhaps you should read the replies the last time you posted this exact same message.
If you're going to troll at least put some effort into it.
Forget about 2,000lb man. What's a 200lb weakling?
Manhole covers are round because they cover round holes.
I just don't understand the big mystery behind that one.
I was really disappointed for OSX for unix geeks. This book should be titled OS X for Unix newbies. I expected more of a cross-reference style approach: Here's how you do it in *nix Here's how you do it in OS X. What I got was some very basic Unix tutorials. My NextStep 0.8 documentation (circa '87) is MUCH more helpful than this book.
They're hugely different - defaults can be, and usually are changed.
Take a look at the list again:
How many NT servers have Administrator/administrator.
Or root/ on linux?
Or even the ubiquetous scott/tiger account in Oracle.
I was looking on that list for actual back doors on systems I have (thought I should be aware). There were none! Just the defaults I've changed.