h3lp

Epicycles just had a poor predicting power; they required many more free parameters to describe reality, compared with the heliocentric model.

Knowledge can be framed as information compression (this actually applies to LLMs as well, amusingly). The heliocentric model plus Newton's gravity are an amazing compression of information related to dynamics of celestial bodies, which then enables related predictions that would be much more difficult to arrive at if you start from epicycles.

They quote a roundtrip of 3.6ms, so one-way 1.8ms. In the plots on their page, it looks like the processing latency is centered on around 1ms:

> The LATMON pulse width is therefore an accurate measure of the total processing latency of each cycle and is affected by every element in the data path: processing delay in the microcontroller, network transmission delay, host OS delays, signal processing delay in the DAW, etc

I feel that it's not such a clear distinction between whackamole bug fixing and systematic security engineering. For instance, he uses an example of recurring security vulnerabilities in Chromium: a DCHECK violation again and again and again. However, DCHECK is a Chromium assertion used to defensively check invariants. In other words, it's an example of the invariant-based security engineering, which he contrasts with the whackamole approach. Just to be clear, I think he has a point and I enjoyed reading it---but the problems we're saddled with won't disappear in a flash of enlightenment.

RPi is not less expensive; current Qty 1 lcsc price for rp2354b is $1.62, whereas ch32v303 is $0.88

So it says that not ALL points are on that single line. But it doesn't stipulate that THREE points can't be on the line---the theorem is about proving that you can find one that doesn't have the third point.

In the interconnected, online world, you can do more damage without root access

     "they can read my email, take my money, and impersonate me to my friends, but at least they can't install drivers without my permission"

   https://xkcd.com/1200/

From the wikipedia article:

   Site preparation began in February, 2024;[12] the prefabricated restroom was placed by a crane in March;[2] and installation was completed on April 22, 2024, costing about $200,000 to the city.

so maybe government did the right thing, after trying all the other possibilities.

Thank you, great info. You have great suppliers though: I can get close on batteries (I see four for $355, so $88 instead of your $70) but for panels the best I can get is $220 instead of your $32---how do you go about getting them at those prices? Also, what Ethernet Power Router for $290? Is that a Fiberhood product? How and where would I order it?

I don't doubt that you can have a low marginal cost, but you still have to invest money to get this system installed. You dismissed my argument as 'vague and hand-wavy', so please give a concrete estimate how much it would cost to install a 10kW system on a typical house in the US midwest, and maybe in Europe or Australia.

They say $0.01/kWh is the target price, to be reached after some decades.

Don't get me wrong, I am excited about solar power but careful about the economics: the capital cost of solar right now is well over 1$/W (panels+inverters+installation/hookup) and even though it is falling nicely, the amortization schedule needs to be considered. A rule-of-thumb figure is 1kWh of power per year from 1W nominal installed, so the capital cost will have to be amortized over 100 years to reach $.01/kWh. The installed price has to come down by a factor of 10 for this to work out.

in sqlite you can do it with FILTER:

   $ sqlite :memory: 
   create table t (product,revenue, year);
   insert into t values ('a',10,2020),('b',14,2020),('c',24,2020),('a',20,2021),('b',24,2021),('c',34,2021);
   select product,sum(revenue) filter (where year=2020) as '2020',sum(revenue) filter (where year=2021) as '2021' from t group by product;

Good insight, but if you discount the visual elements (tabs, buttons, etc), you're limiting TUI to CLI, and I think that's unwarranted. The value proposition of both TUI and GUI is two-fold: you see the available action options, and you see the effect of your actions. So, yes, TUI and GUI _are_ closely related: who cares whether we're displaying pixels or character blocks.

Unfortunately, they are often artificially differentiated by the style of the UX interaction: TUIs promote the keyboard actions, and GUIs prefer mouse without corresponding keyboard shortcuts. Unfortunately for GUIs, their designers are often so enamored with WIMP that they omit the keyboard shortcuts or make them awkward. I hate it when, even if the ACTION button is available by keyboard traversal at all, it requires some unknown number of widget traversals instead of being one tab away.

Since the keyboard is almost always used for the textual data, it makes sense to me to always enable it for command execution. Well designed GUIs and TUIs provide both WIMP and keyboard UX, which sadly is not the norm today, so here's my vote to make them larp for each other more.