monocasa

35 ms·

571.
by monocasa 1y ago
Yes, you can.
572.
by monocasa 1y ago
And don't get me started with Wyatt's Towing and the Public Utility Commission (which the CEO of Wyatt's was on the board of).
573.
by monocasa 1y ago
> This is the same logic by which communists called socialists who believed in democracy "fascists". It's just an attempt to excommunicate people from the church if their interpretation is different from yours. I mean, Chi
574.
by monocasa 1y ago
And in fact, when you look at formally proven code, 80% of the shtick is reducing complexity of mutation to something tractable. That's valuable whether or not you then actually go through the process of formally proving it.
575.
by monocasa 1y ago
I love that this site has an Easter egg if left idle long enough.
576.
by monocasa 1y ago
I think it's a anti flamewar tactic to put the brakes on quick replies.
577.
by monocasa 1y ago
A US administration does not cost tens of billions. He paid $250M to the trump campaign making him the single largest donor of all time, and that's what let him buy the current admin. And that was close to 1% of what he paid for twit
578.
by monocasa 1y ago
That was what stuck, but supporting the big servers was also part of their multifaceted strategy. That's why the alpha, itanium, powerpc, and mips ports existed.
579.
by monocasa 1y ago
Microsoft was absolutely wanting to target large servers at the time. They were actively trying to kill off the vendor unices in the 90s.
580.
by monocasa 1y ago
Tom's hardware is mistaken in their reporting. That's raisng the limit without using CPUMASK_OFFSTACK. The kernel already supported thousands of cores with CPUMASK_OFFSTACK and has at least since the 2.6.x days.
581.
by monocasa 1y ago
It absolutely will. Your process is only assigned a single processor group at process creation time. The only difference now is that it's by default assigned a random processor group rather than inheriting the parent's. For pro
582.
by monocasa 1y ago
I mean, it seems it's quite clear that a single process and all of its threads will just be assigned to a single processor group, and it'll take manual work for that process to use more than 64 cores. The difference is just that p
583.
by monocasa 1y ago
Windows didn't handle numa either until they created processor groups, and there's all sorts reasons why you'd want to run a process (particularly on Windows which encourages single process high thread count software archs) t
584.
by monocasa 1y ago
They were absolutely interested in the server market as well.
585.
by monocasa 1y ago
There were single image systems with hundreds of cores in the late 90s and thousands of cores in the early 2000s. I absolutely stand by the fact that Intel and AMD didn't pursue high core count systems until that point because they wer
586.
by monocasa 1y ago
> Windows didn’t run on these other systems, why would Microsoft care about them? Because it was clear that high core count, single system image platforms were a viable server architecture, and NT was vying for the entire server space, i
587.
by monocasa 1y ago
I mean, x86 didn't, but other systems had been exceeding 64 cores since the late 90s. And x86 arguably didn't ship >64 hardware thread systems until then because NT didn't support it.
588.
by monocasa 1y ago
> a number of teams did that from mips->arm and had success with the result. Do you have any examples? Apple Silicon cores took pieces of the pwerficient cores, and everything else I know of either tweaked an official ARM design or s
589.
by monocasa 1y ago
No datasheet, but their commits to opensbi have been extremely enlightening wrt s and m modes.
590.
by monocasa 1y ago
A lot of synchronization primitives in the NT kernel are based on a register width bit mask of a CPU set, so each collection of 64 hardware threads on 64 bit systems kind of runs in its own instance of the scheduler. It's also unfortu
591.
by monocasa 1y ago
Adding to what was said, it also suspiciously looks like a MIPS core with a RISC-V frontend strapped to it sort of like Qualcomm did with their Nuvia AArch64 core. Particularly stuff like the soft fill TLB from m-mode looks just like MIPS
592.
by monocasa 1y ago
The middle class is on the chopping block too. The lower class will honestly probably last longer than the median of the middle class, like paralegals, etc. Standing in the same bread line creates an awful lot of solidarity.
593.
by monocasa 1y ago
I don't think the parent is making the argument that this level of automation can't be a net benefit for humanity, just that if it results in nearly the entire middle class and down being laid off at the same time with no recompen
594.
by monocasa 1y ago
> But it was better at the basics than anything else in Rust, so it caught on for routine non-game programs. And here we are. Seriously. The main tale I think is how awful Rust's story on GUIs are such that most Rust users prefer a
595.
by monocasa 1y ago
Unfortunately stuff like SAML is XML. That being said, I don't think that libxml2 has support for the dark fever dream that is XMLDSig, which SAML depends on.
596.
by monocasa 1y ago
I'm reminded of Ken Sheriff's reverse engineering of the original FPGA, the Xilinx XC2064. https://www.righto.com/2020/09/reverse-engineering-first-fpg...
597.
by monocasa 1y ago
What's the story with the rest of the contract? You don't normally get a vehicle manufacturer to start up a custom line without some contract in place wrt minimum orders (or paying out the wazoo).
598.
by monocasa 1y ago
Amazon already has custom Rivian vans that were designed for them.
599.
by monocasa 1y ago
The actual cost of the part (within reason) doesn't matter all that much for a hyperscaler. The real cost is in the perf/watt, which an FPGA is around an order of magnitude worse for the same RTL.
600.
by monocasa 1y ago
Eh, it's just a half dozen signals in each direction running at 125Mhz DDR. That's in spitting distance of being able to be bit banged by something like an rpi pico.

More ›