http://www.bankofcanada.ca/wp-content/uploads/2010/11/why_ca...
6,856 karma · joined October 29, 2012
http://www.bankofcanada.ca/wp-content/uploads/2010/11/why_ca...
No more silly than pretending the the abstraction of "files" and "directories" is reality. No more silly than pretending that your computer is running a Python program, when in reality there are sequences of machine language instructions being run. Computers are useful because of abstractions.
"There is no Internet, just a bunch of private networks connected together"
You might have missed the definition of "an internet:"
https://en.wikipedia.org/wiki/Internetwork
There is, in fact, an Internet that we use every day. The overwhelming success of the Internet is due to the abstraction it presents, which is best-effort routing of packets from one host to another -- without regard for what networks the hosts are connected to, what arrangements govern their connections to those networks, and perhaps most important of all, what applications those hosts are running. On the scale of positive improvements to human communication, the Internet is up there with the printing press and written language.
"Now that real money is in play, the fiction of the internet is crumbling and the physical nature is becoming exposed."
No, what we are seeing is the impact of years of systematic attacks on the Internet by companies that are desperate to protect obsolete business models. Comcast is worried about the imminent demise of cable TV and all the power and profit that came with it. AT&T is worried about the demise of long distance fees, roaming charges, SMS charges, and all the power and profit that came with controlling the phone system. The recording industry and movie industry worked hard to leave the Internet divided into "consumers" and "services," even though the system itself was designed to be far more general.
In short, had we told these companies to adapt or die rather than tolerating their efforts to roll back the clock, we would not be in the situation we are in today. This has nothing to do with leaky abstractions, physical limitations, or the design of the Internet. It is just a power grab, a systematic effort to destroy a good thing that threatened the entrenched players.
Really, the point of the Internet is that you can communicate with other Internet users without having to worry about what ISP or network they are connected to or what arrangements govern that connection.
This needs to be emphasized more. We rarely get to choose between equally cost-effective ISP options. The typical choice is one cable company, one phone company, and some kind of wireless service (possibly satellite). That is not competition, any more than heavy truck sales compete with mo-ped sales.
Funny, back when I was a Comcast customer, I do not remember paying for "Comcast Network Access." I remember paying for "Internet Access;" sure, I went over Comcast's network, but I (maybe naively) thought that such distinctions were irrelevant on the Internet (that was kind of the point, if memory serves).
No, it seems to discuss something else. It starts out talking about blind signatures, then veers off with claims like this:
"The novelty of the scheme is that unlike the original Chaum blind signature scheme, this one does not allow anyone to prove that the signing party signed a particular message"
I am not actually sure what you are trying to say there. Does it mean that I can only narrow down the possible signers to some group? Does it mean that the signature key is ephemeral, yet somehow meaningful?
To put it another way, what differentiates your proposal from this:
https://eprint.iacr.org/2011/402.pdf
""Multiparty computation" with "threshold system" here are provided by Bitcoin automatically, "
What? Where? Citation needed.
That is not a security through obscurity success story. The Skype design was changed by Microsoft in a way that made government access easier.
"How does the company convince you that it is using best practices without compromising its competitive advantage?"
Your competitive advantage is not my problem. I need a secure voting machine, a secure ATM, a secure medical database, etc. If you cannot deliver a secure system to me in a way that allows me to verify its security, then you never had a competitive advantage in the first place.
Frankly, almost none of the C++11 features are actually useful for teaching data structures, and those that are relevant would only confuse students. Basically, only auto and the three kinds of smart pointers are relevant to an introductory data structures course. At the end of the day those would only create as many problems as they solve. For example, unique_ptr means that there is only one "owner," right? Wrong, get() returns a raw pointer to the object, and you can make a new unique_ptr from that. Sure it is easy to avoid -- if you are an expert with lots of C++ experience, who follows coding guidelines and all that. The data structures students had little to no C++ experience and would almost certainly have done what I just described -- and that is just one of many ways they can and will screw up C++11 features.
At the end of the day, C++ is too complicated, too poorly defined, and has all the wrong abstractions for basic CS courses.
I disagree. There is a rich theory of cryptography that is entirely abstract, for which the low-level details are an irrelevant distraction. Even the AES finalists, which were designed with low-level concerns in mind, are described abstractly and can be implemented at a high level (I have an implementation of Serpent in Common Lisp, for example -- no messing around with low-level details, just a functionally correct block cipher). Within the crypto research community there are people who work on high-level languages suitable for cryptography implementation:
http://www.charm-crypto.com/Main.html
To be fair, there is also an enormous body of work on implementing cryptosystems in the real world -- at least enough to have an entire course dedicated to the topic. If anything, we should really have two courses: an introductory course that covers the theory of cryptography, and a cryptography engineering course that deals with real-world implementations.
The thing to keep in mind is that the changes that web companies make to free software are not usually for internal consumption. The changes are user-facing -- but the software is delivered via the web, rather than distributed to the users, and so the web company never triggers any requirement to make their changes available. The GPL does allow this, but it is not in the spirit of the GPL, and the Affero GPL was created to deal with this problem.
Why is it important to teach the underlying mechanics of a computer in a data structures course, or an algorithms course, or really anything beyond OS or computer architecture courses (and perhaps a compilers course)? The reality is that the way computers work "under the hood" is counterintuitive in an extreme sense. Pointers are a counterintuitive abstraction. Fixed-width arithmetic is counterintuitive, as is having integer division always round down, as is using floating pointer numbers to represent fractions. Yes, eventually a CS student should learn about these things -- but an introductory course is the wrong place, as is basically anything that deals with purely abstract notions (data structures, algorithms, cryptography, etc.).
In my experience TAing an undergrad course that used C++, almost all of the things that left students scratching their heads were things that are present in C. No garbage collector, no built-in way to determine array sizes at runtime, no way to determine if a pointer has already been deallocated, no requirement that non-void functions actually return a value on all control paths, etc. The worst thing C++ does is to amplify these problems (particularly that last one -- yes, I know, use -Wall, but someone who is just starting to use a language would not know that, and having to teach compiler flags is an even worse distraction from the subject matter of the course).
Really the problem is not language size at all. Python is a big language too, but it does not have the above problems. Common Lisp is just as big as C++ (in terms of the number of pages in the standard), yet these are not problems Lispers have. Scheme is a small language, like C, yet the elegance and expressive power of Scheme is on a completely different level from C.
The problem is that the few abstractions C presents are hard to deal with, especially for beginners, and the abstractions that C could present are sorely missed. Even the abstractions C presents are unreliable, with loads of undefined behavior and plenty of ways to break the abstractions.
Really, the fact that real-world C programmers have to pick a subset of the language and enforce various style standards and coding conventions speaks volumes about the suitability of C for beginners. If we were going to require students to use a specific subset of C, why not just write a compiler for that subset and use that to teach? The answer is pretty clear: if we were going to write a compiler for a new language that was suitable for teaching students, we would write something better. Why bother when we already have better languages to choose from? Save C for the OS course, and only as long as it remains relevant there.
As for preferring one data structure over another, C does that as well: arrays are the only data structure with first-class support.
https://en.wikipedia.org/wiki/Scheme_%28programming_language...
(Otherwise I agree, start with something like this to learn CS)
I say this as someone who watched the catastrophic results of trying to use C++ as a language to teach data structures. It is far more important to be able to think abstractly than to know how to deal with pointers.