Slashdot Mirror


Amazon's New Silk Redefines Browser Tech

angry tapir writes "While the Kindle Fire tablet consumed much of the focus at Amazon's launch event Wednesday in New York, the company also showed off a bit of potentially radical software technology as well, the new browser for the Fire, called Silk. Silk is different from other browsers because it can be configured to let Amazon's cloud service do much of the work assembling complex Web pages. The result is that users may experience much faster load times for Web pages, compared to other mobile devices, according to the company."

166 of 249 comments (clear)

  1. No. by Anonymous Coward · · Score: 5, Informative

    Opera was doing this YEARS ago. As usual.

    Frist?

    1. Re:No. by DelitaTheFridge · · Score: 3, Informative

      They aren't even the only ones, Skyfire on android/winmo does this as well.

    2. Re:No. by Zantetsuken · · Score: 1

      Also, hasn't this been the way pretty much every single feature phone from cellular carriers with a "web browser" worked this way since that capability came out?

    3. Re:No. by kfet · · Score: 1

      It's in the desktop version of Opera for some time now, Opera Turbo : http://www.opera.com/browser/turbo/

    4. Re:No. by treerex · · Score: 1

      I was working on a project at Spyglass in the late '90s that did this... it isn't a new idea. It just got pushed to the background when devices started getting more powerful and bandwidth increased.

    5. Re:No. by RenderSeven · · Score: 1

      So when Apple adopts and popularizes an existing technology its a brilliant radical hybrid of marketing and engineering genius, but if Amazon does it its boring?

    6. Re:No. by Ruch · · Score: 1

      Agreed. I don't understand what's new. Several mobile gateways already do this! Cache, optimize, re-size content before it's set to the mobile browser. What's interesting is by going through their network, they can observe/track the usage, build data analysis engine, etc.....invaluable resource for advertisers.

    7. Re:No. by mattack2 · · Score: 1

      I was going to say no, thinking that you were probably thinking about WAP -- http://en.wikipedia.org/wiki/Wireless_Application_Protocol

      However, reading that page, you could maybe argue that it is similar to "Amazon's cloud service do much of the work assembling complex Web pages".. But I think mostly it was used as "simpler HTML".

    8. Re:No. by hkmwbz · · Score: 1

      Skyfire is not doing it anymore. It's just a video transcoder these days.

      --
      Clever signature text goes here.
  2. Potential privacy nightmare by sprior · · Score: 4, Interesting

    Nice performance bump for users, and an incredible data mining opportunity for Amazon - who wins more?

    1. Re:Potential privacy nightmare by sprior · · Score: 1

      Can you imagine what happens when at an inconvenient time someone goes to their Amazon home page and it says "because you like www.clownsboinkingnuns.com we recommend this selection of clown masks"

    2. Re:Potential privacy nightmare by Howard+Beale · · Score: 1

      Ding Ding Ding, we have a winner! And how much do you want to bet that there's a certain three letter government agency just licking their chops to get access to this data?

    3. Re:Potential privacy nightmare by magarity · · Score: 2

      Is that site slashdotted or something? I get a page not found error.

    4. Re:Potential privacy nightmare by colinrichardday · · Score: 1

      A certain three-letter government agency? I suspect that several such agencies would like a peek.

    5. Re:Potential privacy nightmare by timeOday · · Score: 4, Interesting
      You could just as well argue it increases privacy, since Amazon becomes a proxy service. So instead of your 1-page request hitting 10 companies' servers, each of which collects information on you, now they see a bunch of hits from Amazon.

      Of course, google probably aggregates information from those ten servers anyway, and Amazon probably sells the information they collect on you anyway, and the government is probably monitoring everybody involved in any case...

    6. Re:Potential privacy nightmare by Anonymous Coward · · Score: 1

      Another question to ask (other than "who wins more") really is "what are we losing?" "The Filter Bubble" by Eli Pariser is a potentially useful context to look at this "radical" new technology. It does sound very exciting and interesting, but there are questions we are ignoring about what sort of limitations become implicit when the choices we are presented with are based more and more on what have chosen in the past.

    7. Re:Potential privacy nightmare by Archangel+Michael · · Score: 1

      When people fear their government more than the government fears its people, it is a sad day.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    8. Re:Potential privacy nightmare by Dahamma · · Score: 2

      Except they also said they were going to proxy your HTTPS traffic by making a connection from their "cloud" to the destination server for you. In some parts they call that a "man in the middle"...

    9. Re:Potential privacy nightmare by shellbeach · · Score: 2

      Nice performance bump for users, and an incredible data mining opportunity for Amazon - who wins more?

      Is it really a performance bump, though? I mean, when have you ever felt the load time for a page accessed through broadband was too slow?

      If the Kindle Fire was running on a 33MHz Dragonball and accessing the net through a 14.4kbps modem, I could understand the need for this. But with a dual-core 1.2GHz processor and high-speed broadband, why do we need this? I'm still slightly confused at Amazon using this as a selling point ... (or perhaps it's a case of needing a selling point other than price, and drawing a blank?)

    10. Re:Potential privacy nightmare by timeOday · · Score: 1

      HTTPS can be proxied without being decrypted by the proxy, are you sure they aren't doing that? Or are you just joking? *Nobody* would want amazon snooping on their online banking etc.

    11. Re:Potential privacy nightmare by SomePgmr · · Score: 1

      I doubt it. The opportunity to sift through a trillion porn and lolcats visits a day probably isn't as interesting or inclusive as the access they already have, legally and otherwise.

    12. Re:Potential privacy nightmare by Dahamma · · Score: 2

      From Amazon's own FAQ on Silk:

      What about handling secure (https) connections?
      We will establish a secure connection from the cloud to the site owner on your behalf for page requests of sites using SSL (e.g. https://siteaddress.com./

      Still a bit vague, but not the part about "from the cloud to the site owner on your behalf". But in this case nothing can be assumed - it's their browser, so they can implement the client to cloud connection however they want. Let's just hope they do it securely (even if, unlike real HTTPS, there is no way to guarantee a point to point secure connection, which is enough for me never to trust it enough for my online banking...)

    13. Re:Potential privacy nightmare by justforgetme · · Score: 1

      Why would the GSA possibly want your tweets?

      --
      -- no sig today
    14. Re:Potential privacy nightmare by justforgetme · · Score: 2

      sift through a trillion porn

      Maybe they want to use amazon as a human filter? You know, to get to the good stuff faster!

      --
      -- no sig today
    15. Re:Potential privacy nightmare by justforgetme · · Score: 1

      Yes, popular theory is that your options and the diversity of the content will shrink if the filtering is done without some heuristic to add outside trends that fit your profile. But I think most content filters atm have nothing to worry about that because the theory implies you do semantically correct filtering.

      --
      -- no sig today
    16. Re:Potential privacy nightmare by justforgetme · · Score: 1

      Try to open up yahoo from a noisy public AP. The page might not even load. I think the real benefit for this will be on mobile devices and low bandwidth connections like overutilized public APs.

      --
      -- no sig today
    17. Re:Potential privacy nightmare by bennomatic · · Score: 1

      Yes, I call those "week days".

      --
      The CB App. What's your 20?
    18. Re:Potential privacy nightmare by thePowerOfGrayskull · · Score: 1

      People who watch tons of porno. Think of how fast it will load.

      I think the concern in that case is more the speed of un"load"ing.

    19. Re:Potential privacy nightmare by MrAngryForNoReason · · Score: 2

      no one wants to use a search engine that is shreds your privacy.

      I can confidently say that the majority of people using Google aren't concerned about privacy at all. And if there was a major scandal they would either not hear about it at all, or quickly forget it.

      At the end of the day most people either don't understand the issues sufficiently to worry about them, or flat out don't care.

      The only way your average web user is going to be up in arms about something like this is if the tabloids picked it up and ran big scare stories about it, and even then I bet most of them would be back using Google within a fortnight.

      99% of what annoys/outrages your average Slashdot user goes completely unnoticed by your average web user.

    20. Re:Potential privacy nightmare by MrAngryForNoReason · · Score: 2

      If it gives as much of a boost as Opera mini then it will be well worth it. One of the biggest performance increases comes from javascript being run on their servers before they send the page to your device. They give any onLoad events 2 seconds to fire and then cancel them so you don't get pages hung up waiting for flaky javascript that has hung for some reason or another. Any on page javascript is also processed on the server which massively reduces the load on the device itself.

      It does lead to slightly wonky interactions on sites that use a lot of javascript in the interface sometimes but it is miles faster than other mobile browsers (notably mobile safari).

    21. Re:Potential privacy nightmare by joost · · Score: 1

      They are using SPDY for the client to cloud connection, which is not only very fast but also https by design, you cannot have SPDY over plain http.

    22. Re:Potential privacy nightmare by afidel · · Score: 1

      Dude we know for a fact that all the Tier-1 traffic in the US already gets repeated to the NSA, why would they need a peek? Now the FBI might want a look, but for them to be able to do anything with it they need a warrant (even if it is a expost facto FISA warrant).

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    23. Re:Potential privacy nightmare by Lusa · · Score: 1

      I'm somewhat confused. Why would they care? You're talking about a small percentage of web browser usage compared with all other browsers and platforms. Not only that but this is just a small percentage of the network traffic. What about instant messages, bittorrent and other formats of communication some of which will be completely bespoke?

      No, I call bullshit. Some conspiracy theorists will happily sling around that an agency has their claws on the data but when you realise it is such a small percentage of all the data out there. It's pointless. Besides, they could get more information by hooking into the little facebook Like buttons, google's +1 or other tracking technology already in use. The real winners are the data miners, now amazon has a way to increase this without having to buy so much from other sources.

    24. Re:Potential privacy nightmare by Alternate+Interior · · Score: 1

      It looked to me from Ars take on it that they're compiling JS server-side but running it client-side. Timing shouldn't factor into that. It should decrease the time it takes JS to start running because the code's already been parsed and I would think poorly coded animation will run smoother. In a perfect world this feature would make litte difference.

    25. Re:Potential privacy nightmare by BitZtream · · Score: 1

      Uhm, SPDY works over HTTP just fine.

      It's a really retarded protocol to use, but that's another story.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    26. Re:Potential privacy nightmare by sprior · · Score: 1

      I wasn't really worrying about three letter agencies in this as much as Amazon itself knowing even more about me than they already do and using that to market to me endlessly. It already happens a lot that I see a product mentioned so I look at it on Amazon, but then it bugs me after that with all sorts of related suggestions so I end up going in and deleting it from my viewing history. If you've got three letter agencies interested in you, then your life is far more interesting than I plan for mine to be, and probably not in a comfortable way.

    27. Re:Potential privacy nightmare by Unequivocal · · Score: 1

      Serious question: could you explain why SPDY is retarded? I'm actually curious what's wrong with, not knowing much about it other than having read some material when it first came out..

    28. Re:Potential privacy nightmare by Maxmin · · Score: 1

      > You could just as well argue it increases privacy, since Amazon becomes a proxy service. That only works if they don't add client-identifying proxy headers to each of your requests... e.g. HTTP_X_FORWARDED_FOR, REMOTE_ADDR.

      --
      O lord, bless this thy holy hand grenade, that with it thou mayest blow thine enemies to tiny bits, in thy mercy.
  3. They Both Win by Gr33nJ3ll0 · · Score: 2, Insightful

    It's not always lose-win or lose-lose.

    1. Re:They Both Win by sprior · · Score: 2

      Reading comprehension is a blessed thing - my comment wasn't who loses, but who wins more.

    2. Re:They Both Win by Infernal+Device · · Score: 1

      It's not always lose-win or lose-lose.

      These days, it's pretty much a total loss for privacy.

      --
      "My God...it's full of trolls!"
    3. Re:They Both Win by Jonner · · Score: 1

      It's not always lose-win or lose-lose.

      Perhaps you missed the last word "more."

    4. Re:They Both Win by DrXym · · Score: 1

      Well it is lose-win if you don't actually want Amazon knowing your business. If it's optional then fine, if it's always on or kicks in when it feels like it or is even on by default then that sucks.

    5. Re:They Both Win by Tharsman · · Score: 1

      From the summary:

      Silk is different from other browsers because it can be configured to let Amazon's

      It can be configured. Or it can be ignored. As long as it's an Opt-In feature, and not an Opt-out one, the right to privacy is preserved.

      Real problem comes when they make these things "Opt Out", specially if the opt-out settings are as out of the way (and often buggy) as Facebook's.

    6. Re:They Both Win by CubicleView · · Score: 1

      That depends, is Charle Sheen a user?

    7. Re:They Both Win by Gr33nJ3ll0 · · Score: 1

      Who wins more implies there's a higher winner, and thus a loser, who is getting the worst of the deal.

    8. Re:They Both Win by slim · · Score: 1

      No it doesn't.

      I pay you $5 for a painting. Then I sell it for $10 (to a buyer who wouldn't have bought directly from you).

      We've both gained $5, we've both got some costs to take out of that. Neither of us loses.

    9. Re:They Both Win by CharlyFoxtrot · · Score: 1

      It's not always lose-win or lose-lose.

      The loser here is Google. They created Android to prevent Apple putting a layer between the user and Google's services and now here's Amazon using their Android fork to do exactly that. Oopsy.

      --
      If all else fails, immortality can always be assured by spectacular error.
  4. Opera Mini by Anonymous Coward · · Score: 5, Informative

    When you request a page in Opera Mini, the request is sent to the Opera Mini server that then downloads the page from the Internet. The server then packages your page up in a neat little compressed format (we call it OBML), ready to send back to your phone at the speed of ninjas on jetpacks.

    1. Re:Opera Mini by lostmongoose · · Score: 4, Funny

      The jet packs actually slow the ninjas down.

  5. No thank you. by pro151 · · Score: 1

    No trust here.

  6. This is just Opera Mini/Turbo by Necroman · · Score: 4, Informative

    Opera released Opera Turbo back in 2009 which does this same thing. As well, Opera Mini, their mobile browser, does this as well.

    So this isn't really re-defining the browser, it's just bringing the technology more mainstream.

    --
    Its not what it is, its something else.
    1. Re:This is just Opera Mini/Turbo by Anonymous Coward · · Score: 1

      Yea seriously. Opera Mini has done this for nearly 7 years. Before UMTS, and especially before EDGE, it was common place to use Opera Mini on a wide variety of smart and 'feature' phones. Yes, smart phones existed before iOS/Android, incredible.

    2. Re:This is just Opera Mini/Turbo by Excelsior · · Score: 1

      And the TMobile Sidekick by Danger (now Microsoft) did it many years before Opera. Nothing to see here. Move along.

    3. Re:This is just Opera Mini/Turbo by Necroman · · Score: 1

      Please, explain to me how it differs? I've read over the linked article and I don't see anything amazingly different? It can render locally or on the EC2 cloud (like turbo). I will agree there is the addition of "learning". Is there something else we're missing?

      Also, not an opera fanboy here. I tried opera mini when it came out. I'm a FF/Chrome fanboy.

      --
      Its not what it is, its something else.
    4. Re:This is just Opera Mini/Turbo by Anonymous Coward · · Score: 1

      Also, don't forget Skyfire and DeepFish. Both did the heavy lifting on backend servers and used a lightweight client on the mobile device. I don't see how Silk is redefining anything here.

    5. Re:This is just Opera Mini/Turbo by aaronszy · · Score: 1

      What Amazon is describing is something entirely different. They aren't just compressing the content, they actually render of the page remotely through their EC2 service. The bottleneck for web browsing on small devices like phones/tablets is often in the render time instead of the transfer time. Assuming you have a decent wireless connection, this should do a lot more to improve your web browsing experience than just content compression would.

    6. Re:This is just Opera Mini/Turbo by mobets · · Score: 1

      AOL did it with images back in the days of dial-up. I was confused by the low quality pictures the first time I saw it while visiting relatives.

      --

      It was me, I did it, I moved your cheese
    7. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 5, Informative

      You're absolutely correct that the basic "innovation" here is exactly what Opera Mini (note, not Turbo - specifically Mini) has done for ages. So all talk about "redefining the browser tech" is pure marketspeak, and both the submitter and the editor should be ashamed of spinning it the way Amazon PR wanted them to.

      However, there is one crucial difference with Mini here: it also does work as a full-fledged local browser. Mini always does layout and other optimizations "in the cloud", and fetches the result. That's why it's so bad at JS, Flash, HTML5 etc - if it's something that has to run locally, it's not supported. Here, they are transparently offloading work on the server, but when there is something in the page that cannot be handled well that way - or when the server is not available - it gets rendered locally, same as in any other browser. So it's supposed to be completely transparent to the user, unlike Opera.

      Of course, we haven't actually seen how well that it all works in practice, and I'll reserve my judgement until then. It'll be interesting to sniff traffic and see how much actually gets preprocessed; right now my suspicion is that on any script-heavy website, it'll mostly just do compression.

    8. Re:This is just Opera Mini/Turbo by 93+Escort+Wagon · · Score: 1

      Opera fanboys.. lol, who would've thought?

      If you didn't know Opera had fanbois, you've never participated in a Slashdot discussion about any browser tech before.

      --
      #DeleteChrome
    9. Re:This is just Opera Mini/Turbo by Amouth · · Score: 2

      so - if i have a hammer and i use it to nail a chair leg back on and then turn and use it to nail a table leg back on i've "refined" what?

      so Opera's reason for doing this was to conserve bandwidth (image compression was only part of it) the other large but was the overhead of the requests and also the optimization of space in the transmission.

      Amazon's is to optimize the data prior to the device.

      they both do the same thing with minimally different options - so yes Amazon did what Opera has been doing for years. (FYI Opera mini always had an option to disable image compression)

      --
      '...if only "Jumping to a Conclusion" was an event in the Olympics.'
    10. Re:This is just Opera Mini/Turbo by MrZilla · · Score: 1

      As far as I can tell, there is no bandwidth saved using EC2, only processor time (and, in turn, battery life). The pictures aren't degraded in quality like they were on the Turbo.

      Except that, according to TFA:

      The service also uses content compression techniques, such as re-encoding video and images before sending them to a device.

      --
      mov ax, 4c00h
      int 21h
    11. Re:This is just Opera Mini/Turbo by moronoxyd · · Score: 1

      Opera Turbo was all about compressing when connections were slow, not saving processor cycles for complex content.

      Opera Turbo on notebooks, desktops and high end smart phones is mostly about bandwidth reduction, yes. But before introduction of Opera Turbo Opera was already using this technology for Opera Mini.

      And Opera Mini uses proxy server to render pages that the CPU in a feature phone or older smart phone can not do. AND reduce bandwidth.

    12. Re:This is just Opera Mini/Turbo by MemoryDragon · · Score: 1

      Actually it is not only opera turbo, they were the first, but google also has this kind of offloading facility, early versions of the android browser used it.

    13. Re:This is just Opera Mini/Turbo by Threni · · Score: 1

      From my experience, the opera one was still too slow. It seemed to be ok immediately after a new version was released then it would end up being worse than a regular browser. So if Amazon put some CPU/bandwidth behind it it would be quite different.

    14. Re:This is just Opera Mini/Turbo by narcc · · Score: 5, Funny

      Speaking of optimization, you can save a byte with a small change to your sig.

      Your sig assembles to: A1 00 4C CD 21 (5 bytes!) whereas:

      mov ah, 4ch
      int 21h

      assembles to: B4 4C CD 21 (4 bytes)

      Interrupt 21h won't care what's in al, so you don't need to clear it.

      You kids these days code like everyone has megabytes of RAM just lying around.

    15. Re:This is just Opera Mini/Turbo by narcc · · Score: 1

      Bah, that should be B8 00 4C CD 21

    16. Re:This is just Opera Mini/Turbo by MrZilla · · Score: 5, Insightful

      Interrupt 21h won't care what's in al, so you don't need to clear it.

      Well, whoever spawned the process in question might care, since AL is the return/error code after termination!

      You kids these days code like everyone has megabytes of RAM just lying around.

      I would have thought you old timers had learned your lessons about skimping on what you assumed to be unimportant bytes ;)

      --
      mov ax, 4c00h
      int 21h
    17. Re:This is just Opera Mini/Turbo by Lennie · · Score: 1

      Those devices which existed before iOS/Android/WebOS/whatever are now sometimes called 'feature phones'.

      --
      New things are always on the horizon
    18. Re:This is just Opera Mini/Turbo by Nursie · · Score: 1

      Not that I approve of windows mobile, and it was a horrible experience, but -

      I had a Windows phone in about 2004. I compiled mame for it, and it could play some games tolerably fast. The UI layout was xml based and could be adapted. It had a camera module and a reasonably high def screen, and could take MMC-RS cards to play video and music. Definitely a smartphone by any description you choose to apply to it, and it was far from the only one.

    19. Re:This is just Opera Mini/Turbo by Lennie · · Score: 1

      I don't know how to classify the old Windows Phone, I just know one thing the browser definitely was not smart.

      --
      New things are always on the horizon
    20. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 1

      Opera Turbo doesn't do that, though. It does caching and image compression, and it also repacks HTML in a more efficient binary format - but it doesn't do server-side layout or rendering.

    21. Re:This is just Opera Mini/Turbo by narcc · · Score: 1

      I would have thought you old timers had learned your lessons about skimping on what you assumed to be unimportant bytes ;)

      Who knew that code would still be in production 30 years later? I'm just glad the 9/9/99 bug went relatively unnoticed.

    22. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 1

      Actually it's still a good idea to have Mini on your phone/tablet if you live in or travel to an area where cellular connectivity is either very slow (e.g. no 3G and no EDGE), very expensive per-byte, or both. There are plenty such places on the planet, still.

      Anyway, my comparison was with Mini because that's what Silk is most like. It's different from Opera Mobile in that Mobile doesn't do any server-side processing, except for (in "turbo mode") compression of images. Silk, on the other hand, does that, while retaining full support for all HTML5 features and Flash - or at least that's what Amazon says. So it does something that neither Opera Mini nor Opera Mobile can do.

    23. Re:This is just Opera Mini/Turbo by Nursie · · Score: 1

      You know what, I got confused between two old phones there.

      The windows one took full sized SD cards, had a camera module and could play music and videos.
      Then I had a Nokia N70 Symbian Phone, that took MMC-RS and could run some basic stuff in Mame.

      I guess I just wanted to make the point that there had been various degrees of smartness in phones for some time.

    24. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      Opera Turbo does do that. It adapts the page to the screen size and such. Images are resized, etc. In order to do that, it needs to render on the server first. That dynamic stuff is still handled on the browser part on the phone doesn't change that. Claiming that Silk is different from what Opera has been doing for ages is just silly. Opera can both render on the server, and render on the phone.

      --
      Clever signature text goes here.
    25. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1
      So, it works as a full-fledged local browser, just like Opera Turbo.

      Opera Mini is bad at Flash? No, it just doesn't handle Flash. Flash is a plugin, and no proxy browsers are able to process Flash. All they can do is to use the local plugin, or transcode some specific Flash videos.

      And how is Opera's compression not transparent? The user doesn't have to care about whether it takes place on the phone or the server.

      --
      Clever signature text goes here.
    26. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 1

      To the best of my knowledge, Opera Turbo doesn't do rendering and layout on the server. It does image compression and caching on the server only, and uses a more efficient binary protocol - and that's that.

      For example, if you go to their official page, the only explanation they give is:

      How we squeeze out all that speed?

      When Opera Turbo is enabled, webpages are compressed via Opera's servers so that they use much less data than the originals. This means that there is less to download, so you can see your webpages more quickly.

      and here is the comparison page for Mini vs Mobile (note that the latter has Turbo):

      What is the difference between Opera Mobile and Opera Mini?
      The main difference is what goes on behind the user interface.
      Opera Mini always uses Opera’s advanced server compression technology to compress web content before it gets to a device. The rendering engine is on Opera’s server.
      Opera Mobile is a full Internet browser for mobile devices. The full web-rendering engine – Opera Presto – is run on the phone using the phones’ hardware to download and display webpages.

      Seems pretty clear-cut to me that only Mini does any server-side processing other than compression and protocol optimization.

      If you have any references to prove otherwise, please give them.

    27. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      Amazon is describing Opera exactly.

      --
      Clever signature text goes here.
    28. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      Anyone who doesn't agree with blatant marketing lies from Amazon is automatically a fanboy for some other product.

      --
      Clever signature text goes here.
    29. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      The point is: As you can clearly see, Opera offers both local and remote handling of the page itself. Browsers have been doing this for years. There's nothing new with Amazon's offering.

      --
      Clever signature text goes here.
    30. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 1

      The point is that "remote handling" can mean some very different things. Browsers have been doing remote compression for ages, long before Opera even (e.g. AOL). But compression only works to surf faster on a slow network channel; it does nothing to improve browser speed on slow hardware. Opera Mini was what introduced the concept of doing the "hard work" of HTML/CSS handling server-side, and feeding preprocessed data to the browser in a form that can be rendered fast even on underpowered hardware - that was a major step, but it was not transparent, in that if you came by a website that used something that couldn't be handled in that manner, you were SOL, and had to switch to a proper browser (if your device had any).

      The neat thing about Silk is that it does that completely transparently to the user - those parts of the page that can be rendered in the cloud, are, and those that can't are rendered locally with full support for HTML5 features and plugins. Thus you get all the speed / low-power advantages of Mini everywhere they can be used without sacrificing user experience. That is what's new with Amazon's offering.

    31. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      but it was not transparent, in that if you came by a website that used something that couldn't be handled in that manner, you were SOL, and had to switch to a proper browser

      That's a load of nonsense. First of all, Opera Mini handles more dynamic content now. Secondly, other "cloud" browsers like Skyfire (before they removed that feature), Bolt, etc. all handle all that stuff perfectly.

      The neat thing about Silk is that it does that completely transparently to the user - those parts of the page that can be rendered in the cloud, are, and those that can't are rendered locally with full support for HTML5 features and plugins.

      Again, this is nonsense. It's exactly what all these other browsers have been doing for years.

      Thus you get all the speed / low-power advantages of Mini everywhere they can be used without sacrificing user experience. That is what's new with Amazon's offering.

      Again, no. Complete and utter nonsense. You have been drinking the Amazon Kool-Aid.

      --
      Clever signature text goes here.
    32. Re:This is just Opera Mini/Turbo by shutdown+-p+now · · Score: 1

      The plain fact is that Opera Mini is not a conformant HTML5/CSS/JS browser. It can handle a certain subset, and that's it. Regardless of whether it's handling "more" now or not, it's not a full browser. Silk is different in that regard.

      I never used Skyfire so I'm not familiar about it - I was only talking about Opera Mini. If Skyfire does everything that Silk claims to do, then more power to it.

    33. Re:This is just Opera Mini/Turbo by hkmwbz · · Score: 1

      By that logic, no browser conforms because all browsers are missing pieces of those standards, or have bugs that mean that they violate them.

      And you are artificially and dishonestly limiting to Opera Mini (which still did what Silk does ages ago), ignoring browsers like Bolt, Skyfire, Nokia's S40 browser, etc. Anything Silk claims to do, other browsers did it before it.

      --
      Clever signature text goes here.
  7. Mandy Rice-Davies comments ... by Kittenman · · Score: 1
    From TFA "The result is that users may experience much faster load times for Web pages, compared to other mobile devices, according to the company."

    And to paraphrase the immortal words of Mandy Rice Davies - they would say that, wouldn't they.

    --
    "The greatest lesson in life is to know that even fools are right sometimes" - Winston Churchill
  8. Opera? by nine-times · · Score: 1, Redundant

    Didn't Opera do something similar, where they rendered the web pages on their own server and then passed it to their mobile browsers in an optimized form?

    1. Re:Opera? by POWRSURG · · Score: 5, Funny

      You're missing the major difference between what Opera did and what Amazon is doing. Opera did the rendering on their own server, while Amazon does it in the cloud. Totally different.

    2. Re:Opera? by Anonymous Coward · · Score: 1

      Opera Mini renders for slow processors (packages the rendered content in a formal called OBML).
      Opera Turbo compresses for slow connections.

      I think the parent's sarcasm is justified. You're missing a vital piece of information.

    3. Re:Opera? by 93+Escort+Wagon · · Score: 3, Insightful

      Not sure if trolling or just stupid...

      He was engaging in an obscure practice known as humor.

      --
      #DeleteChrome
    4. Re:Opera? by DarwinSurvivor · · Score: 1

      Nice trolling. Trying to up your youtube view counter there?

    5. Re:Opera? by Peter+Bortas · · Score: 1

      You are thinking of Opera Mini. Opera has the (disabled by default) acceleration feature "Opera Turbo" built in to Opera Desktop and Opera Mobile that works pretty much exactly like Amazons Silk.

    6. Re:Opera? by synapse7 · · Score: 1

      So if a server at Amazon is in the cloud where are the Opera servers?

    7. Re:Opera? by hunangarden · · Score: 1

      Nothing in the articles to suggest they are doing any Rendering in the cloud. Not sure where anybody is getting this from. They will cache content, compress, etc, but I doubt they will render.

  9. Re:Prior Art - Opera Turbo by sprior · · Score: 1

    Also the WAP protocol used in the early days of phone web browsers.

  10. Yo dawg... by Lanteran · · Score: 1

    We heard you like the cloud, so we put the cloud in your cloud so you can swear while you disconnect!

    --
    "People don't want to learn linux" hasn't been a valid excuse since '03.
    1. Re:Yo dawg... by Jonner · · Score: 1

      We heard you like the cloud, so we put the cloud in your cloud so you can swear while you disconnect!

      The next version of silk won't need a client at all. The cloud will be able to take the place of the user's device as well. Sure, you might end up spending thousands of dollars on items from Amazon you wouldn't have ordered, but think of the time savings!

  11. Re:Prior Art - Opera Turbo by unrtst · · Score: 1

    They didn't patent it (AFAIK). WTF does prior art have to do with it?

    And "How is this any different..."? uh, just read about it. Off the top of my head, it's based on Amazon EC2 and ties into that entire network - I'm not intimately familiar with Operas solution, but I doubt they have as much hardware real estate on the server side. Similar? maybe a lot, but it's not the same, and it's still something that will end up being a very new experience and thing to most people.

    It's still new tech, even if done before elsewhere. New as in relative to time, as opposed to "brand new" or first time in use.

  12. Re:Reads like hype... by Guspaz · · Score: 1

    Indeed, it is. Opera is also available on the iPhone. And the blackberry. And featurephones. And Mac. And PC. And Linux. I'm not sure there's any computing platform that it's not available for...

  13. How exactly is this redefining? by SirDrinksAlot · · Score: 3, Informative

    This is ridiculously old technology. Just about every other mobile browser does this now other than maybe IE on Windows phones and Safari on IOS. BlackBerry's have been doing this since 2005, as someone else mentioned Opera has had it since 2009, Bolt Browser has this feature as well. So I am to believe that a browser technology that's been around for 6 years is redefining browsers now? Way to grab on to an old feature and herald it as something new and ground breaking.

    1. Re:How exactly is this redefining? by geekmux · · Score: 1

      This is ridiculously old technology...BlackBerry's have been doing this since 2005...

      Uh, wow. Maybe I'll hold off altogether on this "new" tech then. Seems in the battle of browser wars to find the fastest, easiest, and most efficient one out there, I don't ever hear someone exclaim "Oooh, you should go get a Blackberry!"...

  14. Re:Prior Art - Opera Turbo by magarity · · Score: 4, Interesting

    Opera turbo uses compression via opera's servers. Amazon's thing uses amazon's servers to render. With opera the point is to get around a slow connection on the consumer's side. Amazon's point is to do the render processing on amazon's side. Let's take an annoyingly busy website, for example: http://home.sina.com/ Now this beast can take a while to download and get ready, especially on a low power handheld thing like a tablet. Amazon's silk method should prep all those parts for the displaying device.

  15. Amazon Silk + SSL = MITM? by Kupo · · Score: 5, Insightful
    Cross posting from my old comment. As per their help:

    What about handling secure (https) connections?
    We will establish a secure connection from the cloud to the site owner on your behalf for page requests of sites using SSL (e.g. https://siteaddress.com/ ).

    So essentially, they become the man-in-the-middle so they can better cache your HTTPS content? And their browser is programmed to show this is acceptable/secure... What kind of privacy implications does this introduce? Even if their privacy policy says they won't use the data maliciously, cloud computing isn't a bullet-proof system (i.e., leaks, hacking incidents, etc.). Call me paranoid, but if I read this right, this sounds like a frightening idea.

    1. Re:Amazon Silk + SSL = MITM? by nullchar · · Score: 1

      Agreed. Proxies (like the Silk browser uses, even if fancy like Opera's OBML) *shouly* only proxy/format plain HTTP data. Any HTTPS connections *must* go direct from device to server: end-to-end.

      I hope the browser displays a warning every time if it truly proxies HTTPS content! (And iconally shows the 'broken padlock' or jolly rodger.)

    2. Re:Amazon Silk + SSL = MITM? by Jonner · · Score: 2

      Call me paranoid, but if I read this right, this sounds like a frightening idea.

      That's an entirely appropriate level of paranoia. What they're describing in their own help is exactly a MITM attack and extremely irresponsible. If the browser portrays that as "secure" it's fraud.

    3. Re:Amazon Silk + SSL = MITM? by js_sebastian · · Score: 1

      Cross posting from my old comment. As per their help:

      What about handling secure (https) connections? We will establish a secure connection from the cloud to the site owner on your behalf for page requests of sites using SSL (e.g. https://siteaddress.com/ ).

      So essentially, they become the man-in-the-middle so they can better cache your HTTPS content? And their browser is programmed to show this is acceptable/secure... What kind of privacy implications does this introduce? Even if their privacy policy says they won't use the data maliciously, cloud computing isn't a bullet-proof system (i.e., leaks, hacking incidents, etc.). Call me paranoid, but if I read this right, this sounds like a frightening idea.

      Iif they put themselves as a man in the middle that sees your banking account credentials, credit card numbers, etc, all their servers that are involved in this should be subject to the kind of security standards and regulations that are required of sites that handle credit card numbers...

    4. Re:Amazon Silk + SSL = MITM? by Peter+Bortas · · Score: 1

      In the case of OBML that is not possible. Opera Mini in it's core is a ~50KiB application. You could barely build an HTML1 parser/render with that, forget about HTML5. Opera Turbo on the other hand is mounted in fully featured browsers, so it will refuse to proxy SSL connections.

    5. Re:Amazon Silk + SSL = MITM? by kiwix · · Score: 1

      On the other hand, as soon as you use proprietary software, the software vendor is effectively a man-in-the-middle... They just do it in a more visible way.

    6. Re:Amazon Silk + SSL = MITM? by vagabond_gr · · Score: 1

      If this is only at the TCP level, essentially forwarding all encrypted traffic unaltered, then there is no issue.

      But looking at the content is very serious. If the browser shows that it sends the data encrypted to example.com, but in fact it sends them in cleartext to proxy.amazon.com, it's a ridiculous security hole. I doubt they are doing this.

    7. Re:Amazon Silk + SSL = MITM? by Apocros · · Score: 1

      Not necessarily... see RFC 2817.

      --
      "onward!" cried the copper man, little knowing brass corrupts...
    8. Re:Amazon Silk + SSL = MITM? by LordLimecat · · Score: 1

      Please dont misuse legal words in a non-legal context. If they tell you they are doing this, it isnt fraud, whatever else it may be.

    9. Re:Amazon Silk + SSL = MITM? by Kupo · · Score: 1

      The RFC you linked to points out: in a proxy situation, this establishes a secure connection between you and the proxy (between proxy and target site is undefined). If you want end-to-end TLS, it states you must use CONNECT to create a tunnel.

      I can't imagine Amazon would funnel TLS encrypted connections through AWS using this method, since the whole point of Silk is to analyze/cache/preload the content (end-to-end crypto would break this ability). If they couldn't read your HTTPS data, it would be less latency for you and cheaper for Amazon to have the client connect directly. Their Help site makes it sound like proxy/cached mode is the default setting, so IMHO it still is effectively a man-in-the-middle.

      Thankfully, it looks like you can disable it (or use a different browser), so I may just be paranoid for no reason.

  16. Re:Offline Access? by amRadioHed · · Score: 2

    What magical browser do you use that allows you to surf the web without any network connection?

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  17. Re:Prior Art - Opera Turbo by fluffy99 · · Score: 1

    Opera turbo uses compression via opera's servers. Amazon's thing uses amazon's servers to render. With opera the point is to get around a slow connection on the consumer's side. Amazon's point is to do the render processing on amazon's side. Let's take an annoyingly busy website, for example: http://home.sina.com/ Now this beast can take a while to download and get ready, especially on a low power handheld thing like a tablet. Amazon's silk method should prep all those parts for the displaying device.

    Um, yeah. So it does work exactly like Opera Turbo does. Opera turbo also down-sampled images to a lower resolution or lower number of colors which helped cut the download sizes quite a bit.

  18. Re:Prior Art - Opera Turbo by DJRumpy · · Score: 2

    You do realize that in order to compress the data, Opera's servers have to render it first? The two technologies are more similar than they are dissimilar. From what I recall, Opera's approach is to pre-render on a proxy server, compress the end result, and send down to the device as a compact binary stream, and Silk appears to be doing pretty much the exact same thing but without any additional compression that I saw mentioned.

    In any case, both have to pre-render the page and Opera's approach also removes the bulk of processing as well.

  19. Re:Offline Access? by siddesu · · Score: 2

    You can check if Avant-go is still around.

  20. Re:Offline Access? by Belial6 · · Score: 1

    Funny enough, there are several solutions for this.

  21. Re:Reads like hype... by Guspaz · · Score: 1

    Opera Mini runs fine on Arm Linux.

  22. Re:Reads like hype... by siddesu · · Score: 1

    where do you get it from?

  23. Re:Offline Access? by amRadioHed · · Score: 1

    Such as? Sure you can locally cache files but browsing in such a limited way isn't exactly what comes to mind when I think of "surfing" the web.

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  24. Not sure how long this will be useful (if at all). by SexyKellyOsbourne · · Score: 2, Informative

    Basically, what this service does is make a "google maps" version of the webpage -- cutting pages up into tiles (like the Nintendo NES did) and streaming them over a wireless connection from their reserved-for-holidays EC2 data centers. Some localized bastardization is involved, but the "google maps" img tiling is the basis of it.

    A quick wget of the cnn.com front page yields 2.10 MB of data. And yes, it's less to tile it -- a screenshot at 1400x900, for about 40% of the page, converts into a lossless PNG file for about 700K of data. A lossy but usable 90-quality JPEG is around 350K. The processing time and RAM to bit blit that client-side of course will be a lot less than a modern ACID 2/3 browser would require.

    But as sites become more dynamic, the response time to constantly stream pixels won't be worth it. And a lot of sites rely on being dynamic -- view the HTML source on Facebook some time, it's almost all JS. Even slashdot (famous for being HTML3 well into the 2000's) now feeds its stories dynamically with javascript and HTML5.

    This isn't "redefining browser tech," it's probably a stopgap measure for their current market-undercutting $199 tablet processor. Anything JS/HTML5 runs fine on my dated Athlon X2 laptop on Chromium or Iceweasel, and that kind of speed will easily be in tablets in 1-2 years. Amazon says Fire is "dual core" but it's probably skimpy CPU-wise and/or RAM-wise. Or maybe their attempt to reinvent the wheel by rolling their own browser engine under NIH syndrome instead of using Webkit or Gecko just turned out badly.

  25. Re:silk browser new tech? by MightyMartian · · Score: 1

    I use Opera Mini on a shitty little LG phone. Works quite well, I can even post to Slashdot from it.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  26. iPhones did something similar by Chuck+Chunder · · Score: 2

    And I mean the Infogear iPhone from last century.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  27. This is a potential method to defear noscript by managerialslime · · Score: 2

    Users of noscript have long benefitted from fast loading of web pages as distracting ads pulled from other domains were suppressed.

    If entire web pages are "constructed in the cloud" and then presented to users, the additional overhead of ads,
    including annoying animation, would once again turn perfectly readable pages into aggravating distractions that
    eventually drive readers away. Anyone remember answer.com? AskJeeves? Or cnn.com before noscript?

    Bah humbug to this "improvement" in technology.

    --
    Live Long and Prosper - Thanks Leonard. You are missed.
    1. Re:This is a potential method to defear noscript by MrAngryForNoReason · · Score: 1

      Anyone remember answer.com? AskJeeves?

      No I doubt most people do. Google.com loads up nice and quick though.

      Even on pages that do pull in a lot of ads using javascript if this works anything like Opera Mini they won't be a problem. Opera Mini gives any javascript 2 seconds and then bins it which means an ad server that is slow to respond won't slow the page load down. All the javascript is run in the cloud and only a flat page is pushed out to the device so there isn't any overhead for javascript.

    2. Re:This is a potential method to defear noscript by WillDraven · · Score: 1

      I grew up attached to a computer. I have ad blocking in my wetware. I simply don't even notice web advertisements anymore, unless they have sound.

      I did recently start using adblock, but that was because I started noticing increased load times and companies tracking me with social media buttons. My visual cortex started filtering out banner ads years ago.

      --
      This is my sig. There are many like it but this one is mine.
    3. Re:This is a potential method to defear noscript by afidel · · Score: 1

      If you're worried about the social buttons I would suggest looking at the antisocial subscription list. One warning though I also had to add facebook.com to my block list as some pages kept reloading some php from facebook servers every few seconds once I subscribed.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    4. Re:This is a potential method to defear noscript by WillDraven · · Score: 1

      Someone on Slashdot mentioning the antisocial list is actually what got me to install adblock in the first place. :)

      --
      This is my sig. There are many like it but this one is mine.
  28. Re:Good by shellbeach · · Score: 2

    That whole fucking 2 seconds was killing me

    seriously were not running 486's here aside from slashdots javabloat every other site does not suck on modern machines, hell if you can stand not pissing you pants even slashdot only takes about a min on a 300mhz PPC

    So long?? It takes less than a minute on a Cyrix P-166 running firefox 1.0 and Win95 (yeah, baby!) (don't laugh -- it's the only machine we've got at work that still has ISA slots, which we need for a bit of equipment ....)

    But I agree wholeheartedly with the point. Why would anyone wish to jeopardise their privacy to save a few seconds (max) of waiting for a webpage to load? The fact that Amazon can use this as a selling point is a sad statement on current attitudes to privacy.

  29. Re:This is a potential method to defeat noscript by managerialslime · · Score: 1

    Defeat! Sorry for the typo.

    --
    Live Long and Prosper - Thanks Leonard. You are missed.
  30. Re:You guys seem to be forgetting the pre-fetching by shellbeach · · Score: 1

    It also uses its algorithms to know which links you'll most likely click on (based on what others have clicked on) and starts pre-fetching that data so if/when you click on the link it'll take even less time to load.

    Unlike other pre-fetching technology that had no intelligence built in this sounds very awesome.

    So not only does Amazon see all the data I'm loading, but they keep a record of it too??? What could possibly go wrong here?

  31. NXDOMAIN by furbearntrout · · Score: 1

    That domain is unregistered. Feel free to buy it; this is clearly an SEO opportunity...

    --
    Crap. What did the new CSS do with the "Post anonymously" option??
  32. Skyfire too by CruelKnave · · Score: 1

    Skyfire does it, too.

    1. Re:Skyfire too by hkmwbz · · Score: 1

      I don't think Skyfire is doing it these days. It only compresses video now.

      --
      Clever signature text goes here.
  33. I read it as just another hop... by thrill12 · · Score: 1

    ...not a complete caching of HTTPS content (which would be pretty futile). There would only be an issue if, say, the CA system of validating what server you are talking to has got a leak, because then Amazon(/any attacker controlling (part) of the EC2 server park) could theoretically perform a real MITM (barring any legal consequences, of course). But hey, the CA system is perfect... erm... never mind...

    --
    Slashdot: stuff for news, nerds that matter, matter for news, stuff that nerd
  34. Awesome! by glwtta · · Score: 1

    I love it when stuff redefines other stuff! So exciting.

    --
    sic transit gloria mundi
  35. Re:Not sure how long this will be useful (if at al by Anonymous Coward · · Score: 1

    Why restrict yourself to a rasterized image? Sending it as a mix of vector and rasterized images would cut size down a ton with no quality loss. In fact, Skia, the rendering library behind Chrome and Android, already supports exactly that. Android's WebKit port actually spits out a SkPicture, which is a recording of the drawing commands needed to draw the page (a mix of vector and rasterized parts), which is then sent over to another thread to be drawn onto the screen. Serialization to a byte stream is supported, so just send that over the wire and you've got yourself a highly compressed, no loss representation of the page. More importantly, it can be arbitrarily scaled without quality issues thanks to it's mostly vector nature.

    Whether or not Amazon did that or if they are basically just being a SPDY proxy remains to be seen, but the pieces are all there.

  36. Mixed message on SSL by purplie · · Score: 1
    The FAQ says, confusingly,

    We will establish a secure connection from the cloud to the site owner on your behalf for page requests of sites using SSL (e.g. https://siteaddress.com./

    Amazon Silk will facilitate a direct connection between your device and that site. Any security provided by these particular sites to their users would still exist.

    Which is it?

    1. Re:Mixed message on SSL by sourcerror · · Score: 1

      You get one SSL connection from your phone to the Amazon server, and they get one from the Amazon server to the destination server with your credentials. So you have to trust Amazon not abusing their position by stealing your private keys. But Amazon pretends in their FAQ that their presence in the chain isn't a risk factor at all.

  37. Hmmm, like my T-Mob Sidekick... by poemtree · · Score: 1

    from 2002.

    *Ring*

    Hello? 2002? You want what? Your server-side web optimization catered to a device? Uh huh, ok. Ok, ok, I'll let Amazon know...

    --
    Any sufficiently advanced technology is indistinguishable from Macintosh...
  38. Re:Offline Access? by prionic6 · · Score: 1

    +1 Funny

  39. Pff, Opera does everything earlier by SmallFurryCreature · · Score: 1

    Lets face it, us few Opera users are used to living a couple of years in the future.

    Mind you until 27 Septembet 2012 I sometimes got upset but since the new law enacted two days ago put to death all IE/Chrome and Firefox users (Lynx users already got their punishment through usage) I am a lot more mellow about it.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  40. Re:Not sure how long this will be useful (if at al by Lennie · · Score: 1

    The use of SPDY does seem likely:

    "Software Development Engineers - SPDY
    SPDY is an open source network transport protocol which we have leveraged in the design of Amazon Silk. In this role, you will have end-to-end ownership of our use of SPDY. You will be expected to have strong familiarity with the protocol and to use that knowledge to come up with innovative ways to improve the customer experience. We're looking for strong team players who thrive in a startup-like environment where flexibility is essential and delivering rock solid, customer focused solutions is paramount."

    http://aws.amazon.com/amazonsilk-jobs/

    --
    New things are always on the horizon
  41. Newflash! It's WebKit by tyrione · · Score: 1

    Since when is WebKit and some code from Chromium the revolutionary part and WebKit the mundane part?

  42. Re:Reads like hype... by Nursie · · Score: 1

    Which arm platform?

    My N900 runs Opera Mobile 11 just fine. You can pick that build up from http://labs.opera.com/downloads/

    They have just dropped support for Windows Mobile 6.5 though.

  43. Re:Reads like hype... by WrongSizeGlass · · Score: 1

    If Amazon really wants to aggregate your information they'll keep Opera Mini - and all browsers for Android - out of the Kindle Fire store. Don't forget that you can only get apps from the Amazon store, and Amazon can and will decide what you can get.

  44. This has been done many times by DragonHawk · · Score: 2

    Opera Mini isn't the only one.

    One of the PalmOS browsers worked this way, doing pre-rendering at the other end to help compensate for a slow connection and a small device. If the ISP's server farm went down, so did your web browser.

    I've used a satellite Internet provider that did similar as well, parsing the HTML at the provider ground station so it could fetch all the needed objects and send them in a single stream to the sky. This eliminated a lot of repeated fetch requests from the client over sat, which made a big difference since RTT was around one second.

    And given that it was satellite, wouldn't that also qualify as "in the cloud"? ;-)

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
    1. Re:This has been done many times by RoFLKOPTr · · Score: 1

      And given that it was satellite, wouldn't that also qualify as "in the cloud"? ;-)

      SatNetTechCo: Going Beyond The Cloud

  45. Injecting ads by kiwix · · Score: 1

    The main motivation for this technology is probably the ability to inject or replace ads in any webpage...

  46. Re:Not sure how long this will be useful (if at al by supermank17 · · Score: 1

    I don't know that its a processor issue; from reports its basically running the same 1.2Ghz processor that the Blackberry Playbook runs (which by all accounts is quite zippy). That puts it (roughly) on par with an ipad2, and gives it a fair amount more horsepower than an original ipad. Which again leaves me wondering why they're touting this so highly. My mother's original iPad never seemed particularly terrible when loading pages, and my HTC Sensation seems downright snappy with its dual-core, 1 Ghz OMAP processor. I guess we'll have to wait and see if it really does have some huge speed benefit, or if its just something they threw on the pile in an attempt to make the Fire look more appetizing.

  47. Re:Prior Art - Opera Turbo by crypticedge · · Score: 1

    new [noo, nyoo] Show IPA adjective, -er, -est, adverb, noun
    adjective
    1. of recent origin, production, purchase, etc.; having but lately come or been brought into being: a new book.
    2. of a kind now existing or appearing for the first time; novel: a new concept of the universe.
    3. having but lately or but now come into knowledge: a new chemical element.
    4. unfamiliar or strange (often followed by to ): ideas new to us; to visit new lands.
    5. having but lately come to a place, position, status, etc.: a reception for our new minister.

    Nope, doesn't fit.

    Now you could say new browser or device, but thats really all that's new with this. the tech is far from new, as it's been done for the last 10+ years by Opera. Or in the computing world, its fucking ancient.

  48. Re:Reads like hype... by Guspaz · · Score: 1

    Just grab the generic J2ME version, along with the java runtimes and the J2ME wrappers.

  49. Old Fogey... by tekrat · · Score: 1

    I'm probably dating myself to all the kids on Slashdot, but when did web pages get so complex that work now needs to be split?

    I still write all my HTML by hand, optimize my images, specify the actual size of the image in the IMG tag, yadda yadda.

    I *never* understood the purpose of CSS, except that it mucked things up. I was very happy with black text against grey (woot Mosaic). Heck, my favorite browser was Omniweb for NeXT.

    When exactly did things get so bad that web browsers are at their limit and these tablets, which have far more power than my Amiga, can't render web pages without help?

    --
    If telephones are outlawed, then only outlaws will have telephones.
    1. Re:Old Fogey... by matthewv789 · · Score: 1

      It's more of a bandwidth and latency issue, which is more of a problem on mobile wireless devices than on typical modern wired broadband connections.

      I suspect YOUR pages don't have many of these performance issues (though avoiding CSS is downright backward, unless all your pages really ARE just plain text rendered however the browser defaults make it end up). But that kind of usage is far from typical. People today want visually-rich, content-heavy, interactive web applications, not just simple pages with a little text and not much else. And most web content doesn't have the luxury of being hand-crafted by performance-minded HTML experts.

      For instance, lots of people tend to upload big (as in both large dimensions and poorly-compressed) images, often hundreds of KB or even several MB, to a web page (which isn't often set up to automatically scale images on upload), then set the HTML img tag dimensions to something much smaller (sometimes even tiny thumbnail size). One of the things Silk does is re-scale the image to that smaller size in advance (optimally re-compressing it at the same time), and only send that tiny thumbnail to the end user. It probably takes screen resolution into account so that no image delivered to the mobile device would ever be larger than its maximum resolution. (If you zoom in to see only a part of a large image up close, it probably sends just the tile you're looking at.)

      It does similar things with videos. One might think re-processing videos would take too long, but with the massive processing power of EC2, it becomes feasible to do such things quickly enough to be worthwhile - that is, faster for the end user than just delivering the original form of the video.

      Other components of a typical web page may be linked as many separate uncompressed files, each of which is larger than it needs to be and must be requested separately (often in series, due to browser limits on the number of simultaneous connections to a given server). Silk likely combines and compresses those files (and maybe minifies in the case of HTML/JS/CSS, such as stripping out comments and whitespace, or even omitting irrelevant files, such as IE- or print-only stylesheets, or JS files that don't contain any code that is executed on the page), then transmits them using SPDY, which can be much faster than HTTP (but which most web servers, and browsers, don't understand).

      There may also be a lot of content that's not initially visible (either scrolled off screen or hidden by various means with CSS). It's possible that Silk could preferentially send the visible assets (images etc.) first, then stream in the rest gradually in preparation for scrolling/zooming or interacting with the page, rather than just sending them in the order they show up in the HTML. The browser would eventually get all the assets, but it would get the visible stuff first. (I'm not sure about that, just speculating.)

      Some complex Javascript could be pre-processed and optimized for both performance and code size before being sent to the browser. (For instance, it could omit code that is never called.)

      It might also pre-fetch and pre-process (in the cloud) a variety of pages linked from the current page, so they are ready to send quickly from the EC2 cache as soon as you click on the link, and maybe even pre-send certain assets to the phone so they're already waiting on the device itself before you've even opened the page that needs them. And it keeps open persistent connections to popular sites so that it can fetch content from them more quickly than usual (doesn't have to do new DNS lookup or negotiate a new HTTP connection every time).

      Further, it caches many common components from popular sites (images, videos, Flash, etc., maybe even CSS/JS) as shared assets, so you can get those quickly even if you've never visited the site before, so long as someone else has.

      They claim to have paid great attention to not serving up "someone else's" customized content by mistake, though I'm still very concerned over the decision to form a man-in-the-middle for HTTPS connections.

  50. Losing control of Analytics by eefsee · · Score: 1

    It actually appears to me that this is a significant challenge to Google, and any of the rest of us who depend on web analytics. Silk not only renders on the cloud, but fetches content (even whole pages) predictively for the user. In other words, Silk will hit my website even if the user has not "clicked" on my link. How can I (or Google) tell whether the "GET" is predictive or actual? Furthermore, since Silk is doing much of the rendering in the cloud, how can I be sure that my content is actually getting through (ads, for example, could be modified or replaced).

    None of this is new, others have been able to do this to varying degrees for years. But the scale is new. Amazon will sell millions of Fire readers, and who is to say that Silk will remain limited to just Fire and its descendants? What if Amazon eventually releases Silk as desktop technology. I actually think Fire is the first trial of a technology that Amazon intends for much wider distribution. Why not? It can already claim great success in bringing significant web properties into the Amazon cloud, promising Silk integration will only strengthen that position. Imagine: your user can get to your website without even using the internet! The whole interaction can be in the Amazon cloud. The net is only used to cover the "last mile" to the browser.

    Silk is a major play for Amazon. Possibly bigger than Kindle itself.

  51. Apple Newton was doing this in 1995 by davidwr · · Score: 1

    OK, it was ALMOST doing this in 1995, if you count a serially-attached Macintosh as "the cloud."

    A researcher at some university (The University of Michigan I think) developed a Newton web browser that was just a "front end" to an engine on a Macintosh.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  52. Dear Research In Motion by markdowling · · Score: 1

    Please do a Silk-On-BES. Offloaded processing, but on our servers and not those of Amazon's data miners. For handhelds and Playbook.

    Love and kisses, the people who gave you $,000s for BES licenses.

  53. Re:Not sure how long this will be useful (if at al by hunangarden · · Score: 1

    What gives you any idea that this is what they will be doing? I didn't see anything about them rendering in the cloud. Maybe caching or pre-fetching html based on predictions, but not rendering.

  54. Re:Not sure how long this will be useful (if at al by matthewv789 · · Score: 1

    No, that's not how it works at all.

  55. Re:Offline Access? by Belial6 · · Score: 1

    IBM Domino with DOLS enabled will do it. Sure it won't let you surf to new sites that you haven't visited before, but it will let you use an entire web based application while disconnected, and interact with the application as if connected. When you do connect, any data that was updated will synchronize with the server.

  56. Re:Offline Access? by amRadioHed · · Score: 1

    So what's that have to do with Amazon Silk? No other web browsers have that functionality built in either.

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  57. Re:Offline Access? by Belial6 · · Score: 1

    DOLS make IE and Firefox have that capability.

  58. Re:Offline Access? by amRadioHed · · Score: 1

    And why couldn't Silk have it as well? It would be able to fall back to it's local rendering and work like any other browser.

    --
    We hope your rules and wisdom choke you / Now we are one in everlasting peace
  59. Re:Offline Access? by Belial6 · · Score: 1

    There is no reason it couldn't. The browsers always work from local rendering. DOLS is in essence, a server wrapped as a plug in.

    Of course, I was never speaking specifically of Silk. Just of the fact that offline web browsing of active content isn't impossible, and actually exists today.

  60. Re:You guys seem to be forgetting the pre-fetching by hkmwbz · · Score: 1

    How is pre-fetching relevant? It's just another thing they are doing which they ripped off from another browser, just like they ripped off Opera Mini/Turbo. Just because they are combining them into one product doesn't make either of them a revolution, contrary to Amazon's silly claims.

    --
    Clever signature text goes here.
  61. Re:Prior Art - Opera Turbo by hkmwbz · · Score: 1
    So because Opera's compression uses different hardware than Amazon's compression, Amazon's compression is a huge innovation and never seen before in the entire world?

    Right.

    This isn't new tech, and it sure as hell isn't revolutionary, considering that Opera and others have been doing it for ages.

    --
    Clever signature text goes here.