| Expanded path | |
| Importance | |
| Almost all existing software and net IP is stupid vulnerable to me. This is one of the pervasive things that result in a new paradigm and language. There is no easy fix. | |
| Problem | |
| It is quite hard to come up with a dynamic location scheme for objects. At Internet address level, this problem leads to ICANN. At computer file system level, it leads to fixed paths and path variable. etc.. | |
| My solution | |
| Every name is a pair. The first part must be resolved once, or on command. As it is, per machine, "dir" is used expecting a filename of equalpairlines of a dirname and what it stands for. There is also a "metadir" per tool that allows this map to be tool specific. These maps are used to expand paths. | |
| File name application | |
| The object names may be different for development "d:\bigdrive\..." and for sales transportation "a:\..." and some convenient path in customer machine. Even the tree structures may be different. | |
| Internet application | |
| An object referred to in a htm document may be anywhere, depending on the pathmap of the giant dynamic Internet tree which is a separate file periodically autogenerated and sold. | |
| Site application | |
| ICANN is an organization of nuts looting you big. The first part of a name corresponds to a domain word, second to a name. Each domain has a set of rules on who can get what name. These rules DON'T have to be even similar - if you don't like them, don't go for it. Only domain names must be assigned based on common rules. Simplest and solves ALL problems is to always have the two letter country prefix followed by a common semantic domain name. Thus ustm/foo says us trademark rules label foo, in person/arun-arya says india person rules label arun-arya, usperson/arun-arya is us person rules label arun-arya. These are unambiguous, free from cyber-squatting, free of lawyers and courts, implemented, will be applied regardless of morons for internet goes everywhere and I can now match by ANSWER all viciousness, famililial permanent counter-sue of inappropriate sue-persons.. | |
| Organization application | |
| A company is a recognizable multiarchy of people. The mapping of persons and applicable rules to them is an unnecessarily hard administrative problem with serious legal consequences and bad blood between employees and managers. What I propose is simple: function indexed rules that can be automatically , reliably, fast, accurately, relevantly and applicably made available incrementally to effectees only following every reorganization. | |
| More application | |
| Don't tell me about them! You will get no return! Only if you want to debate the issues, and I am game to the debate, then we can debate with no expectations. Just remember, I passionately hate lawyers. | |
One of the difficult questions I have solved is this: given A and B, are they the same language or not. The simplest solution is to abandon the use of word-language itself into <x>-cantfake-language. <x> is a term with semantics given by a series of tests. cantfake ensures credit for me and forbids quiet unauthorized extension for you.
pervasive cantfake language is one that can not be reasonably implemented as a preprocessor or library enhancement to another. Automatic garbage collection is a pervasive cantfake issue in that no amount of tweaking the library of another language without this feature will get you it. Object orientation is another. The lists itself is crucial development for it related to intelligent predictions of tomorrow - not based on empirical extrapolations that managers excel in and are unnecessarily eulogized by management schools for money, who shamelessly refer to reality of development as disruptive technologies. Like lawyers, there is always the breakfast cereal of judges!
| Pervasive cantfake issue | example language | deserving victims |
| Dependent Initialization | cantfake | cpp |
| Multiple Inheritance | cantfake | java |
| true distribution | cantfake | all software |
| Automatic garbage collection | java, c# | cpp |
| object orientation | cpp, small talk | C |
| structured programming | C, Pascal | fortran |
Suppose some one sent you a letter with nice graphic. The thing may work for a while, then no more!
Company foo let you get some space, Now they want money. Other than all the uploading effort, you mailed letters with links to this place!
You have some spiffy thing to sell. You got it on your machine. How do you transport it to potential buyer? Why does the buyer have to conform to your structure!
You paid for a program, installed it, reorganised your files, and program works no more! Especially upsetting when all you did was to buy a bigger disk!