run a business without paying the traditional costs in the field and socialize your costs. in this case he wants every internet customer to pay for his bandwidth whether they use netflix or not.
ISPs chose their flat-rate business model; Netflix didn't force it on them. If that business model no longer works, ISPs should switch to a different one.
There are two different ways to do network display: the RDP way and the right way. With RDP you're sending the entire "screen" over the network, so all the windows have to be composited first. Thus RDP requires a fully featured compositor like Weston on the remote end.
The right way is to send each window over the network, which should require a lightweight compression proxy. No one appears to be working on this.
I think Google intends to put it in the kernel once they have finished actually designing and standardizing it. Since it would take 10-15 years to get QUIC into the Windows kernel, they're putting it in Chrome as a stopgap.
QUIC uses an equivalent of SYN cookies to prevent some kinds of DoS. It also uses packet reception proofs to prevent some ACK spoofing attacks that TCP is vulnerable to. Overall it looks even better than TCP.
As for encryption, Google gives two reasons. They intend to run HTTP over QUIC and Google services are encrypted by default; it's more efficient for QUIC itself to implement encryption than to layer HTTP over TLS over QUIC. The other reason is that middleboxes do so much packet mangling that encryption is the only way to avoid/detect it.
The rover loses 30% of its value as soon as you drive it off the lot. And if NASA tries to trade it in I bet a lot of "damage" will be discovered to drive down the price.
I used to have an N900 running Maemo with "true multitasking". A poorly-written app in the background (like Firefox with the "full Web experience" of Flash) would run down the battery in two hours. But at least I could use top to find the problem and kill -9 it.
Now I use Android where apps are specifically written to be aware of my battery.
That was kinda my point; people with a 15 GB cap will not sign up for Netflix at all. They won't sign up for Netflix, blow their cap, and pay $100/month in overages. So Netflix does not cause ISPs to earn more money.
But since most ISPs are either unlimited or have such punitive overage charges that customers will never pay them, greater demand for bandwidth generally does not translate into more revenue for ISPs. Even the lowest tier 5 Mbps plan is sufficient to watch Netflix.
In low-cost systems the CPU and GPU are combined on a single chip with a single (slow) memory controller. Given that constraint, AMD is trying to at least wring as much efficiency as they can from that single cheap chip. I salute them for trying to give customers more for their money, but let's admit that this hUMA thing is not about breaking performance records.
Yeah, I'm thinking 30" monitor + keyboard + mouse, apps that aren't forced full screen, a real file system instead of crippled sandboxes, etc. If tablets can deliver that, more power to 'em, but I doubt it.
Even years from now there will still be a few people who do actual work, and they won't be using tablets to do it. They'll be using computers and they'll need an OS which is optimized for productivity, not gaming, watching movies, tweeting, or shopping at Amazon. Few as they are, these people are willing to pay real money for a computer, like $2,000. Perhaps that is what GNOME and KDE should focus on, considering that Microsoft, Apple, Google, and Canonical don't care.
The reported reasoning for making Wayland support Android GPU drivers was difficulty in ODM vendors not wishing to offer driver support for platforms aside from Android.
ODMs don't know how to write software, so you're better off not asking them to; the result would just be garbage anyway. All the GPU drivers are actually written by the GPU IP vendors (Qualcomm, Imagination, ARM, etc.) and they only provide Android drivers. You could try to pay them to write KMS/DRM drivers, but they'd probably quote you a price in the millions which minority platform wannabes like Jolla could not afford anyway.
Back in the pre-DLC days they would have developed the ending but cut back on the middle of the game. I'm not aware of any games where critical mechanics are DLC; wouldn't that make the base game unplayable?
Slashdot Mirror
Like how people weren't bothered by Y2K bugs? Let's not repeat that every century.
Start at != fully loaded.
run a business without paying the traditional costs in the field and socialize your costs. in this case he wants every internet customer to pay for his bandwidth whether they use netflix or not.
ISPs chose their flat-rate business model; Netflix didn't force it on them. If that business model no longer works, ISPs should switch to a different one.
Nah, Netflix used to use other CDNs. But then they got big enough that it was cheaper to build their own.
That's orthogonal to the issue that (in most people's opinion) no CDN should have to pay broadband ISPs.
There are two different ways to do network display: the RDP way and the right way. With RDP you're sending the entire "screen" over the network, so all the windows have to be composited first. Thus RDP requires a fully featured compositor like Weston on the remote end.
The right way is to send each window over the network, which should require a lightweight compression proxy. No one appears to be working on this.
Immediately you say? Android users might disagree.
QUIC has congestion control. (I suppose your brain would explode if you saw uTP, which runs over UDP yet is even less aggressive than TCP.)
I think Google intends to put it in the kernel once they have finished actually designing and standardizing it. Since it would take 10-15 years to get QUIC into the Windows kernel, they're putting it in Chrome as a stopgap.
QUIC uses an equivalent of SYN cookies to prevent some kinds of DoS. It also uses packet reception proofs to prevent some ACK spoofing attacks that TCP is vulnerable to. Overall it looks even better than TCP.
As for encryption, Google gives two reasons. They intend to run HTTP over QUIC and Google services are encrypted by default; it's more efficient for QUIC itself to implement encryption than to layer HTTP over TLS over QUIC. The other reason is that middleboxes do so much packet mangling that encryption is the only way to avoid/detect it.
He's including free speech in civil rights. He supports free speech for everyone except fanboys and trolls.
You mean a workstation uses "not consumer" RAM? Tell me more...
The rover loses 30% of its value as soon as you drive it off the lot. And if NASA tries to trade it in I bet a lot of "damage" will be discovered to drive down the price.
I used to have an N900 running Maemo with "true multitasking". A poorly-written app in the background (like Firefox with the "full Web experience" of Flash) would run down the battery in two hours. But at least I could use top to find the problem and kill -9 it.
Now I use Android where apps are specifically written to be aware of my battery.
That was kinda my point; people with a 15 GB cap will not sign up for Netflix at all. They won't sign up for Netflix, blow their cap, and pay $100/month in overages. So Netflix does not cause ISPs to earn more money.
A lot of BitTorrent traffic shifted to cyberlockers like MegaUpload a few years ago; I don't know if it has come back since then.
But since most ISPs are either unlimited or have such punitive overage charges that customers will never pay them, greater demand for bandwidth generally does not translate into more revenue for ISPs. Even the lowest tier 5 Mbps plan is sufficient to watch Netflix.
If by similar you mean 1/18th the performance.
In low-cost systems the CPU and GPU are combined on a single chip with a single (slow) memory controller. Given that constraint, AMD is trying to at least wring as much efficiency as they can from that single cheap chip. I salute them for trying to give customers more for their money, but let's admit that this hUMA thing is not about breaking performance records.
One of the problems with the PS3 is that it didn't have shared memory. Maybe you're thinking of the 360.
Yeah, I'm thinking 30" monitor + keyboard + mouse, apps that aren't forced full screen, a real file system instead of crippled sandboxes, etc. If tablets can deliver that, more power to 'em, but I doubt it.
Even years from now there will still be a few people who do actual work, and they won't be using tablets to do it. They'll be using computers and they'll need an OS which is optimized for productivity, not gaming, watching movies, tweeting, or shopping at Amazon. Few as they are, these people are willing to pay real money for a computer, like $2,000. Perhaps that is what GNOME and KDE should focus on, considering that Microsoft, Apple, Google, and Canonical don't care.
Wayland's native remoting protocol is under development but "only at the proof of concept state". http://cgit.freedesktop.org/~krh/weston/log/?h=remote http://lists.freedesktop.org/archives/wayland-devel/2013-April/008555.html
All the people talking about RDP keep in mind that that's a stopgap and won't be needed long-term.
The reported reasoning for making Wayland support Android GPU drivers was difficulty in ODM vendors not wishing to offer driver support for platforms aside from Android.
ODMs don't know how to write software, so you're better off not asking them to; the result would just be garbage anyway. All the GPU drivers are actually written by the GPU IP vendors (Qualcomm, Imagination, ARM, etc.) and they only provide Android drivers. You could try to pay them to write KMS/DRM drivers, but they'd probably quote you a price in the millions which minority platform wannabes like Jolla could not afford anyway.
Not really; they're just slow enough that power isn't a problem.
Back in the pre-DLC days they would have developed the ending but cut back on the middle of the game. I'm not aware of any games where critical mechanics are DLC; wouldn't that make the base game unplayable?