TaintedHotSauce
Member
1) The PS4 has a OpenGL desktop, a browser is loaded at all times so Netflix will act like a browser app and only keep a bookmark on the PS4.
2) Netflix will use the HTML5 <video> with media extensions so streaming a movie will use the already loaded player and Playready.
3) A few K and a temporary cache for the artwork.
A console only has fixed hardware so suspend/resume should be very easy...that it hasn't been implemented has implications and my explanation is the most likely.
Oh, why is Netflix currently just slightly under 1GB in size?
Okay let's go through this one by one.
1) The PS4 has a OpenGL desktop, a browser is loaded at all times so Netflix will act like a browser app and only keep a bookmark on the PS4.
PS4 has an OpenGL desktop? What does that mean? Why would Sony use OpenGL for their UI and not their own libgnm? What's your source on that?
Netflix will act like a browser app and keep a bookmark on the PS4? Huh? So Sony's going to ditch the Netflix app and use a browser based Netflix? Again, where's your source on this?
2) Netflix will use the HTML5 <video> with media extensions so streaming a movie will use the already loaded player and Playready.
Again, where's your source on this? You're again saying Sony will ditch the current Netflix app for an HTML5 based web implementation. What advantages would this have and why?
3) A few K and a temporary cache for the artwork.
Ugh. I guess this goes back to your "Sony is going to ditch the Netflix app for a web-based HTML5 implementation for god knows what reason".
A console only has fixed hardware so suspend/resume should be very easy...that it hasn't been implemented has implications and my explanation is the most likely.
So your argument is "Well, it should be easy and since it hasn't been done, my explanation is the most likely one". That's a very sound, well-reasoned argument there.
Oh, why is Netflix currently just slightly under 1GB in size?
Huh? What are you trying to convey?