HN user

feelamee

102 karma

I no need email to register... its incredible....

Posts1
Comments137
View on HN

As discussed earlier, having full control over allocations and deallocations is what I want in our compiler's implementation. And in tests, I also appreciate the testing allocators detecting leaks—it can even detect leaks in compiled Roc code! Unfortunately, to get that benefit requires a lot of "init this, defer deinit" code in tests that has to be correct or else the test fails on a memory leak. None of that is necessary in Rust. I care more about the compiler's implementation being the way I want it than the tests looking nicer, but in a perfect world I could somehow have both.

haha, just for fun... do you want a C++ in your perfect world :D?

sure, without any action from the user to increase safety, desktop OS's just allow any app to read any files. On the other hand, desktop OS's allow a wide spread list of ways to control what applications have access too (especially Linux and BSD families). Although, despite all this, running malware can never be safe.

I don't understand - you arguing that artists should learn to use cli? if so, "programmish" git output is not a problem, because they already not just artist, they learned git.

But, for me this looks like this - if artist need to go to cli to solve some error, then this is bug or leaky abstraction in GUI client.

I think this can happen in technical communities - people who can write/read/understand code. Who really cares about software size/performance/usability/minimalism.

This is a small part of the whole users, but.. why not. People who value hand-by wood goods are also a small part.

Also, there are also communities which slow down AI integration - like Zig. Maybe they will alive

funny, but seriously.. Caring about child safety is not only about restricting network access, but also choosing the right (read as safe/predictable/stable) place for living.

I understand that this is not always possible, but... it's spectrum - try to reach maximum and do your best.

Also, consider that I don't have any experience in raising a little human, so, probably, I'm talking nonsense

q> sp_log() writes directly to an IO writer. An IO writer can be buffered or unbuffered, but is unbuffered by default. This is a feature, not a bug. Have a look through the IO code!

Why is the unbuffered default? Is there any thoughts on this?

This decision seems to based more in politics than engineering.

Will you use untrustworthy dependencies in your project, which has users? I think, no.

I don't know, but I feel that this is the case with yt-dlp.

And this is absolutely engineering - care about quality and security of your software, which is used by thousands of people

Obviously, in most cases they will generate boring slop. But this is not mean that [yet] they can't generate good reading.

I'm deciding to read something not by answering question "is it LLM written on by human?". But by question - "is it good and interesting?". With the same thoughts I will skip LLM slop as well as humans slop