8 ms·
And this is the logical conclusion of the death of the 56K baud modem. There was a prophetic (if early) contest at Sun to 'imagine the future' and the winner go
by ChuckMcM 12y ago
And this is the logical conclusion of the death of the 56K baud modem. There was a prophetic (if early) contest at Sun to 'imagine the future' and the winner got a SPARCStation. As a networking guy I tried to imagine what was going to change when the 'big yellow hose' (which is what 10MB Ethernet looked like at the time) came right into your living room. And one of the things that changed was that you could work at 'home' like you did at work, which at the time was most of the stuff on a beefy server with lots of CPU + storage and just the X windows on the local machine. (this worked fine with a lot less than 10MB of bandwidth of course, but it was conceptually a 'return to mainframes' pitch)
The economics are pretty sweet, given the marginal cost of one additional subscriber to a cloud 'hosted' environment. Google Drive / Drop box gets the storage requirement out of the way. Company X, acquires/operates a small server farm connected with a generic 10G pipe to the 'web' (this is an off the self config at places like Switch in Las Vegas). Sign up a bunch of subscribers where you have a 'free' tier to sop up excess compute and a paid tier for folks who care enough about response times to pay for them.
The dependency on the network has always been troubling, but once the network is like house 'power'. so many things one does depend on the house having power available, making it a requirement becomes less and less onerous. Combined with things that make traveling with data annoying (like cross border inspections) and I can see this as the future of application level computing for a lot of things.
Interesting that terminals are the future once again.
- astrocat 12y agoThe power/electricity analogy here is what's really key - there will come a time when the ubiquity of being "online" will be the same as the ubiquity of "the power is on." It's so prevalent in modern society we really don't think about it. It took me a while to realize that this is where Google is headed with ChromeOS/Chromebooks. Ultimately, "applications/apps" will not exist, there will just be the web and all personal computing devices become thin clients. What to use photoshop? great, go to //photoshop.adobe (or something); Office? //office.microsoft; play the latest COD? //callofduty.activision. [EDIT: also note the importance of search in this scenario...] I think google's bet is that just like CompUSA and other computer retail outlets have died, so too will "app stores" that sell digital equivalents of physical boxed apps. All apps will become services available openly on the web. It's definitely exciting, though I realize it makes a lot of people scared and there are definitely security risks that need to be kept in mind. But overall I see it as another step in the democratization of access and knowledge. A few hundred years ago, only the privileged had access to resources enabling them to read and write and create things. A few years ago, only those with some serious cash could (legally) purchase a license to operate a copy of Adobe's products. Now, any kid with 100 bucks and a decent laptop can spend 3 months with the entire Adobe catalog available to them. Pretty soon, that "high-powered" hardware requirement will be gone and the market opens up even further and pricing will drop even more. That's pretty awesome.
- na85 12y agoKids in the first world having access to mobile broadband at speeds and prices that make Photoshop-as-a-service feasible on their chromebooks is explicitly not awesome unless you're one of those privileged kids. This is a "rich get richer" situation that is developing. The problem with the centralized model is that it rather fucks over even people in developing or under-developed countries, and also places like, say, South Africa where broadband speeds are internally decent but are notoriously slow to the rest of the planet.
- dkokelley 12y agoI don't see how lowering the barrier to entry (access to tech) has any impact on the "rich getting richer".
- na85 12y agoDo you not understand analogies or something?
- seanflyon 12y agoIf I understand na85 correctly, they are suggesting that the terminal model of chrome books requires decent internet and thus increases the barrier to entry. I agree with you that Chromebooks lower the barrier to entry because hardware cost is too big of a factor (and many things still work offline).
- danieldk 12y agoAnd there are other barriers (I actually think the bandwidth problem is solvable, by caching large parts of the program). Before SaaS, a poor kid from Egypt could (although it's illegal) get a pirated copy of Photoshop, Office or Visual Studio and improve their skills with modest means. Now they need software subscriptions that they can't afford. I can see two things happening: it increases the popularity of FLOSS software in such countries and/or companies will adjust the monthly subscription fee to be proportional to e.g. the median income. Anyway, I think thinks can be said for both models. Regardless my worries about SaaS, I also like always having the latest version, not having to install and maintain programs, etc.
- blowski 12y agoDid you win?
- ChuckMcM 12y agoNo sadly. The winning entry involved video conferencing. (which also came to pass but not in quite the way that person envisioned it, I still think there is a chance we'll see it in games).
- vollmond 12y agoI telework two days a week. I VPN into work, then RDP into a Windows server and start up Eclipse. It works.
- joe_the_user 12y agoThe dependency on the network has always been troubling, but once the network is like house 'power'. so many things one does depend on the house having power available, making it a requirement becomes less and less onerous. Well, the other troubling aspect of getting all your software from the network is that you don't own anything. Adobe can end your access to the software if they just decide to. If you have paid, you might be able to sue them for the software back or you might get damages but neither will help if you have a job on a tight deadline.
- mwcampbell 12y agoThis optimistic outlook ignores the pesky reality of latency. Using VNC, X11, or an equivalent protocol over a connectiion to a data center hundreds or thousands of miles away isn't the same as an X terminal connected to a server in the same office buildinig.
- sliverstorm 12y agoWhile I entirely agree and preach latency often, there are two major points I would like to make: 1) Remote computing doesn't have to use X11. The local machine can do some of the lifting. Wolfram Alpha on mobile phones is a good example of this- a server does the crunching, but neither is the client side a dumb terminal. 2) I cross my fingers that one day latency will be prioritized more... IMO the majority of latency problems are not caused by the limits of physics, but rather the simple fact that not many people care about it. The theoretical peak ping speed across the USA & back is something like 20ms, an entirely reasonable figure for remote computing- if only it was ever anywhere close to realized.
- eru 12y agoAnd with modern browsers and AJAX we already have clients in place that can deal with latency better than X11 servers.
- 72deluxe 12y agoTrue, but is the real solution to remove the latency in the first place and just run it on your local machine without a network connection? (Like ordinary desktop software that we have at the moment.....; seems the terminal approach to software is attempting to fix a problem that has already been fixed - just run it locally)
- tincholio 12y ago> IMO the majority of latency problems are not caused by the limits of physics If you look at network QoS research in the past 20 years, you'll see that a lot of people do care. It's just not an easy problem to solve.
- deleted 12y ago[deleted]
- e12e 12y agoClaiming that "terminals are the future once again" is hardly controversial. How much (time/money/mind share) are invested in non-networked, desktop-style apps? Some, yes, but "everyone" seem to be (continuing) the push for networked apps (MS Office and Exchange/Sharepoint, Google (everything), Adobe/Macromedia with Creative Cloud, Apple iCloud ...). Mozilla is doing a cloud-push to, but have thankfully so far had a very strong self-host, do-what-you-please story. Not sure about the Firefox OS, though -- will we be able to (easily) host our own app store? Back-end services? At least for now the things I use (Firefox sync) is easy and feasible to self-host. The one thing I could see giving a resurgence to "off-line" for mainstream use, is latency -- more concretely -- the low latency tolerance of VR. But then again, as long as you can stream enough data/logic to the "terminal" -- even that shouldn't be a problem. I do hope the industry can help shift things towards locally cacheable/locally hostable solutions, though. I'd much rather run some "cloud" office suite on my server, with the option of taking it with me off-line from time to time (and then perhaps sync up whenever I'm on-line) -- than having my data on a third-party server. Or servers. I'm afraid the more likely future, is a future where a majority of users are locked-in to the whims of mega-corps -- and the scariest part of that, is that those that are leading in providing "cloud" services actually have a business model that centres around (ab)using the data, not charging for the services they provide.
- deepGem 12y agoSun had a specific phrase for these workstations. It was quite geeky to carry one of those id cards embedded with a chip. Practically everyone outside Sun made a mockery of these cards.
- marktangotango 12y agoThe problem with this formulation of the future is limiting cycles for the free tier sopping up as you say. How does that work exactly? Unless you're implementation is an interpreted language, I can't imagine a solution.
- ChuckMcM 12y agoThere is actually a pretty interesting solution in production today, you can use Vagrant and Docker to implement a containerized service system where 'priority' containers get resources in preference to non-priority ones. From the perspective of mainframe computing this problem was solved pretty much as a minimum viable feature (at the time mainframes had hard limits on things like getting billing jobs done before 6AM and other batch jobs got 'best effort' sorts of treatment) We have so many more tools now than they did, and hardware support too.
- marktangotango 12y agoGood points. Supposing you're referring to setrlimit/ulimit syscalls for example, do those apply per thread or per process? My understanding is they're per process. Then the math comes down to how many user processes per remote machine can the service run? A few hundred? That's a hard limit on the scalability of the service. Is process really the ideal level of isolation?