Yes, but some would argue that in a programming language, "different things should look different".
While I agree with you in the context of a programming language, others may try to argue by extending the computer science and unix concept of transparency to programming languages. "We do not need to know if this file is local or on an nfs share"->"We do not need to know if this is an array or a hash, as long as we can do X to it"
Please ignore the fact that the quote is about Perl.
If the world were programmed in perl, there would be no war, only hippies, and the world would be at peace.
EDIT: and the only people in prison would be Ruby coders.
JamesM wrote:
If the world were programmed in perl, there would be no war, only hippies, and the world would be at peace, poor, unintelligent, and without today's technological state.
Fixed. Even Utopia has sides that dumbass liberals forget to consider in light of the "one good argument leads to a solution" theory.
Yes, but some would argue that in a programming language, "different things should look different".
While I agree with you in the context of a programming language, others may try to argue by extending the computer science and unix concept of transparency to programming languages. "We do not need to know if this file is local or on an nfs share"->"We do not need to know if this is an array or a hash, as long as we can do X to it"
Well there's nothing wrong with either case if you can use it in exactly the same way, but personally i prefer to be able to 'know' which is which in any case.
JamesM wrote:While I agree with you in the context of a programming language, others may try to argue by extending the computer science and unix concept of transparency to programming languages. "We do not need to know if this file is local or on an nfs share"->"We do not need to know if this is an array or a hash, as long as we can do X to it"
Or, to paraphrase, "there should be fewer different things". While true in theory, practical concerns (like performance) require trade-offs.
Top three reasons why my OS project died:
Too much overtime at work
Got married
My brain got stuck in an infinite loop while trying to design the memory manager