987 karma · joined March 2, 2013
"when an Indian Navy helicopter tried to recover them from the beach, the Sentinelese fought it off with bows and arrows"
Indian Navy should feel ashamed! :D
Lying is dishonorable, counterproductive in context of multiple cooperating people, and a really bad idea overall, purely objectively. Swearing, linguistics-wise, is indeed a completely normal ("natural and ok") trait (present to some extent in individuals of all cultures, gender, professions etc., even in some higher animals) that is orthogonal to anyone's performance. How could you possibly equate these two is beyond me.
That does not necessarily have to be the case. Just like you have abstract collections capable of handling values of any type, I don't see why it should be impossible to have a model of versionable, editable code into which you could inject your own implementations for the particular language you're coding in right now.
I realized the other day how close persistent collections and tools like Git actually are. And given how most modern languages have programs that are essentially trees or groves, and given that said persistent collections tend to be trees...? Well, what do you think?
Also, the drawback of anything written in this way is that it doesn't compose well. The individual operations may well have been optimized into oblivion, but their composition may not necessarily be what you'd like it to be. One can also say goodbye to higher-order functions. But I'm not exactly a Fortran person when it comes to code style, so I may be prejudiced against overly loopy code.
(BTW, am I the only one who thinks that the Sourceforge (http://sourceforge.net/projects/math-atlas/) comments are machine-generated? I mean, comments like "An essential Windows program." or "The best program that I've ever used." are hardly what I'd expect for a numerical library.)
What you probably meant was that ATLAS and BLAS are implementations of the right way, not the way itself. Because the alternative would be really, really sad.
Did you compose this text with the help of Google Translate, then?
English may not be easy to copy but it's comparatively "bland". "Bland" in this case means "has a smaller number of marked features". For example, it has no tones. It's always easier for someone speaking a tonal language to learn a toneless language than the other way round. Sanskrit has a complex system of synthetic inflection, which is a rather marked feature, and all speakers of analytic languages would hate your guts for forcing it onto them if you tried to make them learn it. In many ways, Sanskrit is like Ancient Greek. You spend a year learning something that other languages can do without (and do so without muddling the meaning of the text), and even if you learn it, you'll still be doing mistakes quite a lot of the time. Such a language would never have a chance of spreading as an international medium of communication.
Also, the notion that the PIE reconstructions describe a "language" in the sense that we usually understand it (a vernacular tongue of a group of people in a single time and place) is a false one: even though the reconstructions with very high likelihood represent individual IE language features in an old form thereof, it would be a folly to try to slap them together and say "this is a language that someone spoke", for the same reason you can't reconstruct individual genes from the tree of mammals, slap them together and say "this was the first mammal". It doesn't work like that. What you get is a constrained probability function over possible languages, not a single solution with 100% probability.
What do you propose as a low cost solution? I've seen some interesting suggestions, such as having a small fish bowl or tube or tank, having air pumped into the bottom, and sampling the patterns of bubbles with some CV solution. Sounds geeky, would make for a nice decoration on one's table, but building it seems like quite a job.
Not even that. It's about making thing easiest for metaprogrammers.
What else would you suggest?
Why not fuse the operations, if the values are immutable?
What? Pure untyped lambda calculus does things "only with syntactic forms". Don't tell me that your solution wouldn't use some basic operators other than rudimentary syntax. Keep in mind that in Lisp-family languages, many things that are a part of syntax in other languages are actually simple functions - arithmetic operations being a case in point - so you really can't avoid using library functions.
I believe that the major point of Clojure etc. is that they provide concise basic operations that you can use everywhere to compose complex operations better than you can do with, say, C#.
Wouldn't that de facto qualify as a contempt of court?
Here, fixed that for you. (Pilot projects on a large scale are useful to all of us. Someone has to finally do it.)
Yes, especially people with childhood dreams of studying history or art will be turned on by the prospect of designing airliners and nuclear reactors.
Almost - not who but _why.