Really, I don't see anything wrong with using Java to write web apps. The problem is when all the 30 different libraries, frameworks, extensions, etc. get thrown in. I steer clear of anything that even mentions Hibernate, Spring (esp. AOP), and any mix of more than about 4 different technologies.
Sounds like your coworkers are busily filling out their resumes with all the latest fad software tools. Like you, I despise such thinking, and it's why I pass on any job opportunity where 'web apps' and 'java' are used in the same description.
Good point. I hadn't considered the multi-device situation for a single user. Like I said, it's all very preliminary ideas at the moment (having started work on any of the implementation yet).
This article is very timely for me. I'm an iPhone developer who's planning to add a server component for some of my iPhone apps. My initial thinking was to simply make use of the built-in UDID since it's there and doesn't require any effort on the part of the user. I did RTFA and I can see how the use of UDIDs could lead to unethical situations.
On the other hand, what's the alternative? Generally speaking, an iPhone app that has a server component with functionality that's geared to a specific user needs something to identify that user. Sure, I could force the user to enter their email address or make up a user id. Unless a user goes to the trouble of making sure that each service/app they deal with uses a separate and distinct user id or email address, you're back in the same situation (or close to it).
I'm genuinely interested in hearing suggestions on the preferred mechanism that helps to maintain privacy.
Really, since when does IBM care about what happens in the U.S.? Aren't they the same company that recently told some of their top researchers that they could either move to China, Poland, or a couple of other countries on their own dime and work for 'local wages' or be out of a job?
These systems are extremely impressive. The hypervisor functionality by itself is amazing. Too bad IBM doesn't know how to market these systems very well.
Linux guests running under z/VM has nothing to do with z/OS. z/VM doesn't (and never has, AFAIK) run inside z/OS. z/OS, as with other mainframe operating systems, can run inside (as a guest of) z/VM. z/VM can even run as a guest of z/VM (2nd level). Linux for z-Series can also run "bare metal" on an LPAR. Again, z/OS is not involved.
You mentioned some cool things, but none of them have anything to do with z/OS. You're talking about the magic of z/VM and Linux guests.
Yeah, a brain implant might be the state of the art for some operating systems, but a lobotomy is probably the more appropriate procedure for Windows users.
In my experience, whether one is treated like "blue collar" or "white collar" has more to do with the culture of the organization and less to do with whether the developer has a certain degree or not.
I agree with you regarding Apple's marketing and overhyping 64-bit. IMO, they made it out to be more important than it really is for most folks. Even so, I realize that having a 32-bit kernel makes some people feel "cheated" by Apple. Looking at the situation objectively though, no one has yet been able to state what the user of a 32-bit kernel will be missing out on, except the bragging rights and the "cheated" feeling. There is a downside of having a 64-bit environment too -- namely more memory consumption.
Besides the general tuning that Apple has done throughout, I believe that Grand Central Dispatch will be one of the biggest benefits of SL. Of course, the benefit will be realized more and more over time, as software is rewritten to take advantage of it. For most of the folks with high-end Mac Pros, I really believe that this will be more beneficial over the long haul than having 64-bit parts. OpenCL will likely have significant benefit for certain applications.
Take a look at Bob Dylan's lyrics from "Union Sundown" (on his 1983 album 'Infidels'). I won't post all of the lyrics here, lest the copyright police try to bust me. But seriously, have a look at the lyrics of this song. Here's the chorus: Well, it's sundown on the union And what's made in the U.S.A. Sure was a good idea 'Til greed got in the way.
True, but that's not how it was marketed. There was lots of marketing hype about it being the first "supercomputer on a chip" (or something to that effect). If Intel's goal was only to sell it for specialized uses, why would they have bothered to generate all the hype?
Intel even made a "supercomputer" using the i860 (they had a version of their nCube that used the i860). All in all, I'd call it a flop. It seems that Intel thought that they would own the scientific, engineering, and academic markets with the i860.
It looks like one of the supercomputers that Intel released using the i860 was the Intel iPSC/860.
True, but that's not how it was marketed. There was lots of marketing hype about it being the first "supercomputer on a chip" (or something to that effect). If Intel's goal was only to sell it for specialized uses, why would they have bothered to generate all the hype?
Intel even made a "supercomputer" using the i860 (they had a version of their nCube that used the i860). All in all, I'd call it a flop. It seems that Intel thought that they would own the scientific, engineering, and academic markets with the i860.
but another to know what to do with it. Also, it wouldn't be that hard for them to build a distributed supercomputer using older systems on a LAN with MPI or PVM.
Slashdot Mirror
Really, I don't see anything wrong with using Java to write web apps. The problem is when all the 30 different libraries, frameworks, extensions, etc. get thrown in. I steer clear of anything that even mentions Hibernate, Spring (esp. AOP), and any mix of more than about 4 different technologies.
Sounds like your coworkers are busily filling out their resumes with all the latest fad software tools. Like you, I despise such thinking, and it's why I pass on any job opportunity where 'web apps' and 'java' are used in the same description.
Good point. I hadn't considered the multi-device situation for a single user. Like I said, it's all very preliminary ideas at the moment (having started work on any of the implementation yet).
This article is very timely for me. I'm an iPhone developer who's planning to add a server component for some of my iPhone apps. My initial thinking was to simply make use of the built-in UDID since it's there and doesn't require any effort on the part of the user. I did RTFA and I can see how the use of UDIDs could lead to unethical situations.
On the other hand, what's the alternative? Generally speaking, an iPhone app that has a server component with functionality that's geared to a specific user needs something to identify that user. Sure, I could force the user to enter their email address or make up a user id. Unless a user goes to the trouble of making sure that each service/app they deal with uses a separate and distinct user id or email address, you're back in the same situation (or close to it).
I'm genuinely interested in hearing suggestions on the preferred mechanism that helps to maintain privacy.
Really, since when does IBM care about what happens in the U.S.? Aren't they the same company that recently told some of their top researchers that they could either move to China, Poland, or a couple of other countries on their own dime and work for 'local wages' or be out of a job?
The server was then heard to be mumbling "knockin' on heaven's door".
Mod parent up.
These systems are extremely impressive. The hypervisor functionality by itself is amazing. Too bad IBM doesn't know how to market these systems very well.
Linux guests running under z/VM has nothing to do with z/OS. z/VM doesn't (and never has, AFAIK) run inside z/OS. z/OS, as with other mainframe operating systems, can run inside (as a guest of) z/VM. z/VM can even run as a guest of z/VM (2nd level). Linux for z-Series can also run "bare metal" on an LPAR. Again, z/OS is not involved.
You mentioned some cool things, but none of them have anything to do with z/OS. You're talking about the magic of z/VM and Linux guests.
I'd be happy to help with the Cocoa work, though I don't have any specific knowledge or experience with audio/video processing.
paul at swampbits dot com
Yeah, a brain implant might be the state of the art for some operating systems, but a lobotomy is probably the more appropriate procedure for Windows users.
In my experience, whether one is treated like "blue collar" or "white collar" has more to do with the culture of the organization and less to do with whether the developer has a certain degree or not.
Normal folks think of aliens as being extraterrestrial. In this case, it's probably a study of non-Catholics.
Tell you what kids, try learning something for a change. And show some respect.
And get off my lawn.
I agree with you regarding Apple's marketing and overhyping 64-bit. IMO, they made it out to be more important than it really is for most folks. Even so, I realize that having a 32-bit kernel makes some people feel "cheated" by Apple. Looking at the situation objectively though, no one has yet been able to state what the user of a 32-bit kernel will be missing out on, except the bragging rights and the "cheated" feeling. There is a downside of having a 64-bit environment too -- namely more memory consumption.
Besides the general tuning that Apple has done throughout, I believe that Grand Central Dispatch will be one of the biggest benefits of SL. Of course, the benefit will be realized more and more over time, as software is rewritten to take advantage of it. For most of the folks with high-end Mac Pros, I really believe that this will be more beneficial over the long haul than having 64-bit parts. OpenCL will likely have significant benefit for certain applications.
Thanks for your comments. What are your overall thoughts about Grand Central Dispatch? Thanks in advance.
Take a look at Bob Dylan's lyrics from "Union Sundown" (on his 1983 album 'Infidels'). I won't post all of the lyrics here, lest the copyright police try to bust me. But seriously, have a look at the lyrics of this song. Here's the chorus:
Well, it's sundown on the union
And what's made in the U.S.A.
Sure was a good idea
'Til greed got in the way.
Hmmm.... Every known star in the universe with it's own ip address. Now I think that the promise of cloud computing is finally starting to dawn on me!
... ESX shop with about 300 guest VM's on five host ...
What kind of servers do you use for the hosts? How many cpus and how much physical ram in the boxes?
Also, what would be the average memory size defined for each guest?
The funny part is that (very deep) under the covers, the zSeries processor is a modified PowerPC running microcode.
Not exactly. It's true that the z10's processor borrows some of the design from the Power6 chip, but they're not the same chip.
True, but that's not how it was marketed. There was lots of marketing hype about it being the first "supercomputer on a chip" (or something to that effect). If Intel's goal was only to sell it for specialized uses, why would they have bothered to generate all the hype?
Intel even made a "supercomputer" using the i860 (they had a version of their nCube that used the i860). All in all, I'd call it a flop. It seems that Intel thought that they would own the scientific, engineering, and academic markets with the i860.
It looks like one of the supercomputers that Intel released using the i860 was the Intel iPSC/860.
True, but that's not how it was marketed. There was lots of marketing hype about it being the first "supercomputer on a chip" (or something to that effect). If Intel's goal was only to sell it for specialized uses, why would they have bothered to generate all the hype?
Intel even made a "supercomputer" using the i860 (they had a version of their nCube that used the i860). All in all, I'd call it a flop. It seems that Intel thought that they would own the scientific, engineering, and academic markets with the i860.
they dropped a Coke bottle from the helicopter and it happened to land within the tribe area. ("The Gods Must Be Crazy")
but another to know what to do with it. Also, it wouldn't be that hard for them to build a distributed supercomputer using older systems on a LAN with MPI or PVM.
carbon dating? Sorry, couldn't resist.
From TFA,
The topic is specifically about virtualization on the x86 platform.