6,620 karma · joined March 5, 2012
Twitter: @runeksvendsen
GitHub: https://github.com/runeksvendsen
apply foo bar (lol wat)
in Haskell, and it confuses you, simply mentally replace it with apply(foo, bar, lol(wat))
To translate into a more popular syntax (e.g. JavaScript).Yes, that definitely the case.
If you know what each function above does, including the function composition dot (.), then this is like reading English — assuming you know how to read English.
One could have the backend fetch DB schema/version info at startup, compare it to its own view of what the schema should look like, and fail if the two disagree. That way, a new deployment would fail before being activated, instead of being deployed successfully and queries failing down the line.
As an extra feature, firmware could hook up to the software that uses the webcam to send a "hang up" signal when I turn off the webcam. That way I don't have to find some button in whatever software the person I'm having a call with wants to use — I just "turn off" my webcam.
Doing Apple's work for free.
If getting people to pay for stuff they use were trivial then advertising wouldn't be as big as it is.
Anyone know what these are?
This too harsh. There's nothing unethical about delivering what your manager tells you instead of what you believe the customers need. Going rogue — as opposed to doing what you're told — is not necessarily the ethical choice.
You mention input lag only once where you say:
> Although this post is mostly focused on productivity, most if not all 8K TVs can be run in 4K at 120 Hz. Modern TVs have decent input lag in the ballpark of 10 ms and may support FreeSync.
Have you measure this, or where do you get this number from?
The TV I bought was also advertised as low-latency, but I found it too high in practice (when typing in code, or scrolling, and waiting for the screen to update).
A formal proof is simply a type that allows only the correct implementation at the term level. And specifying this takes ages, as in hundreds of times longer than just writing it out. So you want to use an LLM to save this 1% of time after you've done all the hard work of specifying what the only correct implementation is?
> I think row polymorphism is a fairly straightforward thing compared to dependent types in general, but can let you crush a whole class of errors [...]
Would you care to provide a few examples? I don't have experience with row polymorphism so I'm genuinely curious.
It doesn't need to be black or white.
A country can have decent consumer protections without e.g. a tax policy that is hostile to startups. But many EU countries are seemingly uninterested in the latter — presumably because there are no votes in it.
And, in any case, explaining what HTML stands for does not get anyone closer to understanding what it is.
I think it's a feature that this book doesn't throw technical jargon at the reader before they've even created anything useful yet.
You’re conveniently forgetting all the things that followed the same trajectory as LLMs and then died out.
EDIT: Found this: https://github.com/HigherOrderCO/HVM1/blob/master/guide/HOW....