jstimpfle

8 ms·

61.
by jstimpfle 3mo ago
Designing something good for me means going through at least 11 seriously bad approaches before half understanding the problem and having a half-working solution. Trying to use a notebook to aid a learning or research process at all has alw
62.
by jstimpfle 3mo ago
> Also one separate function being different than the operator is not a language level feature, it is how that one library data structure is made. That's not so much the point: the point is that even when calling a regular method co
63.
by jstimpfle 3mo ago
> Again you can make these bold statements but saying pointer chasing has no performance impact is what people say when they don't understand the cost of TLB misses and caches misses. You are right to call this out but I did not mea
64.
by jstimpfle 3mo ago
I was not asking, and certainly not for a toy example, are you STILL under the impression you need to explain beginner level C++ to me? You can btw remove the move() from the return statement in this example. It's normal to omit it as
65.
by jstimpfle 3mo ago
>> Move it, so simple, pointer invalidation. > It works for everyone else, I'm not sure why this is controversial. Show the evidence. It does not. It introduces vast amounts of complexity. So much that they were thinking they
66.
by jstimpfle 3mo ago
> Like bringing up PIMPL for no reason? What disorder are you suffering from? Please check who was bringing up PIMPL. Hint: it was the person who does not know what they're talking about. > Which one is the argument against destr
67.
by jstimpfle 3mo ago
You are continuing to fight strawmans I have never said and continuing to not get what I said and continuing to lecture me about beginner level C++. I am bored. > Move it if you need to, so simple! Move it, so simple, pointer invalidatio
68.
by jstimpfle 3mo ago
It's long been clear that you don't understand what you're talking about when you're criticizing what I say. You don't realize that I understand everything you say and I'm only explaining where your line of rea
69.
by jstimpfle 3mo ago
> More insults but there is no difference here. Rebutting your wild and easily disproved claims where it's necessary. > I looked at your godbolt link, which part of this does C avoid? Should I spell it out again for you? With non
70.
by jstimpfle 3mo ago
> Nope, destructors have nothing to do with this and this was never something you mentioned before. If it was you could show it with godbolt. How about you simply Ctrl+F for "build time" or "compile time" and admit yo
71.
by jstimpfle 3mo ago
> Now we're firmly into the insults phase. We have been from about your 2nd comment on. > "I haven't considered that" Considered WHAT? > I repeated what was in the comments. This is another example of claims wit
72.
by jstimpfle 3mo ago
> Your own project First, tone it down a little please, would you? It's not "my project", what is wrong with you? > ... has plenty of the bugs that destructors and contained memory allocation avoid. Raw heap allocations
73.
by jstimpfle 3mo ago
> If you can't demonstrate it with actual source code then you just have claims and no evidence. I can NOT demonstrate it in a tiny godbolt because the effects I am talking about don't apply on a micro-scale. I CAN demonstrate
74.
by jstimpfle 3mo ago
> You bringing up something unrelated doesn't mean anything just because you keep bringing it up. It's NOT unrelated. It is a real world demonstration of the simplicity possible by custom modeling of allocation and lifetime con
75.
by jstimpfle 3mo ago
> If this is so simple I _never_ said it was simple. It is actually very subtle, which is also why I made many attempts at integrating RAII style programming for many projects. RAII works for applications with simple lexical and local li
76.
by jstimpfle 3mo ago
Iterator invalidation is absolutely a huge deal for many datastructures in practice. From an ergonomic standpoint alone it makes a huge difference. 10 years ago I argued the opposite, but juggling indices simply is not fun. Replacing pointe
77.
by jstimpfle 3mo ago
I told you what to check out. I'm not regurgitating this, I've done it often enough. Have you spent 1 minute cloning the raddebugger, 3 seconds to build it, and 0.5 seconds to launch it, to be convinced that it is a solid product?
78.
by jstimpfle 3mo ago
> So lets hear them. There are few people delivering more in-depth explanations of their claims, like literally thousands of hours of content. You can just look it up . If you disagree, please disagree. Personally I find what they say a
79.
by jstimpfle 3mo ago
> This is the statement that no one seems to be able to back up. Actually there are many explanations of systemic issues arising from reliance on RAII. Both Jon and Casey are very good explaining the matters. > Instead you start talki
80.
by jstimpfle 3mo ago
> the main reason to choose arena allocators is for correctness, not speed. They make similar time/space tradeoffs to garbage collectors in that they grant higher allocation throughput in exchange for more memory usage. I'm not
81.
by jstimpfle 3mo ago
You must mean confusing achievements in the area of creating large maintainable and performant systems on the one hand, with achievements in the area of creating large maintainable and performant systems on the other hand? And let me incude
82.
by jstimpfle 3mo ago
Correctness (the kind that comes from simplicity and maintainability) and performance pretty much always go hand in hand. The only additional ingredient to "bridge the gap" between the two is detail .
83.
by jstimpfle 3mo ago
Apparently you're the school of dismissive person who can't even be bothered to look up their technical achievements.
84.
by jstimpfle 3mo ago
If you use a JSON parser, URL parser, configuration file parser, async framework, and so on, maybe you have other problems. Not that I don't know these project or don't have to work on them, but I don't think it matters what
85.
by jstimpfle 3mo ago
> You do the endianness conversion Exactly my point.
86.
by jstimpfle 3mo ago
You may have never done socket programming, or do you use wrapper libs in Zig? Because you have to send the kernel big endian port numbers for example. What do you do if you program a kernel in Zig, or just generally do low level networking
87.
by jstimpfle 3mo ago
Does that mean there are no file formats thatbuse big endian? And network byte order isn't a thing?
88.
by jstimpfle 4mo ago
It's not as black and white as you claim. 99% is obviously much better than 0%, and 99.999% would be an exceptional, unheard-of improvement. In most software projects, this would find ALL bugs. And most "memory safe" language
89.
by jstimpfle 4mo ago
It might just mean the opposite. Unergonomic and/or slow memory safe languages might not be needed anymore at some point, because LLM can check for reasonable programming patterns and can do some amount of vulnerability checking upfron
90.
by jstimpfle 4mo ago
This is one of the articles where I'm immediately grateful to the author to have written it down. Very good and easy to pick up point, actionable advice. I would just slightly modify it, don't create a time bomb. "I would lik

More ›