feelamee

45 ms·

61.
by feelamee 5mo ago
> what can I do to keep them away from stuff 99% of people agree isn't for children to see, without something like this? > before they're ready to handle it You can restrict any access for the network to them. Extra bonus,
62.
by feelamee 5mo ago
How do they all know that it is vibe-coded? I missed the meeting where they were handing out vibe-code-detectors? Please, describe.. P.S. sad to see that HN becomes a witch hunting place
63.
by feelamee 5mo ago
> Oops... apparently this is vibecoded. Welp, I just wasted ten minutes of my life reviewing slop that I'm not going to get back. you interested in project and spent some time researching it, but stop when understand that it is vibe
64.
by feelamee 5mo ago
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
65.
by feelamee 5mo ago
> 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 absolu
66.
by feelamee 5mo ago
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
67.
by feelamee 5mo ago
> In general, reading comments written by actual humans about how a submission is AI, is preferable to reading a long submission written by AI Not as in general as you think. I don't care who writes comments/article - be you hu
68.
by feelamee 5mo ago
because 70 of 140 comments under this submission are owned by this thread about AI. And this is usually not what you want when you click on an interesting submission
69.
by feelamee 5mo ago
another useful sense is easy to understand/read what programmer want to write. (ofc exclude mad code with macros etc). Brainfuck is absolutely not simple in this case
70.
by feelamee 5mo ago
I think vice versa - C is so simply, that debugging it is just a pleasant walk. Especially compared with modern languages with lambdas/exceptions/virtual functions and so on. The one thing I see can make it harder is function poin
71.
by feelamee 5mo ago
> We need some way of fixing UB at scale, without committing AI slop nor overwhelming human reviewers. Write compiler which will define all this behavior. Usually people forget that UB exists only in standard. In practice it is always de
72.
by feelamee 5mo ago
I don't see any problems implementing those 4 types as bindings and others by manual implementation
73.
by feelamee 5mo ago
Does this mean that you will not review human slop too? Then, what if ai will write something cool/good/interesting/high quality/amazing?
74.
by feelamee 5mo ago
why? why you should care if it is human written or by ai, if the result is the same?
75.
by feelamee 5mo ago
ok, probably age verification and strict access control from the state solve your problem.. for some time. But what will you do when this one will grow? There will be no restrictions - not from you, not from the state. Does restriction real
76.
by feelamee 5mo ago
> Your BLAS library will provide you just the four basic element types, ..., and you still need fallback logic anyways to handle the other types. so, your problem with it is that it does all you want (e.g. LAPACK bindings) AND give extra
77.
by feelamee 5mo ago
are u carefully read <linalg> paper[1]? It doesn't require to reimplement it... > Our proposal is inspired by and extends the dense BLAS interface. A natural implementation might look like this: > 1. wrap an existing C o
78.
by feelamee 5mo ago
> People that don’t use SIMD today are unlikely to use std::simd tomorrow. why? at least I see that I will start with std::simd in my pets. If this would not enough, I would go forward to intrinsics. But, I think, starting with std::simd
79.
by feelamee 5mo ago
> The pattern is clear: every major project that actually needs portable SIMD in production chose a third-party library or a different language of course they chose third-party library, because C++26 is just only published and don't
80.
by feelamee 6mo ago
I heard that Zed has very impressive collaboration features. I tried them a little and they really look well (like discord, but directly in editor). But this was very superficial look
81.
by feelamee 6mo ago
Also.. Easily opt-out from telemetry collection https://github.com/beatcracker/toptout (last commit 3ya)
82.
by feelamee 6mo ago
> But if AI is detected in the phrasing and not disclosed, it begs a lot of questions. absolutely zero questions from me. If I see two exactly same writings: one - by human, another - by AI. For me its doesn't matter. > Most long
83.
by feelamee 6mo ago
what do you mean under Ada's complexity? E.g. C++ is really complex because of a lot of features which badly interoperate between themselves. Is this true for the Ada lang/compiler? Or do you mean the whole complexity of ideas in
84.
by feelamee 6mo ago
does it really matter? If AI can produce an essay of such quality - take my respect and steal my time please
85.
by feelamee 6mo ago
why? Before comments about LLM I didn't notice this. After I compared pre-LLM posts and post-LLM and looks like AI was used to write/edit this article. But.. why should I matter? Why my ignorance of this fact insane you?
86.
by feelamee 6mo ago
sure, but solving conflicts is still hard in git. This can be simplified.
87.
by feelamee 6mo ago
the one feature which I have never seen in VCS is ability to stick commit message not just to all changes, but specifically to line/hunk. It looks like very intuitive for me - I don't want to invent "references style" to
88.
by feelamee 7mo ago
why? There is LSP support included. Pretty usable. Of course this is not fully IDE, but I don't expect this from "editor"
89.
by feelamee 8mo ago
your words... > C++ implementations of defer are either really ugly I agree with @pjmlp - you need to write wrappers around the C api. But if you.. > If I'm gonna write RAII wrappers around every tiny little thing that I happen t
90.
by feelamee 8mo ago
if you do it once - why do you care about "ugly" scope_exit? btw, writing such wrappers is easy and does not require a lot of code.

More ›