jbrot

At first glance, this looks pretty similar to the Bob Lee murder last year. I find it interesting and a little surprising how different the reaction and coverage has been

The article claims that the daylight savings transition happens at 11pm in pacific time. However, my understanding is that this transition should happen at 2 am for all us time zones. Where is 11pm coming from?

One of the coolest things about this demo is that the token generation runs on a single node using just 8 RDUs (SambaNova’s chip).

Disclosure: I work at SambaNova and was part of the team that made this

My main takeaway is that you can easily 3D print a small device that converts a semiautomatic gun into a fully automatic gun, and apparently having one of these devices (a “switch”) has become a status symbol

The section on marijuana is particularly interesting. You are apparently allowed to deduct ordinary business expenses, even if the business in question is illegal. However, Congress has explicitly disallowed these deductions in the case of illegal drug trafficking. Since marijuana is illegal federally, the courts have ruled that medical and recreational marijuana businesses that are legal under state law may not deduct any of their ordinary business expenses from their federal taxes.

Another excellent article from Amos digging into the minutiae of how executables work!

From the title I was expecting something about Op Sec, but the article is actually about “show, don’t tell” i.e. that it’s really hard to have people “get it” without letting them experience “it” for themselves

From the underlying paper[1], I found this excerpt:

“The photocurrent or the short-circuit current density (JSC) extracted from BTO is around 0.415 μA/cm2. … The JSC value from SBC555 is around 11.03 μA/cm2 and is about 25 times higher than measured in BTO. The open-circuit voltage (VOC) in the case of BTO was found to be around −0.007 V, as opposed to −0.058 V in SBC555.”

Here, BTO is the existing material and SBC555 is the new material from the paper. Multiplying JSC by VOC to get power density , we see that BTO yields 2.9 nW/cm^2, while SBC555 yields 639.74 nW/cm^2.

For reference, according to [2], we have that “typical external parameters of a crystalline silicon solar cell as shown are; Jsc ≈ 35 mA/cm2, Voc up to 0.65 V.” Notice the unit difference of mA/cm^2 here vs uA/cm^2 above. Multiplying these parameters yields 22,750,000 nW/cm^2. So we see that these cells are still approximately 100,000x worse at producing power than the current crystalline silicon cells.

[1] https://advances.sciencemag.org/content/7/23/eabe4206

[2] https://ocw.tudelft.nl/wp-content/uploads/solar_energy_secti...

If you haven't read it yet, Neal Stephenson's Snow Crash is an excellent novel that explores something along those lines

Very surprising to see this headline (although I doubt it will come to pass). Given recent movements towards ending the war on drugs (e.g., legalizing Marijuana), it seems rather hypocritical to then try and ban cigarettes. Admittedly this is in the UK, and I’m not super familiar with their politics.

Perhaps I missed this discussion in the article, but what are the theoretical advantages of these organic transistors over the traditional CMOS transistors motivating this research?

My understanding is that underground is a constant 50-60°F — wouldn’t that provide a heat difference?

It means using `git merge --squash` which performs a normal merge but then instead of adding a merge commit, it just makes a single regular commit with the changes.

> Programmer discipline doesn’t scale

Thank you for putting this so eloquently. This has basically been the sole tenet of my programming philosophy for several years, but I’ve never been able to put it into words before.

Glad to hear there’s a solution for this! Thanks for responding :)

Very neat project! One question about content addressed programs: how does this play out with types that are structurally equivalent but semantically distinct?

For instance, assuming C definitions, an integer and a file descriptor have the same content but probably should not be treated as the same type (I wouldn’t want arithmetic to type check against file descriptors…).

Another scenario: say I have a type “Foo” which contains an integer. In version 1 of my library, this integer must be even, but in version 2 I add support for odd integers, too. The Foo data type, from a content perspective, is unchanged. However, the invariants around it have changed and it’s therefore essential that it becomes a new type. Otherwise, someone might create a Foo containing an odd integer using the version 2 API and then pass it to a function from the version 1 API, resulting in bad things since the version 1 API believes Foo can never contain an odd integer.

We have a suite of about two thousand integration tests and we run each test in its own docker container for isolation purposes. Multiply by 500 jobs a day and you get to a million containers.

I know the CICD code I wrote and manage at work launches approximately a million docker containers a day, so I suspect the total number of docker containers used per day is well into the billions.

I encountered the project in this article about separation logic [1]. I figured the above project would be more relevant to the HN community, though.

[1] https://dl.acm.org/doi/pdf/10.1145/3211968

Small correction: the definition you shared is that of “uniform continuity” [1] not “absolute continuity” [2]. Absolute continuity is a slightly stronger condition where instead of providing a single (x1, x2) pair with |x1 - x2| < delta, you can now provide a finite list of pairs.

[1] https://en.m.wikipedia.org/wiki/Uniform_continuity [2] https://en.m.wikipedia.org/wiki/Absolute_continuity