and it's remarkable how """low-level""" programmers think because you're responding to hardware error states that means your software MUST be the MOST half-assed unstructured bullshit at all times
0 Boosts
0 Likes
the very first time i've ever once considered whether a backslash escape was adding too much complexity into a language was a badinage with @ska and @navi about parsing kernel command lines after i mentioned having to work around both the linux kernel and the node.js Console object to produce a backwards-compatible fix for coffeescript v2 shebang lines https://coffeescript.org/#breaking-changes-argument-parsing-and-shebang-lines and after an initial arrogance https://circumstances.run/@hipsterelectron/114994260313214101 recognized i was getting schooled by the aang and katara of shell command-line parsing and started taking notes
https://circumstances.run/@hipsterelectron/116209213401859882 i stand by this phrasing quietly iconoclastic -- describing how simple and significant it was to my entire mode of thinking around this problem space when @ska proposed to me for the first time that a backslash isn't just a tool it's necessarily a whole self-interacting dynamical system
wikipedia tries very hard to center the worship of icons https://en.wikipedia.org/wiki/Iconolatry and to pathologize responsess to it as a form of intolerance
conolatry was mainly manifested in popular worship, as freedom of worship while others viewed it as superstitious belief in the divine nature of icons or deities
that's an absolutely classic anti-intellectual line of argument and it's a favorite tactic of the tyrant microsoft e.g. in response to any reference to copyleft license protocols
Both extreme positions, iconolatry and iconoclasm, were rejected in 787 by the Second Council of Nicaea,
by this we can infer that modern-day liberal centrism is at least a thousand-year-old invention, although i believe tall tales about the followers of pythogoreas and their supposedly violent[citation needed] reaction to the concept of irrational numbers have sought to push it back another millennium into the historical record
@hipsterelectron this is an insanely based take by the way. this is the same reason why I am on a mission to kill the toolchain.
everyone is bamboozled by images! I know this because they genuinely see the toolchain stages as fixed objects, an actual firmament. they can't imagine any other configuration of flows or order of operations.
"you're actually the idiot for thinking that the dogma of the dragon book isn't the best possible way"
sure, I wrote 2 entire proprietary compilers and a bytecode interpreter for proprietary chips, one of which was designed by me, and I don't know anything. ok sure thing
"irrationals" do not even exist as a distinct concept without the thoroughly unnatural and much later imposition of "cartesian" "coordinate" "systems" as an approximation of topological and geometric measure theory, imho
this a fucking abombination imho
A Device Path is terminated by an End of Hardware Device Path node. This type of node has two sub-types ( Device Path End Structure):
End This Instance of a Device Path (sub-type 0x01). This type of node terminates one Device Path instance and denotes the start of another. This is only required when an environment variable represents multiple devices. An example of this would be the ConsoleOut environment variable that consists of both a VGA console and serial output console. This variable would describe a console output stream that is sent to both VGA and serial concurrently and thus has a Device Path that contains two complete Device Paths.
End Entire Device Path (sub-type 0xFF). This type of node terminates an entire Device Path. Software searches for this sub-type to find the end of a Device Path. All Device Paths must end with this sub-type.
bolded emphasis mine because this takes a description of a tree, one of the most well-characterized graph classes in human history, and makes it sound like a dark souls boss. it's really impressive stuff
and it still fails to describe the mechanisms or constraints or use cases of this hypothetical time-varying data flow process they just proposed. the structure they handwave over a pipelining output process seems only to inhibit system flexibility, not to capture its semantics at all (except perhaps inasmuch as it represents, in the form of code, which corporations have decided to do business with each other through the unregulated marketplace of software interfaces
first result on their fucking website when you try to find an actual goddamn specification https://uefi.org/sites/default/files/resources/UEFI_PQC_Update_Whitepaper_Final.pdf
UEFI Post-Quantum Cryptography: UEFI Specification Updates
if your fucking hardware specification is so brittle it has to know and care about the internecine political horse races between different groups of academic cryptographers who have made never ever solving the problem of their field into a performance art form, it's over. you're not doing a hardware specification at that point you're just selling cloud services for the BIOS
The advent of quantum computing poses a significant threat to the cryptographic algorithms
that underpin the security of modern computing platforms.
directly and provably false
Algorithm such as RSA2048, which is
widely used in UEFI Secure Boot and authenticated variable, is vulnerable to quantum attacks.
it's also vulnerable to rubber hose cryptanalysis (the modern iteration of this involves freezing RAM sticks). the security of any cryptosystem lies in the state-changing semantics it exposes to external and internal actors to control its behavior. the only perfectly secure system is one which contains no data and represents nothing of significance to any individual or group. /dev/null continues its reign over the title of Most Secure
of course it's microsoft
Over the last year, the UEFI Secure Sub Team (USST), a sub-team of the UEFI Specification
Working Group (USWG),
yeah
has met to define a path forward for several current and emerging
challenges:
and it's literally all just mathwashed jargon for monopolistic coercion processes to force users to "refresh" their perfectly working hardware due to a constructed maze of DRM schemes
- Adoption of post-quantum cryptography (PQC) for UEFI features and platforms
computers of course always have to be swapped out completely whenever you want to start doing different types of math with them
- Impacts of the 2011 UEFI Secure Boot key expiration on in-market PCs
literally just DRM to juice stock market timetables
- Review of the UEFI security features and common implementation/usage patterns, andthe depreciation of unused and unnecessary complexity
declaring any actual engineering and design colloration processes that unfuck the fucked system to be not only INCOMPATIBLE with the new spec, but in fact representative of an ILLEGAL state. just like TLS 1.3
https://www.cloudflare.com/learning/ssl/why-use-tls-1.3/#what-is-a-vulnerability
What is a vulnerability?
cloudflare teaches kindergarten students about 9/11
Cloudflare prioritizes supporting all the latest, most secure versions of networking protocols. Cloudflare immediately offered support for TLS 1.3; in fact, Cloudflare supported TLS 1.3 back in 2016, before the IETF finished fine-tuning it.
"all the latest, most secure versions" would make another great t-shirt to wear to a conference
@hipsterelectron
(The Graduate voice) I just wanna say one word to you son... FORTH