> The scary thing is that Indian juduciary is infamous for being incapable of tolerating any kind of criticism against it and not hesitating to put people in jail for "contempt" for just calling out corruption.
From [0]:
"India's Supreme Court has banned a school textbook after a chapter in it made a reference to corruption in the judiciary.
The revised social science book was published by the National Council of Educational Research and Training (NCERT), which designs the syllabus and textbooks for millions of schoolchildren in the country.
On Wednesday, after Chief Justice Surya Kant criticised the book, saying it could damage the reputation of the judiciary, NCERT apologised and withdrew it from distribution.
Now the court has ordered a complete halt on the book's publication, saying its contents were "extremely contemptuous" and "reckless".
"A complete blanket ban is hereby imposed on any further publication, reprinting or digital dissemination of the book," the court said on Thursday, according to legal news website LiveLaw.
The judges also issued notices to the top bureaucrat in the school education department and the NCERT director, asking them to explain why they should not be held in contempt of court for including the "offending chapter".
> On the other hand, what Windows didn't yet support in this era was DirectDraw — i.e. the ability of an app to reserve a part of the screen buffer to draw on itself (or to "run fullscreen" where Windows itself releases its screen-buffer entirely.) Windows apps were windowed apps; and the only way to draw into those windows was to tell Windows GDI to draw for you.
> This gave developers of this era three options, if they wanted to create a graphical app or game that did something "fancy":
> 1. Make it a DOS app.
This vaguely reminds me of WinG[0][1] - the precursor to DirectDraw. It existed only briefly ~ 1994-95.
My vague "understanding" of it was to make DOS games easier to port to Windows. They'd do "quick game graphics stuff" on Device Independent Bitmaps, and WinG would take care of the hardware details.
It looks like the FPGA that monitors/controls the redundant/lockstep CPUs might be radiation tolerant. From [0]:
"..the critical FPGA which is always on for the duration of the mission, the radiation tolerant ProASIC3 is chosen with the military temperature grade (-55 C to 125 C) and -1 speed grade to mitigate the degradation in the propagation delay caused by the total dose radiation. The single-event upset (SEU) is mitigated with triple module redundancy (TMR) in the FPGA design.
...
The FPGA device is a military-grade version of MicroSemi’s ProASIC3L, which uses the same silicon as the radiation-tolerant device from the same family."[0]
The specs from [1] say there is also a specific radiation-tolerant variant.
So it looks like the CPUs themselves have dual lock-stepped cores, and the CPU checks for errors each cycle. If there's an error it flags the FPGA, which switches to the other CPU.
Only the microcontrollers are automotive redundant CPUs from Texas Instruments.
The high-level control and data processing is done by a now very old smartphone Snapdragon 801 CPU, which has no redundancy and it runs Linux. That CPU uses 4 custom 32-bit Qualcomm Krait cores, which were extremely fast in comparison with the radiation-hardened CPUs available at that time, but which are very slow in comparison with the current automotive CPUs or smartphone CPUs.
Nowadays there are automotive redundant CPUs, using high-performance automotive-enhanced ARM cores like Cortex-A78AE or Neoverse V3AE, which are far more suitable for a space mission than a smartphone CPU.
Because Snapdragon does not have the right hardware, approximate redundancy is achieved by software, i.e. by running multiple times each algorithm and comparing the results, and also by periodic self tests.
This is better than nothing, but a hardware-redundant CPU would have provided much better performance.
See also perhaps Jesus and John Wayne: How White Evangelicals Corrupted a Faith and Fractured a Nation by Kristin Kobes Du Mez:
> The book examines white evangelical affinity for Donald Trump. Du Mez explains that white evangelical support for Donald Trump during the 2016 United States presidential election was a continuing trend rather than an exception. The book focuses on the militant masculinity that white evangelicals idealize and how it has manifested in a pattern of abuse among evangelical leaders. Du Mez criticizes mainstream evangelicals such as John Eldredge, John Piper, and James Dobson for advancing the evangelical ideal of militant masculinity.[4]
Head of FCC threatens broadcaster licenses over critical coverage of Iran war
(twitter.com/brendancarrfcc)
208 points by theahura 10 hours ago | unvote | flag | hide | past | favorite | 100 comments
https://xcancel.com/BrendanCarrFCC/status/203285541423304717...
https://news.ycombinator.com/item?id=47380294
reply