Quite , was just reading also yeah I’m right there with you. The point we are both probably missing is that John Young is old and for that reason if it’s not brilliant because it forces the government to take a very tyrannical position against a person who is literally probably on their way out, or very sad because the poor guy has lost his mind.
It’s possible he knows something about the audience of the content on his site, interesting to think that certain parts of our own government rely on its insights that they can’t otherwise get but can benefit from nonetheless.. really wouldn’t surprise me.
I don’t know if anyone has bothered to point this out but you could keep your schemey SICP and go clojurescript if you wanna run on JavaScript but then again you still have to contend with cycles and reverse polish
Ugh, you know it really wouldn’t be so bad if they would just go back to selling cpus like they're meant to be kept around for more than a year. The thing that has me really ticked off at Intel right now is the i915 sriov capabilities introduced in 11th gen which were meant to supersede GVT-G. I didn’t even know GVT-G was a thing until it was already gone. They didn’t even make a driver that supports 11th gen and 12th is apparently supported in some capacity but I’m not understanding it very well myself. I damn sure wouldn’t buy a 12th gen though if its a thing you think you might actually care about. If 11th gen is any example of how 12th will turn out, any development will be left up to one person who miraculously understands i915 well enough to develop for it, doing for free and doing a good job but not well enough to keep up with linus/linux~HEAD; needless to say if 11th gen support for i915 sriov does ever get merged the cheap low quality construction of the hardware will probably be starting to break down, seems like most of it is by the time you unbox it anyway these days :(
First thing I wanted to know was whether or not it had made use of the 4 bit slice ALU (which imho would have been ok) but unsurprisingly this is one of “those” projects..
But yeah the alto became my new favorite even though it’s way before my time when I saw the cpu card for it, and I really see no reason to take exception to the 74181 other than it’s too complex— the whole ti 74xx series is complex in retrospective. Unless this is somebody with the means to substantiate lithography for many of the TI chips but not the 4bit slice alu, then I’m not really sure what their hang up is with it.
I heard about some recent eBPF vulnerabilities and while I was looking at the kernel code for eBPF I noticed there was some relatively new IMA additions. It seems there’s quite a number of new security mechanisms that can be used with eBPF. Mostly the fact that they added IMA support just stood out to me and seems to say “you should definitely use it if you’re going to use eBPF.”
It is interesting to hear about the problems that eBPF has but it would be helpful to see more people talking about ways that you can minimize the problems or reasons why you can’t
I’ve used it for about 10 years without consequence; except for problems I had once with enabling experimental options in the kernel module (custom build.) I have used BTRFS exclusively and extensively in terms of what you can do with it since realizing it that many years ago. The only thing I haven’t used is its native RAID support. I think 0 and 1 are fine but I’m not sure about 5/6; parity was still experimental last I checked in 2016 maybe it’s reliable now. Everything else though; compression, snapshots, copy on write, online defrag has all been fine. It is the default for SuSE Leap and Tumbleweed, they use it for snapper (OS snapshots) and BTRFS sub volumes are also supported by Docker for container images and containers. It saves a lot of space when images start to add up.
It’s possible he knows something about the audience of the content on his site, interesting to think that certain parts of our own government rely on its insights that they can’t otherwise get but can benefit from nonetheless.. really wouldn’t surprise me.