Field worker: mobile phone, tablet, or laptop (applications can be native, web-based, or hybrid) On-site worker: a combination of several in many cases (native, web-based, or hybrid)
Indeed. Sounds to me like OP is asking to get fired or blacklisted as soon as management gets wind of the plans. I wouldn't even broach the subject with them. The downsides far outweigh any benefits and if nothing else it's highly unethical.
My memory is also failing! You're correct - it was limited to Win16 and Win32S. However, at the time OS/2 2.0 was released all (or nearly all) Windows software was 16 bit. Those 16-bit Windows apps didn't need any SDK, recompile, or anything. They ran as-is.
Incorrect. IBM provided run-time support for existing Win32 software. No porting, no recompile. Windows was essentially a full-fledged subsystem of OS/2.
I don't know if you're serious about radio transceiver as a substitute for a phone. They (radio transceivers) do allow people to communicate, but for the average person it would be a different set of problems for them.
I think more likely it'll be iPullMyFinger and will be sound activated by an accelerometer. The scratch-n-sniff model won't be out for another year or two.
*nix might not be a good fit for you. Right or wrong, *nix has been this way forever. I doubt there'll be an overnight conversion to something different (even if deemed 'better').
I disagree that they're inflexible. Capacity On Demand (COD) gives customers ability to pay for additional capacity (engine/CPU) only while that additional capacity is turned on. A mainframe is typically partitioned into LPARs at bare metal using PR/SM. You can add/remove/rearrange LPAR configurations. Then there is z/VM -- this is IBM's software crown jewel of mainframe software. This is where most shops run virtualized Linux servers. Create, start, stop, reconfigure guests as needed. You can reallocate storage among guests very easily. You can create software-only (virtual) networks for the guests. IBM's latest version of z/VM supports OpenStack. Many other features, these are just the main ones that come to mind. I don't call this inflexible.
Slashdot Mirror
Regarding the type of firearm used in this case. It's a shotgun, not anything firing a "bullet".
You're a dumbass. When you don't know what you're talking about just shut up.
Stubborn man
better keep your head
Don't forget
what your pocketbook said
Not only that, think of what kind of effect it has on morale......
You guys talk as though they're be hail to pay.
Deadheads narrow? You must not know of their affection for LSD.
I hope I never age past this state. The very idea of Lawrence Welk, pre-chewed food, and bingo every week makes me ill.
Hmm. Where does that leave western?
Exactly. You can't even see Townshend's guitar windmills on tape. Lame.
It can't fail cause all of the critics are doing it wrong.
Field worker: mobile phone, tablet, or laptop (applications can be native, web-based, or hybrid)
On-site worker: a combination of several in many cases (native, web-based, or hybrid)
Indeed. Sounds to me like OP is asking to get fired or blacklisted as soon as management gets wind of the plans. I wouldn't even broach the subject with them. The downsides far outweigh any benefits and if nothing else it's highly unethical.
Barbers will also always be in demand, but at this point that's just splitting hairs.
Or an electrician, as shocking as that may sound.
My memory is also failing! You're correct - it was limited to Win16 and Win32S. However, at the time OS/2 2.0 was released all (or nearly all) Windows software was 16 bit. Those 16-bit Windows apps didn't need any SDK, recompile, or anything. They ran as-is.
Incorrect. IBM provided run-time support for existing Win32 software. No porting, no recompile. Windows was essentially a full-fledged subsystem of OS/2.
I agree about tried and true.
I don't know if you're serious about radio transceiver as a substitute for a phone. They (radio transceivers) do allow people to communicate, but for the average person it would be a different set of problems for them.
Interesting. Not even for OS upgrades?
How does the battery life compare to whatever smartphone you had previously (if your previous phone was a smartphone)?
I think more likely it'll be iPullMyFinger and will be sound activated by an accelerometer. The scratch-n-sniff model won't be out for another year or two.
Gives new meaning to "I can't find my password in all this shit"
*nix might not be a good fit for you. Right or wrong, *nix has been this way forever. I doubt there'll be an overnight conversion to something different (even if deemed 'better').
> swallowed by a sinkhole
Or cratered by an asteroid!
My focus had nothing to do with cost -- it was regarding the topic of flexibility.
I disagree that they're inflexible. Capacity On Demand (COD) gives customers ability to pay for additional capacity (engine/CPU) only while that additional capacity is turned on. A mainframe is typically partitioned into LPARs at bare metal using PR/SM. You can add/remove/rearrange LPAR configurations. Then there is z/VM -- this is IBM's software crown jewel of mainframe software. This is where most shops run virtualized Linux servers. Create, start, stop, reconfigure guests as needed. You can reallocate storage among guests very easily. You can create software-only (virtual) networks for the guests. IBM's latest version of z/VM supports OpenStack. Many other features, these are just the main ones that come to mind. I don't call this inflexible.