How about, say, specialized graphics hardware being implemented in separate chips for home computers, and then later being discarded in favor of using faster CPUs to do the rendering instead?
"Reasonable" stack size used to be a handful of kilobytes not too long ago. If you're just programming reasonably you will never, ever need even 1% of a one-megabyte stack.
Which means that even if you did allocate one megabyte for each stack, that memory would never actually be used. You'd still run into the 32-bit limit for the virtual memory space, though.
Of course, you can just allocate less stack space.
Also, coroutines need their own stacks just as much as threads do.
I wouldn't doubt that there's "cracks" for the Wii's SD card DRM that just haven't surfaced yet.
That makes no sense whatsoever. There's no reason at all to keep something like that hidden. The only thing it's good for is fame, and you don't get that by shutting up.
It's easy to make strong copy protection on custom hardware. Just use public-key crypto and keep the keys in hardware. That's what the Wii does, and nobody's managed to touch it yet. The only things we have so far are cumbersome workarounds using bugs in games, and hardware modifications, neither of which in any way attacks the algorithms used.
Like others pointed out, it's been possible to store games on SD for a long time now. Nobody's cracked the protection on those yet. You can't copy them, and you can't create your own and load them onto a card. Same goes for the Wii game discs.
There's plenty of DRM schemes out there that haven't been cracked. It's the ones that are added onto an insecure format as an afterthought that are easy to get rid of, like copy-protected CDs, or the lucky few that are just badly designed, like CSS on DVDs, that fall.
They also have to put the content back as soon as the uploader files a counter-claim.
Which makes it a far better law than not having it, in which case Youtube would have to take it down out of fear of being sued themselves, and wouldn't put it back up because they would be exposing themselves.
Damn them for not making their codebase absolutely perfect from day one! Software should spring into life fully formed, like Athena from Zeus' forehead!
Slashdot Mirror
and what would be an example for this?
How about, say, specialized graphics hardware being implemented in separate chips for home computers, and then later being discarded in favor of using faster CPUs to do the rendering instead?
Like what happened in the 80s and 90s.
Yes, hardware rendering looks so much better!
Here's a hint: They don't actually mean it. They are doing it for the sole purpose of getting you riled up, and you're playing right into their hands.
Doing it right would entail not being immature and giving it a stupid name out of spite.
A goddamn idiotic and immature rebranding, that is. The grandparent poster was suggesting doing it right.
And how, exactly, do you then suggest anybody do anything in exactly the same way twice?
I'll have to admit that it's been a long time since I've seen such a picture-perfect trolling.
"Reasonable" stack size used to be a handful of kilobytes not too long ago. If you're just programming reasonably you will never, ever need even 1% of a one-megabyte stack.
Which means that even if you did allocate one megabyte for each stack, that memory would never actually be used. You'd still run into the 32-bit limit for the virtual memory space, though.
Of course, you can just allocate less stack space.
Also, coroutines need their own stacks just as much as threads do.
I wouldn't doubt that there's "cracks" for the Wii's SD card DRM that just haven't surfaced yet.
That makes no sense whatsoever. There's no reason at all to keep something like that hidden. The only thing it's good for is fame, and you don't get that by shutting up.
It's easy to make strong copy protection on custom hardware. Just use public-key crypto and keep the keys in hardware. That's what the Wii does, and nobody's managed to touch it yet. The only things we have so far are cumbersome workarounds using bugs in games, and hardware modifications, neither of which in any way attacks the algorithms used.
Every DRM can and will be cracked though
Can? Probably. Will? Not so much.
Like others pointed out, it's been possible to store games on SD for a long time now. Nobody's cracked the protection on those yet. You can't copy them, and you can't create your own and load them onto a card. Same goes for the Wii game discs.
There's plenty of DRM schemes out there that haven't been cracked. It's the ones that are added onto an insecure format as an afterthought that are easy to get rid of, like copy-protected CDs, or the lucky few that are just badly designed, like CSS on DVDs, that fall.
Is this entire thing about how there really isn't any point at all in hacking this thing?
Gee, thanks for telling us!
Even the summary has lost interest by the time it reaches the last sentence.
A slashdotter is calling others "smug" now?
Oh wait, I forgot, Slashdotters are right, that makes it not count as smugness!
They also have to put the content back as soon as the uploader files a counter-claim.
Which makes it a far better law than not having it, in which case Youtube would have to take it down out of fear of being sued themselves, and wouldn't put it back up because they would be exposing themselves.
Worst haiku ever.
"Agenda" does not mean "profit motive".
There goes the worst little saying ever again.
You know, I threw some dice several times and I expected different results each time! I must be UTTERLY INSANE!
Except, you know, anybody with even an ounce of common sense could see this was just a mistake right from the start.
but if they're all using the same rendering engine underneath
They aren't. The Windows rendering engine Safari uses isn't fully open-sourced.
And how about "release early, release often"? Or how open source software has a much longer history of perpetual betas than Google?
Pretty good example of why comment hiding and comment threading really isn't a very good combination.
That one's a feature - it's warning you of utterly useless sites.
You know that comments on Slashdot can be replies to other comments, right?
So I take it you don't like open source software much, huh?
Except when they do, of course.
Damn them for not making their codebase absolutely perfect from day one! Software should spring into life fully formed, like Athena from Zeus' forehead!