"VAXocentrism" meaning in English

{
  "etymology_text": "See -centrism.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "VAXocentrism (uncountable)",
      "name": "en-noun"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "noun",
  "senses": [
    {
      "categories": [
        {
          "kind": "other",
          "name": "English entries with incorrect language header",
          "parents": [
            "Entries with incorrect language header",
            "Entry maintenance"
          ],
          "source": "w"
        },
        {
          "kind": "topical",
          "langcode": "en",
          "name": "Computing",
          "orig": "en:Computing",
          "parents": [
            "Technology",
            "All topics",
            "Fundamental"
          ],
          "source": "w"
        }
      ],
      "examples": [
        {
          "ref": "1991, Jay Maynard, “Segmented Architectures ( formerly Re: 48-bit computers)”, in comp.arch (Usenet)",
          "text": "There's nothing that says that array elements in FORTRAN - or, for that matter, C - have to be contiguous. Thinking that that must be true as a matter of Natural Law is purest VAXocentrism.",
          "type": "quotation"
        },
        {
          "ref": "1993, David P. Murphy, “modifying a literal string in C code”, in vmsnet.alpha (Usenet)",
          "text": "i've long insisted that everyone here at NPRI *always* redefine that psect to be readonly under VAX/VMS . . . our code gets ported to other platforms, and it would be definite vaxocentrism to assume that literal strings are writable.",
          "type": "quotation"
        }
      ],
      "glosses": [
        "The incorrect assumption that certain behaviours and memory storage conventions of the VAX (a computer system of the 1970s) are applicable on all computer architectures."
      ],
      "id": "en-VAXocentrism-en-noun-RGxBNI17",
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "assumption",
          "assumption"
        ],
        [
          "memory",
          "memory"
        ],
        [
          "storage",
          "storage"
        ],
        [
          "convention",
          "convention"
        ],
        [
          "applicable",
          "applicable"
        ],
        [
          "architecture",
          "architecture"
        ]
      ],
      "raw_glosses": [
        "(computing, slang, rare) The incorrect assumption that certain behaviours and memory storage conventions of the VAX (a computer system of the 1970s) are applicable on all computer architectures."
      ],
      "tags": [
        "rare",
        "slang",
        "uncountable"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "VAXocentrism"
}

{
  "etymology_text": "See -centrism.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "VAXocentrism (uncountable)",
      "name": "en-noun"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "noun",
  "senses": [
    {
      "categories": [
        "English entries with incorrect language header",
        "English lemmas",
        "English nouns",
        "English slang",
        "English terms with quotations",
        "English terms with rare senses",
        "English uncountable nouns",
        "en:Computing"
      ],
      "examples": [
        {
          "ref": "1991, Jay Maynard, “Segmented Architectures ( formerly Re: 48-bit computers)”, in comp.arch (Usenet)",
          "text": "There's nothing that says that array elements in FORTRAN - or, for that matter, C - have to be contiguous. Thinking that that must be true as a matter of Natural Law is purest VAXocentrism.",
          "type": "quotation"
        },
        {
          "ref": "1993, David P. Murphy, “modifying a literal string in C code”, in vmsnet.alpha (Usenet)",
          "text": "i've long insisted that everyone here at NPRI *always* redefine that psect to be readonly under VAX/VMS . . . our code gets ported to other platforms, and it would be definite vaxocentrism to assume that literal strings are writable.",
          "type": "quotation"
        }
      ],
      "glosses": [
        "The incorrect assumption that certain behaviours and memory storage conventions of the VAX (a computer system of the 1970s) are applicable on all computer architectures."
      ],
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "assumption",
          "assumption"
        ],
        [
          "memory",
          "memory"
        ],
        [
          "storage",
          "storage"
        ],
        [
          "convention",
          "convention"
        ],
        [
          "applicable",
          "applicable"
        ],
        [
          "architecture",
          "architecture"
        ]
      ],
      "raw_glosses": [
        "(computing, slang, rare) The incorrect assumption that certain behaviours and memory storage conventions of the VAX (a computer system of the 1970s) are applicable on all computer architectures."
      ],
      "tags": [
        "rare",
        "slang",
        "uncountable"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "VAXocentrism"
}