posted by dennisn on November 23rd, 2011 at 8:26PM
Webpages were designed for blogs and information -- that is why browsers were written, in C, and people forced to install them. (Although NNTP is still great and going strong. I'm toying with the idea of switching this site to NNTP, since that's all it really is.) Nobody ever brought the value of webpages into dispute. Why are you using strawman arguments?
Your point about a 5000 clone mono-culture is valid, somewhat. If everyone just used the same software/hardware, the world would be so much simpler. I guess this is ultimately what JS wants to do -- have everyone doing and using the exact same thing. It will never work. Although, even that is not a great argument, since if you're managing 5000 workstations, they're probably all variants of just a couple prototype/master machines -- so you would easily test the few "master/test" machines, before deploying. (Not to mention the fact that there isn't much your hypothetical admin currently has to deploy via JS in the first place. A fucking email client? A Like button? A map? Anything else I missed?)
Your point about a 5000 clone mono-culture is valid, somewhat. If everyone just used the same software/hardware, the world would be so much simpler. I guess this is ultimately what JS wants to do -- have everyone doing and using the exact same thing. It will never work. Although, even that is not a great argument, since if you're managing 5000 workstations, they're probably all variants of just a couple prototype/master machines -- so you would easily test the few "master/test" machines, before deploying. (Not to mention the fact that there isn't much your hypothetical admin currently has to deploy via JS in the first place. A fucking email client? A Like button? A map? Anything else I missed?)
|
posted by dsk on November 23rd, 2011 at 8:39PM
>Although, even that is not a great argument, since if you're managing 5000 workstations, they're probably all variants of just a couple prototype/master machines
No. Different departments have different upgrade paths. End-users may wish to access resources from outside of work. For example, they may choose to take a day off but still log in from the home machine to check on a resources. Or they may be on business in another country. Or maybe you may want to give guest privileges to a contractor whose only around for a few weeks or months, or guest privileges to a visiting client. Do you want the hassle of managing all those other workstation, when you could simply have them point their web-browser to a url containing your rich web app? Do you have to worry that they run the proper OS or force them to run one that is compatible with your application? Do you want to spend hours or days debugging an app to run on some exotic hardware when technology exists to you don't have to? See how unimaginative you are? The kinds of problems a web solves? Should come as a shock to you.
|
|
posted by dsk on November 23rd, 2011 at 8:34PM
>Webpages were designed for blogs and information
Very early versions of the web were designed to handle only simple marked up text. THAT WAS THE STARTING POINT, NOT THE END POINT. >Nobody ever brought the value of webpages into dispute. You did. You still do. Because you are a retard, who doesn't know he's a retard. *THIS* isn't a webpage as originally envisioned. It doesn't just serve lightly marked up text. It's a content management system that handles user input (files and text), centrally manages and stores it and returns it specifically formatted to users (formatting that is context sensitive, allowing it, for example to correctly display links to images as images and polls). You've already went beyond the confines of what "Webpages" were originally envisioned it to be.
|
