soedirgo

This is the one that I remember watching https://www.youtube.com/watch?v=826HMLoiE_o. Not exactly 24 hours though.

Haven't read the book, but I liked his lecture series on human behavioral biology: https://youtube.com/playlist?list=PL848F2368C90DDC3D

You jest, but... https://www.rangevoting.org/FeynTexts.html

TL;DR: read the end of the first paragraph.

The other person I have similar feelings for is Geohot.

I don't know about that... https://news.ycombinator.com/item?id=25679907

Not wasmtime, but I'm reminded of wasm-pack [0], though it's not project ownership but crate ownership, and not really a big kerfuffle.

[0] https://github.com/rustwasm/wasm-pack/issues/928

One day, game developers will package static binaries

Wouldn't you still need at least runtime linking (dlopen) to link to OpenGL/Vulkan/etc.?

While I agree with the sentiment, my impression is that the GP's point is about memory safety rather than performance. So yes, this applies for common patterns like per-frame memory in games, in which case the "it" is the arena. Otherwise, as a general rule, profile first, then optimize.

Probably for your PR from way back when: https://news.ycombinator.com/item?id=19359870

The latest edition (7th ed, 2015) actually uses 4.5 as well. AFAIK OpenGL hasn't changed too much since 3.3, certainly not to the point of being irrelevant for learning.

Can you give a source for this? Also, is it still stuck at 4.1/1.2?

Hard to talk about code comments without mentioning 'antirez's article [0] about this where he goes in depth on the different kinds of comments he used throughout Redis.

[0] http://antirez.com/news/124

Are you referring to snapshot testing[0][1]? i.e. you first "snapshot" the output of the function and commit it to VC, and each test run will run the same input and compare it against the "snapshot", failing and giving a diff if it differs.

I'm about to try it soon, seems like a good ROI as you said.

[0] https://jestjs.io/docs/en/22.x/snapshot-testing [1] https://github.com/mitsuhiko/insta

Since we're in pedanticville, these aren't converses, but inverses. The converse goes "If you don't outsource X, then X is your core business".

Hey folks, this is my internship project at Supabase, which you may have heard from its HN thread that got popular recently. We lean heavily on PostgREST, which is a Haskell tool (a wildly successful one!) that turns a Postgres database into a RESTful API.

We use PostgREST through our own client library as it's much easier to use. But it's in JavaScript, and I'm part of the Rust Evangelism Strikeforce myself, and the rest is history. ;)

There's also one for JavaScript: https://github.com/supabase/postgrest-js

It's the transpose operation [1]. See property 3.

[1] https://en.wikipedia.org/wiki/Transpose

Yarn 2 uses Prolog for workspace constraints.

https://dev.to/arcanis/introducing-yarn-2-4eh1#workspace-con...

I don't know how many people FB actually allocates for their main app, but this reminds me of a chapter in The Mythical Man-Month. It is said over 1000 people and 5000 man-years went into OS/360. I don't see it anywhere today.

Instead, the book proposes The Surgical Team, i.e. about 10 people taking specialized roles, with the system being the product of the mind of a few key people. I wonder how well this aged.

Ah! I stand corrected. Mea culpa.

In Go, there's a standard project layout [1]. It'd be nice to have a project layout linter in Go Report Card [2].

[1] https://github.com/golang-standards/project-layout

[2] https://goreportcard.com

  ;;; -*- lexical-binding: t -*-

It's the ultimate yak shaver ;-)

Or you could start with a popular .emacs.d (I use Doom Emacs), tweak a few things, and tell yourself "I don't need to modify yet another key binding" a hundred times.

I found this [1] series of posts to be incredible for implementing Zettelkasten using org-mode in Emacs.

I don't use Zettelkasten myself, but maybe I'll have the time to get around to it...

[1] https://blog.jethro.dev/posts/org_mode_workflow_preview/

This might be related.

From pg: "...you could get smarter programmers to work on a Python project than you could to work on a Java project." [1]

[1] http://www.paulgraham.com/pypar.html