@misterclayt0n I mean, he never said anyuthing about original bun being slop or anything about jarred. He just stated that they warned about comptime usage and lto, that's all. Regarding the slop rewrite, yes, he did say that
@skylar_b_payne@swazza85@schrockn@jarredsumner I mean, he states he lied about things and didn't take advices, he did not say jared is a piece of shit and has to die, you guys are soft
@boquila_ngo@ToushunHare didn't crash because of zig, and the reason they changed to rust was to quote "don't want to handle memory msyelf and let compiler do it".
Moreover, tigerbettle is written in zig and used in production
@dreamsofcode_io I do think having agents for going through ideas is the correct path. The amount of non needed code they produce pisses me off and i have to spend more time having to tell them "no i told you in the spec not to do this" is ridiculous. But for navigating ideas, very good
@furiouswhopper@galactic_dust_@possiblyazure again, 200 code means that request succeeded, if you have conflict error, internal error, there are codes for that. Especially if you integrate your application with third parties or any system, they follow the protocol and error handling for specific cases. (not found, conflict)
@furiouswhopper@galactic_dust_@possiblyazure don't agree with this, if you do a rest api or have a http service, you need to follow the protocol. It's like using the SCIM protocol and not following the field because your app is not scim itself but uses the protocol.