Please. You can't file a class-action lawsuit. Only the federal government can do this. You can file a complaint, and hope the federal government decides it's actionable.
IBM has been doing things like this for years, and they likely have armor-plated their butts.
First it was having an 'indicator light' when the camera was in operation, and we were assured it was absolutey secure - until this came to light. () I read about someone who overcame a physical switch but have lost the link.
Nonetheless, I would not assume any physical switch on a computer. It's read and execution based on the sensor is still software (or firmware, or microcode).
It's not just the camera you need to protect. I used to carry a small audio adapter - plug it into the laptop and the built-in microphone is disabled. I got out of the habit, but the tape is always there.
I can find no workarounds for Chrome - posted in the chrome forum. Just wondered if anyone else was concerned enough to figure out how to disable it in Chrome until the library is updated.
From ldd output of/opt/google/chrome/chrome:
libgraphite2.so.3 =>/usr/lib64/libgraphite2.so.3 (0x00007fb69a34e000)
O/T: There was no Fed before 1913. However, we've had one form or another of a national bank for much longer; the story of how Andrew Jackson stared down Nicholas Biddle and put a leash on the Second Bank of the United States is quite a different story. Perhaps it was this which you attempted to reference...but even then, the BUS lost.
dAzED1, You're quite right in your facts. This is not something that your average techno-geek (or slashdot nerd) is going to grok or espouse, as you're seeing here. It something that will save enterprises (the larger the better) huge piles of money, while providing all the benefits you cite (and a few you have missed).
I'm riding this wave, too, but from the other side of the table. And Cloud - as an enabler - is bringing fantastic (in a business sense) and fascinating (in a technical sense) technologies to the realm of possibility.
The reason I'm replying, though, is to cast a bit of a cautionary note: not everything is cloud-ready or even cloud-friendly. Regulatory issues like BASEL II will make some information/applications impossible for public cloud. SPI (sensitive personal information) and 'classified' or 'confidential' information may never be put into a public cloud. And that's as it should be.
However, having said that, there are private cloud solutions and hybrid solutions that can be brought to bear.
"Cloud" is the foundation technology, the infrastructure enabler, as I see it, that will allow and even encourage this 'entirely new paradigm' to grow and flourish into an entirely new generation of technologies.
And the rate of adoption is just terrific; the interest is, as someone described it to me recently, so exciting it's scary. It will be some time before the field settles, but my money's on the global players who can bring virtually limitless resources to the problem.
Well, everyone's raving about your post. Am I the only one to hear you contradict yourself?
in the case of non-exempt employees, employers derive value from an employee
from the TIME the employee invests... burger joint... stay 5 extra minutes... the company was better off
in the case of exempt employees, employers derive value from the SERVICES that
an employee provides.... you're a doctor... the hospital pays you $7500
every time you perform a tonsilectomy... normally takes you 1.5 hours...
[say it] took you 5 hours to do it. the hospital does not have to pay more
than $7500 because it took you longer to do a tonsilectomy...From your description (which fits my own understanding, I'm an exempt
employee, salaried, etc), the following statement is bass ackwards:
"if you want it simple and easy, exempt employees get overtime and non-exempt
employees don't."Just thought I'd point it out. This is not the same as being a grammar nazi.
This is more like a semantic nazi:-D
All the same, interesting...
/b
Sun likely does not want the publicity they could get out of this.
If you've ever been in a data center with a Sun E10000 "enterprise class" box in a rack...then you'd know that you can't get within 5 feet of one of these beasts without feeling like you're being irradiated as you stand there. The heat just takes your breath away.
It's incredible. "Sun" isn't just a name...And, "global warming" due to "the Sun" (in the computer room...) got to be running jokes.
If nothing else, perhaps these processors will run cooler - they certainly can't run much hotter!
Let's see if I can respond without adding to the level of testosterone, then, as you've fairly obviously laid bare my passions:-)
Your statements appeared, given their narrow focus, to be short-sighted and to "entirely miss the point" of the larger issue of SOA. Your longish foray into reuse bled into statements regarding SOA in other contexts, yet was entirely based on the single web page you found.
It's not that this is my "favorite technology". But, there is much positive about it, and its arrival edges us closer to that day when architects design systems and business people then put together applications. Whether that day is tomorrow or 20 years from now.
I don't agree that my comments constituted an ad hominem attack, but if that's how you perceived them then I apologize.
"I was critiquing the article in question, and pointed out that it contained virtually nothing about how SOA was supposed to contribute to software reuse."
What I read in your statements was a condemnation of SOA in general before you were done, though you certainly started on the topic of reuse.
While you can (and people are certainly trying to) create tools that make software reuse easier, the simple fact of the matter is that anybody who wants to can avoid just about anything they choose.
Perhaps an unfortunate choice of words on my part. I used similar words in another post last night, and was called out on it there too, so I'll concede the point. However, note that the intent of SOA, and CBM, and ESB, and SOMA...is that there is policy, and enforcement, in addition to "tooling", a loaded term with which I intended to convey much more than just development tools, IDEs, or small utilities.
I have a solid technical foundation in SOA and related technologies as a J2EE architect; yet, I'm still a diehard UNIX admin and security guy. Nonetheless, I see the reality of what's coming with SOA, and it's going to be fascinating to live through it.
Working for one of the aforementioned software vendors in the SOA marketplace, I make a living talking to CIO's about this stuff. I would get thrown out by my ear in 5 seconds if I suggested that reuse is due to some kind of drag 'n drop GUI. That's patently ridiculous, and almost a cliche'. Angle-brackets and better data transformation / routing tools aren't going to bring about the reuse nirvana; you're just going to have a more maintainable set of "web services" that are marginally re-usable.
There are (chiefly) two ways to realize SOA - bottoms-up and top-down. Bottoms-up involves "organic" growth, where those closest to the data & functionality develop services, services which are sooner or later adapted into the more formalized structure that is created via top-down methods. It's possible to garner most of the benefits of SOA by bottoms-up methods - but not all. Reuse is difficult (as you and everyone else have pointed out), but it's by no means impossible!
And, yes, you would likely get thrown out on your ear by making an obtuse statement that a GUI would be the sole reason for reuse. On that point we agree. Please note that "supporting tools" need not be as simplistic as, nor restricted to, a "GUI".
Let me modify my statement slightly: SOA is neither an API nor a language binding.:-)
Perhaps another manner of analogy would help. SOA is not the same as Web Services, just as Web Services is not the same as SOAP. SOAP is a very minor part of Web Services, and Web Services is a very minor part of SOA. A CICS transaction on a mainframe can participate in a SOA and provide a service that is sold to external business partners, without entailing the use of SOAP or Web Services (though it would most commonly be fronted by a web service at some point, for many reasons). If you want to provide high availability, security, auditing, metrics, and perhaps QOS for all requesting traffic, then SOA is not only your "best" choice, it may be your only choice.
In a qualitative sense, I think you understand the "flavor" of SOA. One difference between the previous generations of change you describe and SOA is that there is API-based physical requirements like "call stack" or "parameter order" - that have all been abstracted away. There is no overriding requirement for security (it's provided for in the standards as a way of abstracting away the assumed security infrastructure in past generations - and note that assumptions nearly always translate to constraints or requirements).
Monitoring and control are well on the way to becoming realities - which, to someone as experienced as you seem to be, is an important fact. The technology has found acceptance and the supporting tools and technologies are now taking shape.
This is the longest rant I think I've ever seen that was composed based on zero knowledge of the technical subject at hand, but rather on some kind of on-the-fly interpretation of the three words "service" "oriented" and "architecture" used in juxtaposition.
Your points:
[...]being "service oriented" is roughly as new as dirt.
See above.
how in the world this would relate to software reuse
SOA makes software reuse not only easy but unavoidable - through tooling. See my other posts here for other thoughts in this vein, including use of ESB (Enterprise Service Bus).
...they haven't really told you anything about how to facilitate reuse in general, or how SOA is supposed to contribute to that...
Interesting. What else have you tried to read besides this sales-oriented (I call it marketecture) web page? Any actual technical articles?
More FUD. SOAP is an API. CORBA is an API (and more). SOA is not an API.
You don't "create" interfaces for SOA. You choose the correct granularity for a business service/component such that it can serve requests, without the need for state or context, from not just the local executing process in memory, but from anywhere within the enterprise.
And, when you specify the business service/component in such a way that it can serve requests, without the need for state or context, from anywhere, you now have the ability to turn software development from a cost center into a profit center (read: from anywhere, even outside the enterprise).
Regarding your second point - "easier" to reimplement and then refactor (!!!), if in your experience this is true, then all I can say is that XP (extreme programming) and SOA are going to be two huge wedges driven into the already-large chasm between the Cathedral and the Bazaaar - because SOA-based reuse will very likely turn out to be orders of magnitude more productive and profitable (ROI) than "refactoring" - especially after "reimplementing"!
SOA not only will work, it is already working. Companies are saving millions of dollars. Projects estimated at 6 weeks are getting done in 3 days. Projects estimated at days are getting done in an afternoon. Not all projects, of course (before someone "wisely" points this out). But...the world is changing. I could go into "business benefits" but that's not an approach I've seen used successfully on/. in the past...
Wait for it. The tools are coming or are already here - from all the major players (except Microsoft, but they cannot stop this juggernaut & will eventually join the rest of the bleeding-edge-world --- they've already come around in providing robust, genuinely-working.NET-to-Web Services interoperability with J2EE products).
The rest of the problems with SOA are the same ones that've been around ever since someone throught up remote procedure calls. If you aren't familiar with RPC and XDR, what makes you think you won't make the same mistakes and face the same problems this time around?
Because the APIs are not SOA. The APIs are independent of SOA. Say it with me - SOA is not an API.
A SOA does not require Java, nor SOAP. A SOA is an architecture - if you will, a "technique" of building software systems.
Because it is based on standards, there will be proliferation, and interoperability, and scale (look into the newest fledgling standard, ESB or Enterprise Service Bus - the paint is still wet, and it's not even recognized by OAGIS, OASIS, W3C, or IETF, but that will come).
For those who are not even superficially informed about SOA --- the things that SOA will be making possible are going to surprise you.
You know nothing of SOA. You post anon. You don't deserve a rating of 5 - I think "troll" would be more apropos.
This entire thread is full of FUD - but what's really scary to me is that this is/. where technologists theoretically hang out.
Yet, perhaps I should expect this kind of closed-mindedness, given how (mac|mike|php|mysql|ajax|...)-fans tend to just let 'er rip when it comes to the chance to blurt out an uninformed opinion.
Briefly, because I'm afraid I'm passing time in the same fashion as I would at a very, very bad movie - SOA is not going to impact you gamers. Nor you OSX types. Nor you windoze-lovin' 802.11G Cardbus types (you know, the ones Linux won't be supporting for a year or two?).
No, SOA is changing the business landscape in unbelievable ways. It's evolutionary, not revolutionary. The list of companies is impressive, and growing. And there is no looking back.
Points:
SOA is not "an API". It's an enterprise architecture. SOAP is an "API". JMS is an "API". Same for HTTP.
SOA does not stand alone, any more than SOAP does. SOA needs analysis (such as "CBM", or Component Business Modeling), and a common fabric (such as "ESB", or Enterprise Services Bus). Both are strongly recommended (read: required --- only fools will sneer at these).
The market is around US$10B this year, and according to Gartner (IIRC), it'll be US$95B in the next decade or so. That's Billion with a B.
Many companies are approaching this both top-down (CBM & ESB) but I suspect many more are doing it bottom-up (Web Services using SOAP over HTTP or HTTPS or JMS). My last two clients are doing it bottom-up, and they anticipate hundreds of Web Services in the next year or two. Reuse of "Web Services" can be nearly impossible, just as it has been for every technology/approach in the past. Reuse under SOA is virtually guaranteed - because the tools are graphically assembling the underlying services.
I don't know why I'm moved to post on this thread, usually I just ignore the rhetoric and the vitriol, and read the dozen or so interesting posts on any/. discussion thread that exceeds 100 replies...perhaps it was because I only saw one or two semi-literate or informed opinions tonight.
Jesus wept! Flame on if you like.
My son, 13, wants to be a game designer
on
Ask Sid Meier
·
· Score: 5, Interesting
This may get lost in the noise (5 pages long now and still growing) but I would like to know what to tell my son.
He plays games. He's never been interested in hardware. He doesn't know what an OS is, nor a programming language - yet.
However, becoming a game designer may not depend on these things...in the not-too-distant future.
Hearing about the feast-or-famine industry, where human resources are used up and discarded (to be replaced by the next eager candidate), I don't want my son to walk into this without a clue.
I'm a J2EE guy, I don't write or design games. There's too little room here to really put my question(s) into context, but I feel you'll understand where I'm coming from.
If true, that is one of the most damning links I've ever viewed.
I've had limited-skills techs working for me in the past - usually it's the "software testers" - who refer to disk as "memory", but to see it at a hardware review site is just incredible.
There's simply no other explanation than corruption. The site's not being phished. It might be a DNS poisoning attack, but I doubt it.
It may be a case where an "editorial board" saw a check and passed, unedited, unexamined even, a piece of dreck so obviously unworthy of publishing that the child who authored it - or the marketroid - would have received failing grade in Computer Science 101.
And, as if you could not guess, there is no byline. No name. No title, no email address.
This is the nuclear bomb for Tom's Hardware. Nothing less. It makes me sad - they have been around forever, and now they're dead to me.
I was a Tom's fan for years - I bought my BP6 (dual celerons), then my VP6 (dual P-III), based on Tom's say-so (along with a few others I trusted) - but no more:-(
Don't mod me up, mod the parent up - between 500,000 and 1,000,000 visitors to that horrible web page will cause Tom's to pull it, and for those multitudes to never again darken "Tom's Door".
Any opinions are mine alone, not those of the honest, ethical software/hardware/services multinational company for which I labor so assiduously.
Not bad, but could have been a bit better (?)
on
**No Title**
·
· Score: 1
I highlighted the space - thinking the text color was white. I was just a tad bit crestfallen that there was no text there...
But, maybe everyone did that right away, and maybe this was just a smidge better as a result.
I was a consultant for roughly 5 years. I'd been UNIX Systems Manager at a huge company. I had staff. I was Somebody.
Then I went back to University (U.S., State Univ) on an "assistantship" (read: 'free ride') and practically burned the place down:-)
Once you've had a "down system", like a 24-processor AT&T that's having the "stiction problem" with 40 IBM hard drives in 8 RAID-5 LUNs and you run a 5-man crew 24x7 (since you could NOT allow those drives to spin down, you had to fix the system while it was running) --- and get it back in service over a Friday night, all day Saturday, and half of Sunday....well, sitting in a classroom listening to a professor read^H^H^H^H pontificate from their own book is very hard to take. Especially when you know that in the real world, the "knowledge" the professor is imparting will actually hurt the kids who are absorbing it...
Hearing students then parrot that professor does not help. I'm a "mentor" type, so I tried to help. Gratitude? They reacted angrily (the students, not the professor!).
Group assignments? There's always a loudmouth who has just the tiniest grasp of the subject and yet feels they simply must "lead" by talking - and when you step up to the natural leadership role, they don't run to the professor, but to the Dean of the Department of Computer Science.
I soon found myself having my second one-on-one "interview" with the Dean of the Department of Computer Science <BEG>.
Small lesson from my pain: lower your ego-meter. Bite your tongue. Practically in half.
Of course, once I proved I wasn't full of hot air, I developed a following, just as I've done wherever I go. But, at the beginning, it was enough that I almost gave up.
Oh, and the $15K kick the moment I left the school with the Master's degree was definitely satisfying. This was mid-90s, so I'm not sure if THAT rule still applies...good luck!
It won't matter what purpose the first robots are intended to serve. The company that brings out the first robot for the household had better pour millions into testing, and produce a robot that is damn near flawless.
Or they'll kill the industry before it even truly starts to exist.
Imagine a robot that accidentally elecrocutes 150 young children by dropping a hair dryer into the tub at approximately 7:30pm all across the country (US, Japan, wherever) due to a "bug" in software/firmware.
Slashdot Mirror
Please. You can't file a class-action lawsuit. Only the federal government can do this. You can file a complaint, and hope the federal government decides it's actionable. IBM has been doing things like this for years, and they likely have armor-plated their butts.
First it was having an 'indicator light' when the camera was in operation, and we were assured it was absolutey secure - until this came to light. () I read about someone who overcame a physical switch but have lost the link.
Nonetheless, I would not assume any physical switch on a computer. It's read and execution based on the sensor is still software (or firmware, or microcode).
It's not just the camera you need to protect. I used to carry a small audio adapter - plug it into the laptop and the built-in microphone is disabled. I got out of the habit, but the tape is always there.
Wish I had mod points today. Thank you.
I can find no workarounds for Chrome - posted in the chrome forum. Just wondered if anyone else was concerned enough to figure out how to disable it in Chrome until the library is updated. /opt/google/chrome/chrome: /usr/lib64/libgraphite2.so.3 (0x00007fb69a34e000)
From ldd output of
libgraphite2.so.3 =>
O/T: There was no Fed before 1913. However, we've had one form or another of a national bank for much longer; the story of how Andrew Jackson stared down Nicholas Biddle and put a leash on the Second Bank of the United States is quite a different story. Perhaps it was this which you attempted to reference...but even then, the BUS lost.
I'm riding this wave, too, but from the other side of the table. And Cloud - as an enabler - is bringing fantastic (in a business sense) and fascinating (in a technical sense) technologies to the realm of possibility.
The reason I'm replying, though, is to cast a bit of a cautionary note: not everything is cloud-ready or even cloud-friendly. Regulatory issues like BASEL II will make some information/applications impossible for public cloud. SPI (sensitive personal information) and 'classified' or 'confidential' information may never be put into a public cloud. And that's as it should be.
However, having said that, there are private cloud solutions and hybrid solutions that can be brought to bear.
"Cloud" is the foundation technology, the infrastructure enabler, as I see it, that will allow and even encourage this 'entirely new paradigm' to grow and flourish into an entirely new generation of technologies.
And the rate of adoption is just terrific; the interest is, as someone described it to me recently, so exciting it's scary. It will be some time before the field settles, but my money's on the global players who can bring virtually limitless resources to the problem.
Well, everyone's raving about your post. Am I the only one to hear you contradict yourself? ... burger joint ... stay 5 extra minutes ... the company was better off
in the case of exempt employees, employers derive value from the SERVICES that
an employee provides. ... you're a doctor ... the hospital pays you $7500
every time you perform a tonsilectomy ... normally takes you 1.5 hours ...
[say it] took you 5 hours to do it. the hospital does not have to pay more
than $7500 because it took you longer to do a tonsilectomy ...From your description (which fits my own understanding, I'm an exempt
employee, salaried, etc), the following statement is bass ackwards:
"if you want it simple and easy, exempt employees get overtime and non-exempt
employees don't."Just thought I'd point it out. This is not the same as being a grammar nazi.
This is more like a semantic nazi :-D
/b
in the case of non-exempt employees, employers derive value from an employee from the TIME the employee invests
All the same, interesting...
Altavista came up with "The Slashdot is a giant wheel, but it is not a diversion park". That does not look right :-)
What's it mean - what did you intend? Just curious...
Sun likely does not want the publicity they could get out of this. If you've ever been in a data center with a Sun E10000 "enterprise class" box in a rack...then you'd know that you can't get within 5 feet of one of these beasts without feeling like you're being irradiated as you stand there. The heat just takes your breath away.
It's incredible. "Sun" isn't just a name...And, "global warming" due to "the Sun" (in the computer room...) got to be running jokes.
If nothing else, perhaps these processors will run cooler - they certainly can't run much hotter!
Just my $0.02.
See Volume 49, Number 2/3, 2005.
IBM in Asia did some interesting research in 2004 - indoors, using WiFi...
Wireless LAN-based indoor positioning technology
Let's see if I can respond without adding to the level of testosterone, then, as you've fairly obviously laid bare my passions :-)
Your statements appeared, given their narrow focus, to be short-sighted and to "entirely miss the point" of the larger issue of SOA. Your longish foray into reuse bled into statements regarding SOA in other contexts, yet was entirely based on the single web page you found.
It's not that this is my "favorite technology". But, there is much positive about it, and its arrival edges us closer to that day when architects design systems and business people then put together applications. Whether that day is tomorrow or 20 years from now.
I don't agree that my comments constituted an ad hominem attack, but if that's how you perceived them then I apologize.
What I read in your statements was a condemnation of SOA in general before you were done, though you certainly started on the topic of reuse. Perhaps an unfortunate choice of words on my part. I used similar words in another post last night, and was called out on it there too, so I'll concede the point. However, note that the intent of SOA, and CBM, and ESB, and SOMA...is that there is policy, and enforcement, in addition to "tooling", a loaded term with which I intended to convey much more than just development tools, IDEs, or small utilities.I have a solid technical foundation in SOA and related technologies as a J2EE architect; yet, I'm still a diehard UNIX admin and security guy. Nonetheless, I see the reality of what's coming with SOA, and it's going to be fascinating to live through it.
There are (chiefly) two ways to realize SOA - bottoms-up and top-down. Bottoms-up involves "organic" growth, where those closest to the data & functionality develop services, services which are sooner or later adapted into the more formalized structure that is created via top-down methods. It's possible to garner most of the benefits of SOA by bottoms-up methods - but not all. Reuse is difficult (as you and everyone else have pointed out), but it's by no means impossible!
And, yes, you would likely get thrown out on your ear by making an obtuse statement that a GUI would be the sole reason for reuse. On that point we agree. Please note that "supporting tools" need not be as simplistic as, nor restricted to, a "GUI".
Let me modify my statement slightly: SOA is neither an API nor a language binding. :-)
Perhaps another manner of analogy would help. SOA is not the same as Web Services, just as Web Services is not the same as SOAP. SOAP is a very minor part of Web Services, and Web Services is a very minor part of SOA. A CICS transaction on a mainframe can participate in a SOA and provide a service that is sold to external business partners, without entailing the use of SOAP or Web Services (though it would most commonly be fronted by a web service at some point, for many reasons). If you want to provide high availability, security, auditing, metrics, and perhaps QOS for all requesting traffic, then SOA is not only your "best" choice, it may be your only choice.
In a qualitative sense, I think you understand the "flavor" of SOA. One difference between the previous generations of change you describe and SOA is that there is API-based physical requirements like "call stack" or "parameter order" - that have all been abstracted away. There is no overriding requirement for security (it's provided for in the standards as a way of abstracting away the assumed security infrastructure in past generations - and note that assumptions nearly always translate to constraints or requirements).
Monitoring and control are well on the way to becoming realities - which, to someone as experienced as you seem to be, is an important fact. The technology has found acceptance and the supporting tools and technologies are now taking shape.
This is the longest rant I think I've ever seen that was composed based on zero knowledge of the technical subject at hand, but rather on some kind of on-the-fly interpretation of the three words "service" "oriented" and "architecture" used in juxtaposition.
Your points:
- [...]being "service oriented" is roughly as new as dirt.
- how in the world this would relate to software reuse
...they haven't really told you anything about how to facilitate reuse in general, or how SOA is supposed to contribute to that...
Here, try these:Service-oriented architecture - Wikipedia
webservices.xml.com: What is Service-Oriented Architecture?
Service-oriented architecture (SOA) definition
Loosely Coupled monthly digest -- July 2004 (ESB)
ESB Fills Management Gaps for Web Services
More FUD. SOAP is an API. CORBA is an API (and more). SOA is not an API.
You don't "create" interfaces for SOA. You choose the correct granularity for a business service/component such that it can serve requests, without the need for state or context, from not just the local executing process in memory, but from anywhere within the enterprise.
And, when you specify the business service/component in such a way that it can serve requests, without the need for state or context, from anywhere, you now have the ability to turn software development from a cost center into a profit center (read: from anywhere, even outside the enterprise).
Regarding your second point - "easier" to reimplement and then refactor (!!!), if in your experience this is true, then all I can say is that XP (extreme programming) and SOA are going to be two huge wedges driven into the already-large chasm between the Cathedral and the Bazaaar - because SOA-based reuse will very likely turn out to be orders of magnitude more productive and profitable (ROI) than "refactoring" - especially after "reimplementing"!
SOA not only will work, it is already working. Companies are saving millions of dollars. Projects estimated at 6 weeks are getting done in 3 days. Projects estimated at days are getting done in an afternoon. Not all projects, of course (before someone "wisely" points this out). But...the world is changing. I could go into "business benefits" but that's not an approach I've seen used successfully on /. in the past...
Wait for it. The tools are coming or are already here - from all the major players (except Microsoft, but they cannot stop this juggernaut & will eventually join the rest of the bleeding-edge-world --- they've already come around in providing robust, genuinely-working .NET-to-Web Services interoperability with J2EE products).
Because the APIs are not SOA. The APIs are independent of SOA. Say it with me - SOA is not an API.
A SOA does not require Java, nor SOAP. A SOA is an architecture - if you will, a "technique" of building software systems.
Because it is based on standards, there will be proliferation, and interoperability, and scale (look into the newest fledgling standard, ESB or Enterprise Service Bus - the paint is still wet, and it's not even recognized by OAGIS, OASIS, W3C, or IETF, but that will come).
For those who are not even superficially informed about SOA --- the things that SOA will be making possible are going to surprise you.
SOA is not "runtime reuse".
You know nothing of SOA. You post anon. You don't deserve a rating of 5 - I think "troll" would be more apropos.
This entire thread is full of FUD - but what's really scary to me is that this is /. where technologists theoretically hang out.
Yet, perhaps I should expect this kind of closed-mindedness, given how (mac|mike|php|mysql|ajax|...)-fans tend to just let 'er rip when it comes to the chance to blurt out an uninformed opinion.
Briefly, because I'm afraid I'm passing time in the same fashion as I would at a very, very bad movie - SOA is not going to impact you gamers. Nor you OSX types. Nor you windoze-lovin' 802.11G Cardbus types (you know, the ones Linux won't be supporting for a year or two?).
No, SOA is changing the business landscape in unbelievable ways. It's evolutionary, not revolutionary. The list of companies is impressive, and growing. And there is no looking back.
Points:
Many companies are approaching this both top-down (CBM & ESB) but I suspect many more are doing it bottom-up (Web Services using SOAP over HTTP or HTTPS or JMS). My last two clients are doing it bottom-up, and they anticipate hundreds of Web Services in the next year or two. Reuse of "Web Services" can be nearly impossible, just as it has been for every technology/approach in the past. Reuse under SOA is virtually guaranteed - because the tools are graphically assembling the underlying services.
I don't know why I'm moved to post on this thread, usually I just ignore the rhetoric and the vitriol, and read the dozen or so interesting posts on any /. discussion thread that exceeds 100 replies...perhaps it was because I only saw one or two semi-literate or informed opinions tonight.
Jesus wept! Flame on if you like.
This may get lost in the noise (5 pages long now and still growing) but I would like to know what to tell my son.
He plays games. He's never been interested in hardware. He doesn't know what an OS is, nor a programming language - yet.
However, becoming a game designer may not depend on these things...in the not-too-distant future.
Hearing about the feast-or-famine industry, where human resources are used up and discarded (to be replaced by the next eager candidate), I don't want my son to walk into this without a clue.
I'm a J2EE guy, I don't write or design games. There's too little room here to really put my question(s) into context, but I feel you'll understand where I'm coming from.
What would you tell my son?
Thanks.
If true, that is one of the most damning links I've ever viewed.
I've had limited-skills techs working for me in the past - usually it's the "software testers" - who refer to disk as "memory", but to see it at a hardware review site is just incredible .
There's simply no other explanation than corruption. The site's not being phished. It might be a DNS poisoning attack, but I doubt it.
It may be a case where an "editorial board" saw a check and passed, unedited, unexamined even, a piece of dreck so obviously unworthy of publishing that the child who authored it - or the marketroid - would have received failing grade in Computer Science 101.
And, as if you could not guess, there is no byline. No name. No title, no email address.
This is the nuclear bomb for Tom's Hardware. Nothing less. It makes me sad - they have been around forever, and now they're dead to me.
I was a Tom's fan for years - I bought my BP6 (dual celerons), then my VP6 (dual P-III), based on Tom's say-so (along with a few others I trusted) - but no more :-(
Don't mod me up, mod the parent up - between 500,000 and 1,000,000 visitors to that horrible web page will cause Tom's to pull it, and for those multitudes to never again darken "Tom's Door".
Any opinions are mine alone, not those of the honest, ethical software/hardware/services multinational company for which I labor so assiduously.
I highlighted the space - thinking the text color was white. I was just a tad bit crestfallen that there was no text there ...
But, maybe everyone did that right away, and maybe this was just a smidge better as a result.
"Too smart for my own good..." comes to mind :)
I'm out, right away. I have a background in usability, and I have "capslock" disabled in all my winders and linux boxen.
This means I can come in, but I can't get out....oh well. I don't need it that badly.
I was a consultant for roughly 5 years. I'd been UNIX Systems Manager at a huge company. I had staff. I was Somebody.
Then I went back to University (U.S., State Univ) on an "assistantship" (read: 'free ride') and practically burned the place down :-)
Once you've had a "down system", like a 24-processor AT&T that's having the "stiction problem" with 40 IBM hard drives in 8 RAID-5 LUNs and you run a 5-man crew 24x7 (since you could NOT allow those drives to spin down, you had to fix the system while it was running) --- and get it back in service over a Friday night, all day Saturday, and half of Sunday....well, sitting in a classroom listening to a professor read^H^H^H^H pontificate from their own book is very hard to take. Especially when you know that in the real world, the "knowledge" the professor is imparting will actually hurt the kids who are absorbing it...
Hearing students then parrot that professor does not help. I'm a "mentor" type, so I tried to help. Gratitude? They reacted angrily (the students, not the professor!).
Group assignments? There's always a loudmouth who has just the tiniest grasp of the subject and yet feels they simply must "lead" by talking - and when you step up to the natural leadership role, they don't run to the professor, but to the Dean of the Department of Computer Science. I soon found myself having my second one-on-one "interview" with the Dean of the Department of Computer Science <BEG>.
Small lesson from my pain: lower your ego-meter. Bite your tongue. Practically in half.
Of course, once I proved I wasn't full of hot air, I developed a following, just as I've done wherever I go. But, at the beginning, it was enough that I almost gave up.
Oh, and the $15K kick the moment I left the school with the Master's degree was definitely satisfying. This was mid-90s, so I'm not sure if THAT rule still applies...good luck!
It won't matter what purpose the first robots are intended to serve. The company that brings out the first robot for the household had better pour millions into testing, and produce a robot that is damn near flawless.
Or they'll kill the industry before it even truly starts to exist.
Imagine a robot that accidentally elecrocutes 150 young children by dropping a hair dryer into the tub at approximately 7:30pm all across the country (US, Japan, wherever) due to a "bug" in software/firmware.
When I read the home page, my first thoughts, in rapid-fire fashion: That headline should have been "Half Life 2, Stuttering, Bug Officials".
Or perhaps "Half Life 2, Stuttering, Bugs Official".
Stuttering bugs me too. I s-s-s-sometimes do s-s-s-stutter, but it's usually when I'm with my wife and we see a truly stunning w-w-w-w-uh girl!
8-)