Comment: Re:Explains why no native SDK (Score 1) 267
[...] Given that Windows 8 demonstrably can execute even in 128MB RAM [...]
And by that you mean in 128MB RAM with 1GB of swap, which is not the same at all.
[...] Given that Windows 8 demonstrably can execute even in 128MB RAM [...]
And by that you mean in 128MB RAM with 1GB of swap, which is not the same at all.
It has to be decrypted to be displayed. There is always a way to tap into that. DRM fails again.
Developpers needs to stop using int's when unsigned int's would have done the job.
Then all those "oh god, we did not anticipate a negative number here!" bugs would be fixed already.
What other libavcodec-based player would you suggest then?
I believe you could before XP Service Pack 2 (which kinda reinforced security).
Code using the managed syntax will not compile in a standard C++ compiler, and code using the unmanaged syntax will compile to CIL that fails verification.
Nothing that can't be fixed through abuse of preprocessor macros, though.
Damn. I really should have read TFA before posting.
That application will not pass the approval process because it downloads stuff and runs it... quite against the requirements for apps, if I recall.
The problem with old programs are all the unpatched security holes.
I might not want the new and shinier version, but I sure do want to use a version that's still being updated when the next 0-day comes.
But then, crappy programmers misuse them, not knowing about what is done behind their back, and it becomes slow and bloated code.
Having to specify everything explicitely makes you aware of the complexity/memory usage of what you are doing.
That feeling just came over me. -- Albert DeSalvo, the "Boston Strangler"