On College Football 2022: Week 6 Recap and Week 7 Pre... Ken said: |
Yeah, we've both had our share of hope and disappointment in this game. Let's just hope for a good b... |
On College Football 2022: Week 6 Recap and Week 7 Pre... Dan* said: |
I'm not sure how I feel about this game. On one hand, I feel pretty optimistic that we have the tale... |
On College Football 2022: Week 1 Preview Dan* said: |
Glad to see you'll be back writing football again, Ken! Congrats on the easy win today. You didn't ... |
On College Football 2021: Week 10 Recap and Week 11 P... Ken said: |
Yeah, sorry one of our teams had to lose. I've come to appreciate Penn State as a classy and sympath... |
On College Football 2021: Week 10 Recap and Week 11 P... Dan* said: |
Hey Ken, congratulations on the win yesterday! Some really odd choices by our coaching staff in that... |
Computing: IBM's "Workspace" Recalls the Mainframe Era | Wednesday, 2004 May 12 - 6:02 pm |
IBM is introducing a server-based application technology called "Workspace". This technology would allow users to access applications installed on central servers, using platform-agnostic "thin" clients. This is a familiar idea; will it work this time? We've seen this before. IBM's "Workspace" reminds me of mainframe-based computing, where terminals were used to access centralized computing resources. The idea was revived several times after the decline of the mainframes, in the form of Java-based thin-clients. Even Unix/Linux has elements of this idea (remote access via X11), as does Windows (Terminal Services client). The advantages and disadvantages have always been the same. Centralized computing means easier administration for IT departments, but heavier performance and reliability demands on the network. There's also a perceived loss of control for users, who no longer "own" applications (or sometimes, even their data). So will it work this time? Goodness knows, if anyone can make this work, IBM can. They have all that mainframe and server experience to draw from, and they have the enterprise clout and credibility to convince customers to try it. I think the time has come for this. Administration of applications in user-controlled environments is expensive and error-prone (I know, I have to do it myself). Network bandwidth has evolved to the point where even home-based users could deal with remotely-hosted applications. Worries about software piracy, viruses, and malware are pushing the desire for more controlled environments. The big problem here is that the technology wasn't invented by Microsoft. So inevitably, Microsoft will come out with some incompatible and proprietary version of this framework, and try to crush IBM in the process. Oh yeah: Microsoft will call this ".Net". |
Permalink
Posted by Ken in: techwatch |
There are no comments on this article. |