Readit News logoReadit News
sixthDot commented on The Scottish island that bought itself   elysian.press/p/the-scott... · Posted by u/toomuchtodo
sixthDot · 10 hours ago
> When a wealthy artist bought the island [...]

Not an artist. British businessman and Winter Olympian. See https://en.wikipedia.org/wiki/Keith_Schellenberg.

sixthDot commented on LLVM: The bad parts   npopov.com/2026/01/11/LLV... · Posted by u/vitaut
sixthDot · a month ago
Also the C API is a bit the poor child. Plenty of useful options (or even opt passes !) are not available.
sixthDot commented on The C3 Programming Language   c3-lang.org... · Posted by u/y1n0
norir · a month ago
Yes, this is fine for basic exploration but, in the long run, I think LLVM taketh at least as much as it giveth. The proliferation of LLVM has created the perception that writing machine code is an extremely difficult endeavor that should not be pursued by mere mortals. In truth, you can get going writing x86_64 assembly in a day. With a few weeks of effort, it is possible to emit all of the basic x86_64 instructions. I have heard aarch64 is even easier but I only have experience with x86_64.

What you then realize is that it is possible to generate quality machine code much faster than LLVM and using far fewer resources. I believe both that LLVM has been holding back compiler evolution and that it is close to if not already at peak popularity. As LLMs improve, the need for tighter feedback loops will necessitate moving off the bloat of LLVM. Moreover, for all of the magic of LLVMs optimization passes, it does very little to prevent the user from writing incorrect code. I believe we will demand more from a compiler backend than LLVM can ever deliver.

The main selling point of LLVM is that you gain access to all of the targets, but this is for me a weak point in its favor. Firstly, one can write a quality self hosting compiler with O(20) instructions. Adding new backends should be trivial. Moreover, the more you are thinking about cross platform portability, the more you are worrying about hypothetical problems as well as the problems of people other than yourself. Get your compiler working well first on your machine and then worry about other machines.

sixthDot · a month ago
If only that was only about emitting byte code in a file then calling the linker... you also have the problem of debug information, optimizers passes, the amount of tests required to prove the output byte code is valid, etc.
sixthDot commented on Tell HN: Happy New Year    · Posted by u/schappim
sixthDot · a month ago
Another one bites the dust
sixthDot commented on Web Browsers have stopped blocking pop-ups   smokingonabike.com/2025/1... · Posted by u/coldpie
sixthDot · a month ago
The bigest anoyance nowadays (in the EU at least) is rather the cookie policy agreement. "View the list of our 258 partners", etc.
sixthDot commented on Would You Kill for a Job?   nytimes.com/2025/12/27/op... · Posted by u/mitchbob
sixthDot · 2 months ago
That remind me of The Ax [0]

[0] https://www.imdb.com/title/tt0422015/

sixthDot commented on South Atlantic Anomaly   en.wikipedia.org/wiki/Sou... · Posted by u/sixthDot
sixthDot · 2 months ago
How this was discovered is incredible. An amator satelite was lauched. operators collected data. At some point they had the idea to plot them. That gave a big stain in the south atlantic.
sixthDot commented on Why Zig When There is C++, D, and Rust?   ziglang.org/learn/why_zig... · Posted by u/tosh
sixthDot · 2 months ago
Not into ZIG but for some reasons I monitor new issues that pop in the bug tracker of "new" / "raisins" languages. ZIG has clearly reached the next level, let's say if you compare the issues two years ago (lot of comptime/type system things) VS now.
sixthDot commented on Why xor eax, eax?   xania.org/202512/01-xor-e... · Posted by u/hasheddan
sixthDot · 2 months ago
I've wrote a lot of `xor al,al` in my youth.

u/sixthDot

KarmaCake day205July 2, 2023View Original