tomck

6 ms·

1.
by tomck 11mo ago
> `if (file_exists(f))` is misuse of the interface, a lesson in interface design, and a faulty pattern that's easy to repeat with async-await. It's even easier to repeat without async-await, where you don't need to tag the
2.
by tomck 11mo ago
> I replied directly to you My comment was responding only to the person who equated threads and async. My comment only said that async and threading are completely orthogonal, even though they are often conflated > `is_something_true
3.
by tomck 11mo ago
I think you replied to the wrong person. That being said, I don't understand your `is_something_true` example. > It's very often used to do 1 thing at a time when N things could be done instead That's true, but I don'
4.
by tomck 11mo ago
> I do fully understand people who can't get their heads around threads and prefer async This is a bizarre remark Async/await isn't "for when you can't get your head around threads", it's a completely
5.
by tomck 1y ago
I have tried a model on my laptop+GPU before, and it is incredibly unusable. Incredibly slow and just bad output for exactly the work you describe If you're looking for a cheap practical tool + don't care if it's not local,
6.
by tomck 1y ago
This isn't what people are talking about, you aren't understanding the problem With RAII you need to leave everything in an initialized state unless you are being very very careful - which is why MaybeUninit is always surrounded b
7.
by tomck 1y ago
This whole page, and their response in this thread, is about tigerbeetle as a transaction processing database - e.g. financial transaction processing I think this is very clear, I don't know why you're saying that tigerbeetle is t
8.
by tomck 1y ago
You're repeating propaganda from a far right newspaper headline, written misleadingly to make it sound like labour have said something recently about VPNs (they haven't)
9.
by tomck 2y ago
Why do you think you would see a flicker of death? For local inputs, the fixed timestep is always a frame or smaller, this is not an issue unless you're over a network Edit: Oh i see, this is a problem with the commenters suggestion
10.
by tomck 2y ago
> So getListOfUsersWithFoodPreferences and getListOfUsersWithFoodPreferencesWithoutFavouriteFoods living together as client-specific methods is absolutely fine Sorry; my point was that adding this function as a public API 'onion lay
11.
by tomck 2y ago
I have no idea what you're talking about, my example doesn't include any writes, only a read
12.
by tomck 2y ago
Every layer you create is another public API that someone else can use in some other code. Each time your public API is used in a different place, it gathers different invariants - 'this function should be fast', 'this functi
13.
by tomck 2y ago
No, this is how everyone incompetent designs systems Layers of generic APIs required to be 1000x more complex than would be required if they were just coupled to the layer above Changing requirements means tunneling data through many layers
14.
by tomck 2y ago
This article is disingenuous with its Vec benchmark. Each call to `validate` creates a new Vec, but that means you allocate + free the vec for each validation. Why not store the vec on the validator to reuse the allocation? Why not mentio
15.
by tomck 4y ago
You can tell when, because if it uses the allocator it will return an error. So the first line definitely doesn't allocate, and the second definitely does. That is, unless you explicitly handle OOM conditions inside your construct, e
16.
by tomck 6y ago
Is that really that slow? idk how they even read the file in that amount of time, my drive is only about 125MB/s
17.
by tomck 6y ago
> have to restart the server every 20 days because of some memory leak Hmm this seems like something super specific to their async setup, rather than 'common lisp leaks memory'