nickelpro

6 ms·

31.
by nickelpro 6mo ago
CPS[1] is where all the effort is currently going for a C++ packaging standard, CMake shipped it in 4.3 and Meson is working on it. Pkgconf maintainer said they have vague plans to support at some point. There's no current effort to st
32.
by nickelpro 6mo ago
The intended value is difficult to discern in AI written pieces. I agree with both of you, there's some interesting tricks here for how a website builds anti-bot protection, but the AI sloppification is framing it as a consumer protect
33.
by nickelpro 6mo ago
Because it's both slow and terrible? You generally do not want to simulate or describe raw gate-level netlists. Both languages are capable of that. Old school Verilog (not SystemVerilog) is still the defacto netlist exchange format for
34.
by nickelpro 6mo ago
SystemVerilog basically fixes this with always_comb vs always_latch. There's no major implementation which doesn't handle warning or even failing the flow on accidental latch logic inside an always_comb.
35.
by nickelpro 7mo ago
I believe it for the reasons explained by Daniel Stone, there is no difference between my opinion and his on the topic of X's inefficiency as an IPC middleman.
36.
by nickelpro 7mo ago
Don't take it from me, Daniel Stone has a whole talk on the motivation for Wayland: https://youtu.be/RIctzAQOe44 Broadly, the X Server has a bunch of capabilities which are irrelevant. The modern model is really Window
37.
by nickelpro 7mo ago
Wayland is far more aligned with the Unix philosophy than Xorg ever was. Xorg was a giant, monolithic, do everything app. The Unix philosophy is fragmentation into tiny pieces, each doing one thing and hoping everyone else conforms to the s
38.
by nickelpro 7mo ago
https://wayland.app/protocols/ Click any protocol, very few outside the core and absolute essential extensions have universal support.
39.
by nickelpro 7mo ago
No. X11's problems were rooted in the abstractions presented by the X11 core protocol and its extension mechanisms. The interface, not merely the implementation. Wayland was correct in first focusing on replacing this interface. The pr
40.
by nickelpro 7mo ago
But this is sort of the nature of the problem? In X11, the problem was Xserver. Now, X11's design philosophy was hopelessly broken and needed to be replaced, but it wasn't replaced. As you correctly point out, there is no "Wa
41.
by nickelpro 7mo ago
mmap is slow because stalling on page faults is slow. Your process stalls and sits around doing nothing instead of processing data you've read already. You can google the benchmarks if you like. io_uring wasn't built just for kick
42.
by nickelpro 7mo ago
If we're going to be pedantic, mmap is a syscall. It happens that the C version is standardized by POSIX. The underlying syscall doesn't use the C ABI, you need to wrap it to use it from C in the same way you need to wrap it to us
43.
by nickelpro 7mo ago
mmap is also relatively slow (compared to modern solutions, io_uring and friends), and immensely painful for error handling. It's simple, I'll give it that.
44.
by nickelpro 7mo ago
> Why does C have the best file API > Look inside > Platform APIs Ok. I agree platform APIs are better than most generic language APIs at least. I disagree on mmap being the "best".
45.
by nickelpro 8mo ago
Dumb. Compilers aren't deterministic in small ways, timestamps, encoding paths into debug information, etc. These are trivial, annoyances to reproducible build people and little else. You cannot take these trivial reproducibility issue
46.
by nickelpro 8mo ago
> a paid, invite-only social network where every person is verified human and there's no algorithm This seems like an incredibly niche product that only a handful of people are interested in to begin with. It isn't an notable o
47.
by nickelpro 8mo ago
It's original meaning was days since software release, without any security connotation attached. It came from the warez scene, where groups competed to crack software and make it available to the scene earlier and earlier. A week afte
48.
by nickelpro 8mo ago
Properly manage PATH for the context you're in and this is a non-issue. This is the solution used by most programming environments these days, you don't carry around the entire npm or PyPI ecosystem all the time, only when you act
49.
by nickelpro 8mo ago
The OP does this and measures ~1.2x improvement over PCH.
50.
by nickelpro 8mo ago
Macro hygiene, static initialization ordering, control over symbol export (no more detail namespaces), slightly higher ceiling for compile-time and optimization performance. If these aren't compelling, there's no real reason.
51.
by nickelpro 8mo ago
import std; is an order of magnitude faster than using the STL individually, if that's evidence enough for you. It's faster than #include <iostream> alone. Chuanqi says "The data I have obtained from practice ranges fro
52.
by nickelpro 9mo ago
> even senior C++ developers are always going to be able to deduce the correct value category Depends what "senior" means in this context. Someone with 20-years of domain experience in utility billing, who happened to be writin
53.
by nickelpro 10mo ago
The author has succeeded only in arguing one meaningless image factory produces images they find more aesthetically pleasing than another meaningless image factory. The framing implies they understand little of art at all; beyond gurgling a
54.
by nickelpro 10mo ago
Reading COW memory doesn't cause a fault. It doesn't mean unused literally. And even if it's not COW, there's nothing wrong or inefficient about opportunistically allocating pages ahead of time to avoid syscall latency.
55.
by nickelpro 10mo ago
You're an expert, you're overestimating the competence of the median programmer. That's a great bug you found, and of course it is a compiler bug, not UB. 99.9% of the bugs I've dealt with of this sort were just pointer
56.
by nickelpro 10mo ago
People keep saying "O3 has bugs," but that's not true. At least no more bugs than O2. It did and does more aggressively expose UB code, but that isn't why people avoid O3. You generally avoid O3 because it's slower.
57.
by nickelpro 10mo ago
Unity builds have been largely supplanted by LTO. They still have uses for build time improvements in one-off builds, as LTO on a non-incremental build is usually slower than the equivalent unity build.
58.
by nickelpro 10mo ago
Except for `xchg eax, eax`, which was the canonical nop on x86. Because it was supposed to do nothing, having it zero out the top 32-bits of rax would be quite surprising. So it doesn't. Instead you need to use the multi-byte, general
59.
by nickelpro 11mo ago
> The community doesn't need to be a 'house party,' but the license guarantees the right for a community to form when the original author walks away. Which is why the license is the only thing that matters. Without the lic
60.
by nickelpro 11mo ago
> That is obviously false... It is fundamentally true. You cannot have a Pokemon community without Pokemon, a knitting community with yarn, or a software community without software. > Technically true You should have stopped here. It

More ›