forrestthewoods

6 ms·

31.
by forrestthewoods 3mo ago
This is all true. But it’s still a counter-example to “once cameras go up all trust is lost”. Clearly cameras are not the sole issue that makes trust achievable. As demonstrated by high-trust societies with cameras!
32.
by forrestthewoods 3mo ago
It’s interesting that Bun was a human rewrite from Go to Zig. (I think?). Then rewritten from Zig to Rust. AI is pretty good at rewrites and ports. Quite good infact.
33.
by forrestthewoods 3mo ago
> However, I continue to be amazed that Perforce survived Git. Virtually 100% of non-indie devs use Perforce. Is Perforce good? Ehhh not really. It’s been stagnant for 15 years. Is Git capable of meeting game dev needs? It’s not enough c
34.
by forrestthewoods 3mo ago
Nice post. Thanks for sharing.
35.
by forrestthewoods 3mo ago
Ehh. Cargo has build.rs but calling that a polyglot build system is like calling bash scripts a polyglot build system. Buck and Bazel have the right architecture. Just need a version written fresh without all the baggage.
36.
by forrestthewoods 3mo ago
> the problem is that you need a compiler capable of compiling said zig, python, rust no! No you do not!! It’s perfectly totally fine to have multiple different compilers. Literally not a problem at all. That’s my point! Compilers and bu
37.
by forrestthewoods 3mo ago
compilers and build systems are and should be different. A good polyglot build system should support llvm and zig and python and literally any toolchain under the sun.
38.
by forrestthewoods 3mo ago
The world has yet to standardize on a good crossplatform polyglot build system. The only real such build systems are Buck and Bazel. But they have way too much baggage from their overlords. It’s a shame.
39.
by forrestthewoods 3mo ago
> one of Seems reasonably accurate? Odin is not particularly popular. Zig is much much more popular. As-is Go, although that’s not a straight C competitor. But other than that? Odin is a real language being used by real professionals t
40.
by forrestthewoods 4mo ago
Costco is way too damn crowded. There needs to be 2x or 3x the number of stores. It is a great deal. But an utterly miserable shopping experience.
41.
by forrestthewoods 4mo ago
> With wider adoption the ratio shall shift in favor of inference Yes? That’s why more money will be spent on inference than training? I’m talking absolute cost. As the number of people using AI and burning tokens goes up the amount of s
42.
by forrestthewoods 4mo ago
Inference costs are higher than training now. I think. Nvidia is king of general purpose training chips. But inferences can be specialized.
43.
by forrestthewoods 4mo ago
…but why? JS/TS does not seem like the right tool for the job?
44.
by forrestthewoods 4mo ago
> And one I'm more confident about but expect disagreement on: not building on ROS 2 / LeRobot, Tell me more! I am slightly biased in that direction. But can’t fully justify it at this point.
45.
by forrestthewoods 4mo ago
> You do not "lock assets", Uhhhhhh. Locking binary assets is ABSOLUTELY NECESSARY in Git. Except Git can't actually do that. So what locking binary assets Git looks like in practice is an unenforced message in Slack sayin
46.
by forrestthewoods 4mo ago
Frickin sweet. Perforce is a necessary evil in games. Git is simply not suitable. So this is already a huge win. I main that Git is - at absolute best - simply mediocre. It's not a "good" VCS tool. It is merely adequate. I wo
47.
by forrestthewoods 4mo ago
Spectacular write up. Gonna have to re-read this one a few times to fully internalize it.
48.
by forrestthewoods 4mo ago
Thanks for the conversation. But I think I’m done here. Cheers.
49.
by forrestthewoods 4mo ago
Very rude. I have not personally attacked you a single time.
50.
by forrestthewoods 4mo ago
> example of exceptions introducing faulty behavior unrelated to resource management that I asked for? Well there’s a reason that constructors aren’t allowed to throw. Because it would leave objects in a weird hybrid state. My physics sy
51.
by forrestthewoods 4mo ago
> All else being equal, exceptions make this kind of code better by making it more readable. I just fundamentally disagree that hidden secret control flow makes code more readable. Well, it may be more readable but it is, imho, signifi
52.
by forrestthewoods 4mo ago
> You're being rather vague. Completely forget about memory allocation and memory allocation like things. Let’s say I have a physics system that runs an update. Assume we catch outside the update. If anything throws the system is no
53.
by forrestthewoods 4mo ago
^^^ truth speaker
54.
by forrestthewoods 4mo ago
Program state is significantly more complex than just needing some RAII resources to cleanup via destructors. > during sections that may throw Yeah one of the problems with exceptions is it’s impossible to know what “may throw” other tha
55.
by forrestthewoods 4mo ago
> You really don't. Like I said, it's kind of the whole point of exceptions. No, this is actually just wrong. With exceptions you “don’t have to think about” the exception getting caught by some higher level catch. But you do h
56.
by forrestthewoods 4mo ago
> Throwing lets you handle the new situation without changing the API at all. I do not disagree. https://xkcd.com/1172/ If you add exceptions to a library that didn’t previously use them then I almost definitely hav
57.
by forrestthewoods 4mo ago
That’s a No True Scotsman argument. It is not a good or useful one imho.
58.
by forrestthewoods 4mo ago
> What if you don't control those call sites? If I am choosing to change the API contract then someone who wants to use the new API has to update. This is not a big deal. > If the function doesn't use exceptions for normal e
59.
by forrestthewoods 4mo ago
> The only two ways to resolve this contradiction is to throw, or to terminate. Or they’re bad APIs that should be redesigned to be not bad. They’re fallible functions. Don’t write fallible APIs that require exceptions to report errors!
60.
by forrestthewoods 4mo ago
> Throwing an exception and letting it unwind the stack way up (perhaps even all the way up to main()) is the sensible solution No. I would never in a million years do this. If the API is that a function is infallible and then I decide t

More ›