Viewing profile — throwawaymaths

too many features. tryhard vibe

this time in lua. cloudflare can't catch a break

> As a very very heavy LLM user, I also notice that projects tend to be much easier for LLMs (and humans alike) to work on when they use opinionated well-established frameworks. i …

have you ever deployed an erlamg system? the biggest bugbear for concurrent systems is mutable shared data. by inherently being distributable you basically "give up on that" so for…

ironically with zig most of the things that violate expectations are keywords. so you run head first into a whole ton of them when you first start (but at least it doesn't compile)…

yeah, its a better c, but like wouldnt it be nice if c had stadardized fat pointers so that if you move from project to project you don't have to triple check the semantics? for ex…

and you can have good races too (where the order doesnt matter)

'const expected = [_]u32{ 123, 67, 89, 99 };' constant array with u32, and let the compiler figure out how many of em there are (i reserve the right to change it in the future)

why would you need batteries included? the ai can code most integrations (from scratch, if you want, so if you need something slightly off the beaten path it's easy

> suspend/resume special @asyncSuspend and @asyncResume builtins, they will be the low level detail you can build an evented io with. new Io is an abstraction over the higher level…

IDK being able to produce a good product in a corpo environment sure sounds like a competency issue. > how hard it is for top performers to make change then you're not a top perfor…

i am not familiar with rust and i gave up on python async years ago so i have no frame of reference here. but im really not sure why theres a need to distinguish between tasks and …

i haven't. do people still use the "class" keyword?

the io isnt a single resource? it's a module grouping together a pile of code. and you can swap out implementations. the io modules should be responsible for handing out many faila…

i mean not really? it absolutely does nothing to segregate stateful impurity into a type theoretically stateless token

run code anywhere hamstrung by 90s syntax and hidden code indirections

how do you "fail to obtain the token"?

is it not the case that in zig, the execution happens in a_future.await? I presume that: io.async 1 stores in io "hey please work on this" io.async 2 stores in io "hey also please …

Pretty sure the Zig team is aware of this and has plans to fix it before they re-release async.

1) zig's io is not a viral effect type, you can in principle declare a global io variable and use it everywhere that any library calls for it. Not best practice for a library write…

it is what it is. i didnt write it, i was surprised when i read it too. > This document contains the rules that govern these spaces only: > The ziglang organization on Codeberg > #…

Aside from the Chernobyl part, that's basically Andromeda strain

The website is not covered by the CoC, so they are not in abeyance