Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Stagefright or C/C++fright?

Name: Anonymous 2017-07-30 18:09

There is a technique called stagefright that can exploit a system by playing a video, but this is not an MPEG problem or any other video format problem. It's a C and C++ problem. Malformed data causes a C or C++ program to behave unexpectedly. The C and C++ languages not only cripple your mind, your operating system, and your hardware, they allow invaders to take over your machine by doing simple things like watching a video or generating thumbnails.

Name: Anonymous 2017-07-31 15:18

>>13
Of course it isn't. The distinction is that the language can exist on paper or any other medium and the operations can likewise be executed on paper. If someone doesn't understand this very simple distinction then perhaps they really have no idea what they are actually doing when they write a program.

If you wish for a language to become broadly adopted then it will most certainly have many implementation in order to function on different computing architectures.
>>14
This is untrue and makes some useless assumptions. Whether a technical standard requires a compiler to behave a certain way is simply specification stipulation that affects implementation conformity nothing more. These sorts of arguments are reminiscent to the arguments that people have given for their preference of Python. They will say things such as "I can do a whole bunch of shit in just one line of code with one function call" and "there are so many easily found libraries that do all the things I want."

Those are some pretty dumb arguments of course. There is nothing that limits a C program or a C library from implementing those things or the things discussed in this thread. There is nothing about a programming language that will somehow extend the capabilities of a computer any more than a program written on paper will create extra pages in your notebook.

Emulating existing syntactical paradigms and primarily attacking vulnerabilities in very specific libraries on very specific implementation for specific machines wont get a fad language anywhere. With some luck continuing down that path will make RUST the next Ruby. Then business executive can spend thousands of dollars learning some new buzzwords together in a classroom with champagne and appetizers. A glorious future no doubt, moving on ...

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List