

Zig is not as strict as Rust for memory management


Zig is not as strict as Rust for memory management


for anyone like me who could not understand that stupid title
“Call a spade a spade” is a figurative expression. It refers to calling something “as it is”[1]—that is, by its right or proper name, without “beating about the bush”, but rather speaking truthfully, frankly, and directly about a topic;
“Blow smoke” - to speak idly, misleadingly, or boastfully
Fwiw it works on the desktop’s alexandrite ui and on the thunder app


that crushed ear lobe lol


that’s still massive, an animated webm will probably be more useful


I can’t wait for the day they decide to build a hyperspatial express highway through our star system


that’s bad, we’ll get a pretty bad reputation around the milky way


There’s plenty of busy work that requires some level of “thinking” but it doesn’t add anything to whoever is doing it for the 50th time. You’re the one sounding like an idiot for ignoring this.


OOTL what does notepad++ have to do with that? Or they just like to be eccentric in their releases for marketing?


Right, like I mentioned, it’s a scale problem and how people feel about generated code. Abandonware have always been the majority of repos, because people don’t have time or interest to maintain most things they create. We just have more things being created now (whether they’re any good/usable or not).


Disagree. Most projects are never “done”. Whether that is defined by the user or by the users, there are nearly always things to work on. Maintainers just lose interest or don’t bother. This is as old as open source and it has nothing to do with LLMs, it’s only aggravated by it.


Hardly an issue with generated code. You could say the same about projects before LLMs were widely used for code generation: “most projects are abandoned within months of release”. The difference now is the scale and how some people feel about it.
du* - applogies hehe
don’t you guys pay your rent and buy food with github stars?
A lot of people prefer rounded to sharp corners, if given the option. And given that sharp corners are the most bland default for a UI, I’m not even sure how one can call rounded corners amateurish while defending sharp ones: if you put no effort in an interface whatsoever, you end up with sharp corners.


zero cal pizzas, finally


Reminder that “a coin toss” is only bad odds for problems with binary and equally likely outcomes. And that’s rarely the case for anything that an LLM is used for. A 50% chance of saving an hour of work a couple times a day are pretty good odds. If I have a problem which a candidate solution is easy to verify, it’s often more effective to let an LLM investigate it for some time before I do so, and only jump in if it fails.
There have been several little fixes I’ve done in minutes with an agent that would take me at least an hour to manually investigate, write a solution, test, and refactor. So yes, there is something to it, but you need to know how to use it. Keep arguing in a thread after noticing hallucinations is a clear sign the author doesn’t know how to use an LLM.


This. If you’re at a point that you’re arguing with an LLM, you’ve already lost. Just start a new thread with a different approach, don’t make an article about your inability to use an LLM.
this is what does it for me most times; but I usually also have a CI .env file
actcan use and usejustto abstract recipes e.g. when runningjust test, either CI or local will run depending if the CI env var is set. It’s the same battery of tests, only different env files.