50 years after BASIC and nothing is written in BASIC.
To replicate its success from the 80s we would need a language that is simple enough for everyone to learn but actually performant and powerful enough to write an entire operating system and application stack in. Then perhaps non-programmers would feel more inclined to look under the hood, see how things work, and change their program's behavior.
The problem though, is that for any reasonably complex system or application, you need to use structured programming. This is what enabled the levels of abstraction that we use to break down programs into layers that can be understood in pieces, and it is what makes large complex software possible without ending up with a mess of spaghetti.
However it is these abstractions that turn a software's code into a Domain Specific Language, and endless APIs that need to be learnt and understood by the programmer.
For programmers it is normal to us that when we want to work on a new codebase we have to learn the idiosyncrasies of the codebase, and learn its DSL and the APIs that it uses, or exposes. But for a non-programmer, this would essentially feel like learning everything about programming from scratch. They would have to become a programmer and develop maintainer skills just to understand what they want to change. (This is why programmer is still a job).
Perhaps the real value of BASIC was that without structured programming, every program was just a pile of spaghetti that even a child could pull apart with a fork.
We then show that receiving the herpes zoster vaccine reduced the probability of a new dementia diagnosis over a follow-up period of seven years by 3.5 percentage points (95% CI: 0.6 – 7.1, p=0.019), corresponding to a 19.9% relative reduction in the occurrence of dementia.
Instead of making a unilateral decision on behalf of all of the members of this community without any kind of consultation, why don't you move to L.W and allow people who do want to be here, who do want to be subject to the moderation rules of this instance, to step in and take the reins?
I say unlock the community and appoint a new mod team. Who said you could just close the whole community, just because you've volunteered to take out the trash?
It sounds like what he was really doing was managing the relationship with upstream, and from the tone that the Arkenfox developer takes, it sounds like it was a relationship that needed managing.
If I'm understanding this correctly, it's the mere existence of reloader.efi and the fact that Microsoft signed it that's the problem.
ESET first discovered CVE-2024-7344 in July 2024. Since then, all vulnerable applications have been fixed, and Microsoft revoked the old, vulnerable binaries in its Jan. 14, 2025, Patch Tuesday update.
So Microsoft are just signing anything even if it breaks UEFI security? And presumably, now that this file is out there, it can be used to subvert SecureBoot on any system that hasn't had its UEFI blacklist updated?
One thing about Cory’s books is that there is always some extremely cringe party section with some rather forced romance part screaming “how do you do fellow kids?” even to me, a middle aged guy himself.
50 years after BASIC and nothing is written in BASIC.
To replicate its success from the 80s we would need a language that is simple enough for everyone to learn but actually performant and powerful enough to write an entire operating system and application stack in. Then perhaps non-programmers would feel more inclined to look under the hood, see how things work, and change their program's behavior.
The problem though, is that for any reasonably complex system or application, you need to use structured programming. This is what enabled the levels of abstraction that we use to break down programs into layers that can be understood in pieces, and it is what makes large complex software possible without ending up with a mess of spaghetti.
However it is these abstractions that turn a software's code into a Domain Specific Language, and endless APIs that need to be learnt and understood by the programmer.
For programmers it is normal to us that when we want to work on a new codebase we have to learn the idiosyncrasies of the codebase, and learn its DSL and the APIs that it uses, or exposes. But for a non-programmer, this would essentially feel like learning everything about programming from scratch. They would have to become a programmer and develop maintainer skills just to understand what they want to change. (This is why programmer is still a job).
Perhaps the real value of BASIC was that without structured programming, every program was just a pile of spaghetti that even a child could pull apart with a fork.