On the other hand, trying too hard to shoehorn semantic descriptions on names ends up with pathological cases (yes, chemistry, I’m looking at you!).
Jokes apart, words are symbols that even if they have some semantics through etymology, in general they are quite arbitrary. I’d rather go with outlandish names that help mnemonics, if I were to choose. Names from people can serve that purpose; I still remember what a Kohonen map is, back from Uni, because of the childish resemblance with “cohone” (Andalusian for cojones), and a silly joke from a close friend.
But if we choose words that are famous names, they are far less likely to be systematically used as a building block. And woe be to us if that individual invents too many things, because then the meaning of their name will be too ambiguous.
Putting forth an idea to an audience without rigorous proof does have intrinsic value.
Further, if said idea implies that the audience is exceptionally good, you don't really need the proof, do you? The value for the audience is obvious :)
Naïvely, writing only one logic relation of n parameters is about equivalent to writing n^2 functions (just decide for each parameter whether you give it or not as input). So there clearly is value there.
I say naïvely because on one hand you might not need all versions of the function, but on the other one you can also provide partial values, so it’s not either input or output.
Well to be pedantic: the time-keeping part isn’t the gears but a pendulum.
The spring gives energy to the pendulum, but that can’t effect more than in its amplitude: the period of a given pendulum is constant. Later springs demultiply the tick tack of the pendulum into desired units.
The heart of the clock is that choke on energy though a period.
Thats also why the famous phrase: clocks dont measure time but other clocks.
This work describes a general, scalable method for building data-parallel by construction tree
transformations that exhibit simplicity, directness of expression, and high-performance on both CPU and GPU architectures when executed on either interpreted or compiled platforms across a wide range of data sizes, as exemplified and expounded by the exposition of a complete compiler for a lexically scoped, functionally oriented programming commercial language. The entire source code to the compiler written in this method requires only 17 lines of simple code compared to roughly 1000 lines of equivalent code in the domain-specific compiler construction framework, Nanopass, and requires no domain specific techniques, libraries, or infrastructure support. It requires no sophisticated abstraction barriers to retain its concision and simplicity of form. The execution performance of the compiler scales along multiple dimensions: it consistently outperforms the equivalent traditional compiler by orders of magnitude in memory usage and run time at all data sizes and achieves this performance on both interpreted and compiled platforms across CPU and GPU hardware using a single source code for both architectures and no hardware-specific annotations or code. It does not use any novel domain-specific inventions of technique or process, nor does it use any sophisticated language or platform support. Indeed, the source does not utilize branching, conditionals, if statements, pattern matching, ADTs, recursions, explicit looping, or other non-trivial control or dispatch, nor any specialized data models.
I have a hard time accepting that some of those are what trips people. That a something called “file” is in one place (device or particular location) seems more readily understandable than an ethereal thing that’s (sometimes, to some degree, at some resolution) ubiquitous.
The format topic is also something that I see causing frustration, but it is not complicated to understand, as long as someone is familiar with the concept of incompatibility (screwdrivers, human languages, etc.)
In my opinion at this day and age is more an issue of “never needed to learn / cared to” than that of “it is difficult to learn”.
Jokes apart, words are symbols that even if they have some semantics through etymology, in general they are quite arbitrary. I’d rather go with outlandish names that help mnemonics, if I were to choose. Names from people can serve that purpose; I still remember what a Kohonen map is, back from Uni, because of the childish resemblance with “cohone” (Andalusian for cojones), and a silly joke from a close friend.
reply