@observer@SuperDicq Barcelona y Madrid están llenas de caribeños y moros. Cada vez se ven menos españoles en las iglesias (los católicos practicantes representan alrededor del 20% de la población) y, desde luego, no son lugares tan seguros en comparación con Japón.
>Aldo >Valores cristianos >Otra gente *blanca* protegerá a mi hija inexistente Lol, lmao incluso.
@freebeer@Suiseiseki They are not, but commercial glasses cleaners are often proprietary. Visual diseases, such as myopia, are indeed restrictions imposed by proprietary nature — they limit your vision and force you to rely on external free aids like glasses. Myopia often develops due to insufficient exposure to proprietary sunlight. Furthermore, excessive exposure to free computer screens (i.e., free electric light) worsens the condition.
@mjg59@Suiseiseki Although it's true that modern microcode is written in a language the CPU can interpret and that it can be updated or loaded from flash memory, this does not mean that all microcode is software.
The base microcode stored in MROM is physically implemented in silicon and serves as the hardwired circuitry that defines the CPU's core logic and fundamental behavior. It is not interpreted or executed like a program; it is hardwired to control the CPU's internal signals and state transitions.
Microcode fragments loaded from flash memory at boot time (updates or patches) are software: they consist of instructions that the CPU interprets to dynamically alter its behavior. However, the foundational layer —the original hardwired microcode— remains intact and is not executed in that way. These updates are not executed directly from flash; they are copied into the CPU internal volatile memory during the boot process, where they temporarily override specific behaviors, while the physical MROM remains unchanged.
@mjg59@Suiseiseki >the base microcode loaded from ROM is what validates the signature on any ACMs that are loaded from flash. Base microcode is not loaded, executed or modifiable. It is physically embedded in the CPU silicon as hardwired logic, commonly implemented as a hardwired finite-state machine. It functions as a control circuit that responds to input signals with predetermined outputs, without the need for interpretation or instruction execution. Among its functions is the validation of ACMs using integrated cryptographic modules.
>It is not simply an instruction lookup table, it is software. Not being simply an instruction lookup table does not make the base microcode software; it indicates that it is complex circuitry.
@mjg59@Suiseiseki It is not false to say that the base microcode functions like a hardwired FSM, because it is a good analogy for its fixed and deterministic operation. It is true that the implementation has become more complex and is no longer so simple.
@mjg59@Suiseiseki I'm not sure exactly what you mean. A ROM can be electrically programmable and erasable (EEPROM). A CD can be a CD-RW, CD-R, CD-ROM or CD-A — all of them are different.
@mjg59@Suiseiseki The term "software" comes from "soft", implying something flexible or modifiable without physically altering the medium in which it resides. In contrast, "hardware" comes from "hard", referring to something rigid or fixed, which requires physical intervention to change.
A CD-ROM can store a computer program, but it does so in a fixed, physical, and immutable form. Because this data cannot be modified without physically altering the disc, it does not align with the notion of software as something "soft" or easily changeable. In such cases, we are dealing with a tangible, unalterable representation — in other words: hardware.
This analysis is logically consistent and valid within the conceptual framework based on etymology.
@mjg59@Suiseiseki >your understanding of modern microcode is simply incorrect You can't just say it's simply incorrect. You need to correct my supposed misunderstanding.
>and whether something is software or not is not determined by the tangible form it is fixed in I did not claim that. In fact, I made it quite clear: for those instructions to be software, they must be in a format that a computer can interpret or execute.
@mjg59@Suiseiseki Microcode updates loaded into volatile memory at boot are indeed software (usually proprietary and potentially malicious) — snippets of code that the CPU can interpret to modify or patch its behavior. However, this does not turn the base microcode into software nor change the physical MROM. It just adds a software layer on top of the hardware.
@mjg59@Suiseiseki What has changed is the addition of an update layer loaded into volatile memory at boot, which can patch, modify or add behaviors. Using microcode updates for mitigations like Spectre does not mean the base microcode ceases to be hardwired, nor that the physical MROM is altered. These updates act on internal volatile memory that dynamically overrides behavior, while the MROM remains intact. Thus, modern CPU microcode operates on two levels: a hardwired base layer and a software layer that adds flexibility without changing the underlying hardware.
It is also important to note that vulnerabilities such as Spectre are not "mitigated" exclusively through proprietary microcode updates. Many effective mitigations are implemented at the operating system level —especially in the kernel— such as retpolines, kernel page table isolation, speculative execution barriers, et cetera.
"The ethical issues of free software arise because users obtain programs and install them in computers; they don't really apply to hidden embedded computers, or the BIOS burned in a ROM, or the microcode inside a processor chip, or the firmware that is wired into a processor in an I/O device. In aspects that relate to their design, those things are software; but as regards copying and modification, they may as well be hardware" https://www.fsf.org/campaigns/free-bios.html
A ROM can contain software, such as in the case of an EEPROM, which can be electronically reprogrammed. However, the microcode embedded in a CPU’s MROM is not software — it is physically etched into the silicon as part of the chip’s design and cannot be modified without completely redesigning and remanufacturing the chip.
An MROM is a section of the circuit where the manufacturer permanently fixes a binary sequence during fabrication by connecting or leaving disconnected specific silicon pathways — similar to fuses, but at the level of lithographic mask design. That is to say, the microcode is not executable software but hardwired logic: a behavior physically implemented in the chip’s design through fixed connections in the silicon. The CPU does not execute it as a program but operates according to a finite state machine implemented directly in hardware, which determines step-by-step how to internally execute certain complex instructions.
Microcode updates loaded at boot time do not modify the physical MROM or the hardwired microcode — instead, they overwrite a small internal volatile memory or cache that temporarily alters the CPU's behavior. Such software is often proprietary and potentially malicious.
@mjg59@Suiseiseki The FSF does not claim that these elements are software, but rather that, although they can be considered software from a design perspective, in practice they are hardware.
Writing instructions on a sheet of paper does not constitute software by itself, but rather a tangible representation of software (like printed source code). That sheet is merely a physical medium. For those instructions to be software, they must be in a format that a computer can interpret or execute.
The base microcode etched into a CPU's silicon is not a program that the processor executes or interprets. Instead, it functions as a finite state machine implemented in hardware — a fixed set of rules and physical connections (states and transitions) that guide the CPU’s internal behavior to execute complex instructions.
@SuperDicq@koakuma@kaia Yeah... that also happens in the Third World, except for the part about coins (at least in my country). I never thought that the Netherlands would be such a proprietary country, especially regarding transport.
@SuperDicq@koakuma@kaia >They have these Suica cards for public transport there. They are completely anonymous because you can buy and recharge the cards using cash from a vending machine.
>But these cards are not used only for public transport. Many stores accept them too, and so do vending machines, arcade machines, etc.
Isn't that how those cards work all over the world? The only drawback of not registering your card here is that your transport ticket costs more, but hot chocolate doesn't.