News for hackers. Stuff that matters.
Re:FaCT: Constant Time Programming Language by hinkley on Sunday October 23, 2022 @03:06PM (#33309328)
Also related to tribal knowledge: One of the sins of technical writing is forgetting to tell people up front why they should care. The assumption that everyone who got here knows exactly why they are here doesn’t scale. You write enough docs and people are gonna click on the wrong one. Nobody wants to read half a page of text and get out a dictionary to find out they’re in the wrong space. You’ve dumped all of short term memory, for one thing.

A constant time programming language sounds like a ridiculous notion to most problem domains. It is a ridiculous notion. You only want code that always runs in exactly half a millisecond when you’re solving a very, very specific set of problems, like protecting secrets or opening airbags, and then it’s one of the most important things.

Re:FaCT: Constant Time Programming Language by chowells on Sunday October 23, 2022 @03:21PM (#33309454)
You don't even need constant time for opening airbags. Real time (upper bound, but no lower bound) will do the job. Pretty much it's just working with secrets that cares about constant time.
Re:FaCT: Constant Time Programming Language by emmelaich on Sunday October 23, 2022 @04:38PM (#33310049)
> One of the sins of technical writing is forgetting to tell people up front why they should care.

Hence our confusion of you mentioning Shamir. I went back to the site thinking he may have been a contributor.