Commons:Deletion requests/File:Computer abstraction layers.svg
Diagram does not make sense (it is mixing up various things) and is highly misleading. OS and applications are erroneously shown on same level of abstraction. Assembler is no abstraction layer at all, but a tool to translate assembly language into machine language. OS and applications are software as well. Firmware is a weak term, as it may include programmable logic. By other definitions it includes all software as well. What might have been meant might be an hardware abstraction layer like a HAL or BIOS, but this does not become clear at all. All in all, no matter how this diagram is interpreted, it is never correct and only confuses readers. Therefore, there's no point in keeping it. Matthiaspaul (talk) 21:37, 31 December 2016 (UTC)
Speedy keep: File uploaded un 2007 and widely un use, and I don'see any accurancy problems un the diagram. --Amitie 10g (talk) 03:36, 1 January 2017 (UTC)
- As an encyclopedia we have a responsibility not to spread false information. It is better to create a new diagram (or a set of new specifically tailored diagrams) than spreading fundamentally false information.
- This diagram is so confused, it is not like comparing apples and oranges, or apples and trees, but like comparing apples and cars.
- As I explained above, an "assembler" (in the context of computing) is a tool used in software development to translate assembly language programs into machine language. The term has nothing to do with abstraction levels.
- Perhaps the creator of the diagram actually meant "assembly language" (rather than "assembler"), which could at least make sense in a diagram comparing it with "machine language", and "higher level languages" like compiled or interpreted languages. But terms like "firmware", "applications", "OS", or "kernel" would not make sense to be included in such a diagram on programming languages.
- Alternatively, perhaps the creator meant that the lower-level software between the application and the hardware is often written in assembly language, whereas higher-level components are often written in higher-level languages, but this is not what the diagram shows, and it would be using false terms, anyway. In this case, the creator might have meant a HAL (hardware abstraction layer) or a BIOS (Basic Input/Output System).
- Further, the term "firmware" typically includes all system software in an embedded system, including the operating system, and typically often even including the application (if fixed). It is not something below an operating system, hence the diagram is misleading again.
- A "kernel" is a part of an operating system, so it does not make sense to show it on a different layer than the "operating system".
- And so on... This diagram is totally confused. We can only gain by deleting it.
- --Matthiaspaul (talk) 19:18, 1 January 2017 (UTC)
Kept: per Amitie. Ruthven (msg) 14:21, 6 January 2017 (UTC)
